README.md in kite-0.0.6

- old
+ new
@@ -11,93 +11,19 @@
 
 Requirements
 -----
 
 - Install [terraform](https://www.terraform.io/intro/getting-started/install.html)
-- Install [bosh-init](https://bosh.io/docs/install-bosh-init.html)
-- Install the [bosh_cli](https://bosh.io/docs/bosh-cli.html)
+- Install [bosh](https://bosh.io/docs/cli-v2.html#install)
 
-Ensure you have created a `terraform/terraform.tfvars` file with your variables, or set suitable [environment variables](https://www.terraform.io/docs/configuration/variables.html). An example tfvars file can be found in `terraform/terraform.tfvars.example`
-
-Assumptions
------
-
-You already have:
-
-- A Route53 Zone in AWS.
-- An EC2 SSH keypair
-- An SSL certificate in AWS for your Concourse ELB
-
 Usage
 -----
 
-Set your desired AWS region in `terrform/variables.tf`. Ensure terraform is in your path, then apply the configuration to prepare the IaaS for BOSH and Concourse:
+To deploy a BOSH Director:
+- Apply the terraform IaC from `terraform` folder
+- Run `bin/setup_tunnel.sh` to create an SSH CLI tunnel
+- Run `kite render bosh --cloud aws` to render BOSH deployment files
+- Run `bin/bosh_setup.sh` to deploy the BOSH Director
 
-```
-cd terraform/
-terraform apply
-```
-Set the following environment variables:
+To access BOSH Director information, use bosh -e *bosh_name* env
 
-```
-$AWS_ACCESS_KEY_ID
-$AWS_SECRET_ACCESS_KEY
-$AWS_REGION
-$AWS_AZ
-$BOSH_PASSWORD
-$AWS_KEYPAIR_KEY_NAME
-$PRIVATE_KEY_PATH
-```
-
-Then create the `bosh-director.yml` manifest:
-```
-./bin/make_manifest_bosh-init.sh
-```
-
-You are ready to deploy the BOSH Director
-```
-bosh-init deploy bosh-director.yml
-```
-
-Go and make a cup of tea.
-
-Once the director is deployed, target it and apply your cloud-config for AWS.
-Remember to set your chosen AZ and the subnet-id output by terraform in `aws-cloud.yml`.
-
-```
-bosh target <your EIP address>
-bosh update cloud-config aws-cloud.yml
-```
-
-Set a database password and external URL for your deployment in these environment variables:
-
-```
-$DB_PASSWORD
-$CONCOURSE_URL
-```
-Create a new OAuth application in GitHub as described [here](http://concourse.ci/authentication.html). The manifest assumes the existance of a 'CI' team that contains your authorised users, so create that too. Then set the following environment variables:
-
-```
-$GITHUB_ORG
-$GITHUB_CLIENT_ID
-$GITHUB_CLIENT_SECRET
-```
-
-Then create a concourse manifest for a single server deployment:
-```
-./bin/make_manifest_concourse.sh
-```
-Or, create a concourse manifest for small cluster:
-```
-./bin/make_manifest_concourse-cluster.sh
-```
-
-Upload the necessary stemcell & releases, then deploy concourse:
-```
-bosh upload stemcell https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-trusty-go_agent
-bosh upload release https://bosh.io/d/github.com/concourse/concourse
-bosh upload release https://bosh.io/d/github.com/cloudfoundry-incubator/garden-runc-release
-bosh deployment concourse.yml
-bosh deploy
-```
-
-Congratulations, you should now be able to see your new CI server at https://your-concourse-url.
+To connect to Bastion over SSH, use ssh jumpbox@*bastion ip* -i jumpbox.key