http://theblasfrompas.blogspot.com/2018/08/bosh-bootloader-or-bubble-as-pronounced.html
Now with bosh director deployed it's time to deploy concourse itself. The process is very straight forward as per the steps below
1. First let's clone the bosh concourse deployment using the GitHub project as follows
2. Target bosh director and login, must set ENV variables to connect to AWS bosh correctly using "eval" as we did in the previous post. This will set all the ENV variables we need
$ eval "$(bbl print-env -s state)"
$ bosh alias-env aws-env
$ bosh -e aws-env log-in
3. At this point we need to set the external URL which is essentially the load balancer we created when we deployed Bosh Director in the previous post. To get that value run a command as follows where we deployed bosh director from as shown below
pasapicella@pas-macbook:~/pivotal/aws/pcf-pipelines$ bbl lbs -s state
Concourse LB: bosh-director-aws-concourse-lb [bosh-director-aws-concourse-lb-f827ef220d02270c.elb.ap-southeast-2.amazonaws.com]
4. Now lets set that ENV variable as shown below
pasapicella@pas-macbook:~/pivotal/aws/pcf-pipelines$ export external_url=https://bosh-director-aws-concourse-lb-f827ef220d02270c.elb.ap-southeast-2.amazonaws.com
5. Now from the cloned bosh concourse directory change to the directory "concourse-bosh-deployment/cluster" as shown below
pasapicella@pas-macbook:~/pivotal/aws/pcf-pipelines$ cd concourse-bosh-deployment/cluster
6. Upload stemcell as follows
$ bosh upload-stemcell light-bosh-stemcell-3363.69-aws-xen-hvm-ubuntu-trusty-go_agent.tgz
Verify:
pasapicella@pas-macbook:~/pivotal/aws/pcf-pipelines$ bosh -e aws-bosh stemcells
Using environment 'https://10.0.0.6:25555' as client 'admin'
Name Version OS CPI CID
bosh-aws-xen-hvm-ubuntu-trusty-go_agent 3363.69 ubuntu-trusty - ami-0812e8018333d59a6
(*) Currently deployed
1 stemcells
Succeeded
7. Now lets deploy concourse as shown below with a command as follows. Make sure you set a password as per "atc_basic_auth.password"
$ bosh deploy -d concourse concourse.yml -l ../versions.yml --vars-store cluster-creds.yml -o operations/basic-auth.yml -o operations/privileged-http.yml -o operations/privileged-https.yml -o operations/tls.yml -o operations/tls-vars.yml -o operations/web-network-extension.yml --var network_name=default --var external_url=$external_url --var web_vm_type=default --var db_vm_type=default --var db_persistent_disk_type=10GB --var worker_vm_type=default --var deployment_name=concourse --var web_network_name=private --var web_network_vm_extension=lb --var atc_basic_auth.username=admin --var atc_basic_auth.password=..... --var worker_ephemeral_disk=500GB_ephemeral_disk -o operations/worker-ephemeral-disk.yml
8. Once deployed verify the deployment and VM's created as follows
pasapicella@pas-macbook:~/pivotal/aws/pcf-pipelines$ bosh -e aws-env deployments
Using environment 'https://10.0.0.6:25555' as client 'admin'
Name Release(s) Stemcell(s) Team(s)
concourse concourse/3.13.0 bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3363.69 -
garden-runc/1.13.1
postgres/28
1 deployments
Succeeded
pasapicella@pas-macbook:~/pivotal/aws/pcf-pipelines$ bosh -e aws-env vms
Using environment 'https://10.0.0.6:25555' as client 'admin'
Task 32. Done
Deployment 'concourse'
Instance Process State AZ IPs VM CID VM Type Active
db/db78de7f-55c5-42f5-bf9d-20b4ef0fd331 running z1 10.0.16.5 i-04904fbdd1c7e829f default true
web/767b14c8-8fd3-46f0-b74f-0dca2c3b9572 running z1 10.0.16.4 i-0e5f1275f635bd49d default true
worker/cde3ae19-5dbc-4c39-854d-842bbbfbe5cd running z1 10.0.16.6 i-0bd44407ec0bd1d8a default true
3 vms
Succeeded
9. Navigate to the LB url we used above to access concourse UI using the username/password you set as per the deployment
https://bosh-director-aws-concourse-lb-f827ef220d02270c.elb.ap-southeast-2.amazonaws.com/
10. Finally we can see of Bosh Director and Concourse deployment VM's on our AWS instance EC2 page as follows
More Information
No comments:
Post a Comment