We're on to Part 2. In Part 1, we deployed MicroBOSH that enables us to deploy BOSH. BOSH is needed to deploy Cloud Foundry. This is all adapted from the official documentation located at Deploying Cloud Foundry on vSphere.
This tutorial will go over the steps it takes to deploy Cloud Foundry on vSphere. Here are the proper steps:
Part 1 - How to install MicroBOSH
Part 2 - Deploy BOSH with MicroBOSH
Part 3 - Deploy Cloud Foundry with BOSH
1. If you didn't complete the final step from part 1, we need to set our target and supply the un/pw combo of admin/admin with bosh target 192.168.50.166
administrator@originalbosh:/bosh/deployments$ bosh target 192.168.50.166 Target set to `MicroBOSH01' Your username: admin Enter password: ***** Logged in as `admin'
2. Upload our bosh stemcell to the microBOSH appliance
cd .. cd stemcells bosh upload stemcell bosh-stemcell-2427-vsphere-esxi-ubuntu.tgz
You should see the following output
administrator@originalbosh:/bosh/stemcells$ bosh upload stemcell bosh-stemcell-2427-vsphere-esxi-ubuntu.tgz
Verifying stemcell...
File exists and readable OK
Verifying tarball...
Read tarball OK
Manifest exists OK
Stemcell image file OK
Stemcell properties OK
Stemcell info
-------------
Name: bosh-vsphere-esxi-ubuntu
Version: 2427
Checking if stemcell already exists...
No
Uploading stemcell...
bosh-stemcell: 100% |ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| 385.9MB 23.5MB/s Time: 00:00:16
Director task 1
Started update stemcell
Started update stemcell > Extracting stemcell archive. Done (00:00:03)
Started update stemcell > Verifying stemcell manifest. Done (00:00:00)
Started update stemcell > Checking if this stemcell already exists. Done (00:00:00)
Started update stemcell > Uploading stemcell bosh-vsphere-esxi-ubuntu/2427 to the cloud. Done (00:00:55)
Started update stemcell > Save stemcell bosh-vsphere-esxi-ubuntu/2427 (sc-b7e9628a-e64d-47aa-81d4-60b71758ba96). Done (00:00:00)
Done update stemcell (00:00:58)
Task 1 done
Started 2014-05-28 18:43:14 UTC
Finished 2014-05-28 18:44:12 UTC
Duration 00:00:58
Stemcell uploaded and created.
See the uploaded stemcells by using bosh stemcells
administrator@originalbosh:/bosh/stemcells$ bosh stemcells +--------------------------+---------+-----------------------------------------+ | Name | Version | CID | +--------------------------+---------+-----------------------------------------+ | bosh-vsphere-esxi-ubuntu | 2427 | sc-b7e9628a-e64d-47aa-81d4-60b71758ba96 | +--------------------------+---------+-----------------------------------------+ (*) Currently in-use Stemcells total: 1
3. Upload a bosh release. Navigate to BOSH Artifacts and copy the link for the latest BOSH release. Go to the releases directory and download the file and then upload it to the bosh.
cd /bosh/releases wget https://s3.amazonaws.com/bosh-jenkins-artifacts/release/bosh-2579.tgz bosh upload release bosh-2579.tgz
You will see the following output:
administrator@originalbosh:/bosh/stemcells$ cd /bosh/releases
administrator@originalbosh:/bosh/releases$ wget https://s3.amazonaws.com/bosh-jenkins-artifacts/release/bosh-2579.tgz
--2014-05-28 14:47:07-- https://s3.amazonaws.com/bosh-jenkins-artifacts/release/bosh-2579.tgz
Resolving s3.amazonaws.com (s3.amazonaws.com)... 54.231.0.112
Connecting to s3.amazonaws.com (s3.amazonaws.com)|54.231.0.112|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 130310044 (124M) [application/x-gtar]
Saving to: `bosh-2579.tgz'
100%[===========================================================================================================================================================>] 130,310,044 2.38M/s in 64s
2014-05-28 14:48:12 (1.94 MB/s) - `bosh-2579.tgz' saved [130310044/130310044]
administrator@originalbosh:/bosh/releases$ bosh upload release bosh-2579.tgz
Verifying release...
File exists and readable OK
Extract tarball OK
Manifest exists OK
Release name/version OK
Read package 'nginx' (1 of 14) OK
Package 'nginx' checksum OK
Read package 'genisoimage' (2 of 14) OK
Package 'genisoimage' checksum OK
Read package 'powerdns' (3 of 14) OK
Package 'powerdns' checksum OK
Read package 'blobstore' (4 of 14) OK
Package 'blobstore' checksum OK
Read package 'ruby' (5 of 14) OK
Package 'ruby' checksum OK
Read package 'mysql' (6 of 14) OK
Package 'mysql' checksum OK
Read package 'nats' (7 of 14) OK
Package 'nats' checksum OK
Read package 'common' (8 of 14) OK
Package 'common' checksum OK
Read package 'director' (9 of 14) OK
Package 'director' checksum OK
Read package 'redis' (10 of 14) OK
Package 'redis' checksum OK
Read package 'registry' (11 of 14) OK
Package 'registry' checksum OK
Read package 'libpq' (12 of 14) OK
Package 'libpq' checksum OK
Read package 'postgres' (13 of 14) OK
Package 'postgres' checksum OK
Read package 'health_monitor' (14 of 14) OK
Package 'health_monitor' checksum OK
Package dependencies OK
Checking jobs format OK
Read job 'powerdns' (1 of 8), version 0b80b3c198bf7abc6c81262013de494369fd25b6 OK
Job 'powerdns' checksum OK
Extract job 'powerdns' OK
Read job 'powerdns' manifest OK
Check template 'pdns.conf.erb' for 'powerdns' OK
Check template 'powerdns_ctl.erb' for 'powerdns' OK
Job 'powerdns' needs 'powerdns' package OK
Monit file for 'powerdns' OK
Read job 'blobstore' (2 of 8), version 815391c0ef26b0f1be488899cd5da9967f486d64 OK
Job 'blobstore' checksum OK
Extract job 'blobstore' OK
Read job 'blobstore' manifest OK
Check template 'nginx_ctl' for 'blobstore' OK
Check template 'nginx.conf.erb' for 'blobstore' OK
Check template 'blobstore.conf.erb' for 'blobstore' OK
Check template 'mime.types' for 'blobstore' OK
Check template 'read_users.erb' for 'blobstore' OK
Check template 'write_users.erb' for 'blobstore' OK
Job 'blobstore' needs 'nginx' package OK
Monit file for 'blobstore' OK
Read job 'nats' (3 of 8), version b619fdd39f344ee9fb1a760d0ade9ebf9ddcefe2 OK
Job 'nats' checksum OK
Extract job 'nats' OK
Read job 'nats' manifest OK
Check template 'nats_ctl.erb' for 'nats' OK
Check template 'nats.yml.erb' for 'nats' OK
Job 'nats' needs 'nats' package OK
Job 'nats' needs 'ruby' package OK
Monit file for 'nats' OK
Read job 'director' (4 of 8), version cc1da8b6e4aefd733c9bf4a9c49d7890cc1318d0 OK
Job 'director' checksum OK
Extract job 'director' OK
Read job 'director' manifest OK
Check template 'director_ctl' for 'director' OK
Check template 'director.yml.erb.erb' for 'director' OK
Check template 'worker_ctl' for 'director' OK
Check template 'drain' for 'director' OK
Check template 'sudoers' for 'director' OK
Check template 'stemcell-copy.sh' for 'director' OK
Check template 'task_logrotate.sh' for 'director' OK
Check template 'task_logrotate.cron' for 'director' OK
Check template 'director.pem.erb' for 'director' OK
Check template 'director.key.erb' for 'director' OK
Check template 'nginx.conf.erb' for 'director' OK
Check template 'nginx_ctl' for 'director' OK
Check template 'mime.types' for 'director' OK
Check template 'scheduler_ctl' for 'director' OK
Job 'director' needs 'director' package OK
Job 'director' needs 'nginx' package OK
Job 'director' needs 'genisoimage' package OK
Job 'director' needs 'libpq' package OK
Job 'director' needs 'postgres' package OK
Job 'director' needs 'mysql' package OK
Job 'director' needs 'ruby' package OK
Monit file for 'director' OK
Read job 'redis' (5 of 8), version 875d5cbc9a05a314777eda9b34fad421ad2458b0 OK
Job 'redis' checksum OK
Extract job 'redis' OK
Read job 'redis' manifest OK
Check template 'redis_ctl' for 'redis' OK
Check template 'redis.conf.erb' for 'redis' OK
Job 'redis' needs 'redis' package OK
Monit file for 'redis' OK
Read job 'registry' (6 of 8), version bd99def31c33f95278e8553cb8f21e3a5359e567 OK
Job 'registry' checksum OK
Extract job 'registry' OK
Read job 'registry' manifest OK
Check template 'registry_ctl' for 'registry' OK
Check template 'registry.yml.erb' for 'registry' OK
Job 'registry' needs 'registry' package OK
Job 'registry' needs 'libpq' package OK
Job 'registry' needs 'mysql' package OK
Job 'registry' needs 'ruby' package OK
Monit file for 'registry' OK
Read job 'postgres' (7 of 8), version 51a734cc3abb06ab6d2baf687b2b5e30dc4dd9b7 OK
Job 'postgres' checksum OK
Extract job 'postgres' OK
Read job 'postgres' manifest OK
Check template 'postgres_ctl.erb' for 'postgres' OK
Check template 'postgres.conf.erb' for 'postgres' OK
Job 'postgres' needs 'postgres' package OK
Monit file for 'postgres' OK
Read job 'health_monitor' (8 of 8), version cc4bac1157c2da7fc01274c134fdc67610cb1a0f OK
Job 'health_monitor' checksum OK
Extract job 'health_monitor' OK
Read job 'health_monitor' manifest OK
Check template 'health_monitor_ctl' for 'health_monitor' OK
Check template 'health_monitor.yml.erb' for 'health_monitor' OK
Job 'health_monitor' needs 'health_monitor' package OK
Job 'health_monitor' needs 'ruby' package OK
Monit file for 'health_monitor' OK
Release info
------------
Name: bosh
Version: 80
Packages
- nginx (383a4be04cc776893fd706d4d10aed713a6cae58)
- genisoimage (008d332ba1471bccf9d9aeb64c258fdd4bf76201)
- powerdns (8bb4936f87b4f893c9e6a5f9a096c0e174c94f0c)
- blobstore (9252bff62513e2f17e9f047c82e3903c7836c57d)
- ruby (81fe80099130f04dff2b08c80c04e0cb33a9d3ca)
- mysql (e5309aed88f5cc662bc77988a31874461f7c4fb8)
- nats (720422b1ba6adf981e83b46452106cbd0973e578)
- common (1324d32dbda40da88aade1e07b226a208602baff)
- director (036919ec39c1ff57d756fb644debadc361b99711)
- redis (ec27a0b7849863bc160ac54ce667ecacd07fc4cb)
- registry (ee7b41037e84d7db3141ff7dc5933114cbb8e570)
- libpq (6aa19afb153dc276924693dc724760664ce61593)
- postgres (aa7f5b110e8b368eeb8f5dd032e1cab66d8614ce)
- health_monitor (14d6a072430f6db80d92fa36422a700fd04bc97f)
Jobs
- powerdns (0b80b3c198bf7abc6c81262013de494369fd25b6)
- blobstore (815391c0ef26b0f1be488899cd5da9967f486d64)
- nats (b619fdd39f344ee9fb1a760d0ade9ebf9ddcefe2)
- director (cc1da8b6e4aefd733c9bf4a9c49d7890cc1318d0)
- redis (875d5cbc9a05a314777eda9b34fad421ad2458b0)
- registry (bd99def31c33f95278e8553cb8f21e3a5359e567)
- postgres (51a734cc3abb06ab6d2baf687b2b5e30dc4dd9b7)
- health_monitor (cc4bac1157c2da7fc01274c134fdc67610cb1a0f)
Checking if can repack release for faster upload...
nginx (383a4be04cc776893fd706d4d10aed713a6cae58) UPLOAD
genisoimage (008d332ba1471bccf9d9aeb64c258fdd4bf76201) UPLOAD
powerdns (8bb4936f87b4f893c9e6a5f9a096c0e174c94f0c) UPLOAD
blobstore (9252bff62513e2f17e9f047c82e3903c7836c57d) UPLOAD
ruby (81fe80099130f04dff2b08c80c04e0cb33a9d3ca) UPLOAD
mysql (e5309aed88f5cc662bc77988a31874461f7c4fb8) UPLOAD
nats (720422b1ba6adf981e83b46452106cbd0973e578) UPLOAD
common (1324d32dbda40da88aade1e07b226a208602baff) UPLOAD
director (036919ec39c1ff57d756fb644debadc361b99711) UPLOAD
redis (ec27a0b7849863bc160ac54ce667ecacd07fc4cb) UPLOAD
registry (ee7b41037e84d7db3141ff7dc5933114cbb8e570) UPLOAD
libpq (6aa19afb153dc276924693dc724760664ce61593) UPLOAD
postgres (aa7f5b110e8b368eeb8f5dd032e1cab66d8614ce) UPLOAD
health_monitor (14d6a072430f6db80d92fa36422a700fd04bc97f) UPLOAD
powerdns (0b80b3c198bf7abc6c81262013de494369fd25b6) UPLOAD
blobstore (815391c0ef26b0f1be488899cd5da9967f486d64) UPLOAD
nats (b619fdd39f344ee9fb1a760d0ade9ebf9ddcefe2) UPLOAD
director (cc1da8b6e4aefd733c9bf4a9c49d7890cc1318d0) UPLOAD
redis (875d5cbc9a05a314777eda9b34fad421ad2458b0) UPLOAD
registry (bd99def31c33f95278e8553cb8f21e3a5359e567) UPLOAD
postgres (51a734cc3abb06ab6d2baf687b2b5e30dc4dd9b7) UPLOAD
health_monitor (cc4bac1157c2da7fc01274c134fdc67610cb1a0f) UPLOAD
Uploading the whole release
Uploading release
bosh-2579.tgz: 100% |ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| 124.3MB 22.7MB/s Time: 00:00:05
Director task 2
Started extracting release > Extracting release. Done (00:00:01)
Started verifying manifest > Verifying manifest. Done (00:00:00)
Started resolving package dependencies > Resolving package dependencies. Done (00:00:00)
Started creating new packages
Started creating new packages > nginx/383a4be04cc776893fd706d4d10aed713a6cae58. Done (00:00:00)
Started creating new packages > genisoimage/008d332ba1471bccf9d9aeb64c258fdd4bf76201. Done (00:00:00)
Started creating new packages > powerdns/8bb4936f87b4f893c9e6a5f9a096c0e174c94f0c. Done (00:00:01)
Started creating new packages > blobstore/9252bff62513e2f17e9f047c82e3903c7836c57d. Done (00:00:00)
Started creating new packages > ruby/81fe80099130f04dff2b08c80c04e0cb33a9d3ca. Done (00:00:00)
Started creating new packages > mysql/e5309aed88f5cc662bc77988a31874461f7c4fb8. Done (00:00:00)
Started creating new packages > nats/720422b1ba6adf981e83b46452106cbd0973e578. Done (00:00:00)
Started creating new packages > common/1324d32dbda40da88aade1e07b226a208602baff. Done (00:00:00)
Started creating new packages > director/036919ec39c1ff57d756fb644debadc361b99711. Done (00:00:00)
Started creating new packages > redis/ec27a0b7849863bc160ac54ce667ecacd07fc4cb. Done (00:00:00)
Started creating new packages > registry/ee7b41037e84d7db3141ff7dc5933114cbb8e570. Done (00:00:01)
Started creating new packages > libpq/6aa19afb153dc276924693dc724760664ce61593. Done (00:00:00)
Started creating new packages > postgres/aa7f5b110e8b368eeb8f5dd032e1cab66d8614ce. Done (00:00:00)
Started creating new packages > health_monitor/14d6a072430f6db80d92fa36422a700fd04bc97f. Done (00:00:00)
Done creating new packages (00:00:02)
Started creating new jobs
Started creating new jobs > powerdns/0b80b3c198bf7abc6c81262013de494369fd25b6. Done (00:00:00)
Started creating new jobs > blobstore/815391c0ef26b0f1be488899cd5da9967f486d64. Done (00:00:01)
Started creating new jobs > nats/b619fdd39f344ee9fb1a760d0ade9ebf9ddcefe2. Done (00:00:00)
Started creating new jobs > director/cc1da8b6e4aefd733c9bf4a9c49d7890cc1318d0. Done (00:00:00)
Started creating new jobs > redis/875d5cbc9a05a314777eda9b34fad421ad2458b0. Done (00:00:00)
Started creating new jobs > registry/bd99def31c33f95278e8553cb8f21e3a5359e567. Done (00:00:00)
Started creating new jobs > postgres/51a734cc3abb06ab6d2baf687b2b5e30dc4dd9b7. Done (00:00:00)
Started creating new jobs > health_monitor/cc4bac1157c2da7fc01274c134fdc67610cb1a0f. Done (00:00:00)
Done creating new jobs (00:00:01)
Started release has been created > bosh/80. Done (00:00:00)
Task 2 done
Started 2014-05-28 18:48:32 UTC
Finished 2014-05-28 18:48:36 UTC
Duration 00:00:04
Release uploaded
To verify it succeeded and to grab the version number type bosh releases
administrator@originalbosh:/bosh/releases$ bosh releases +------+----------+-------------+ | Name | Versions | Commit Hash | +------+----------+-------------+ | bosh | 80 | 4fef83a2+ | +------+----------+-------------+ (+) Uncommitted changes Releases total: 1
For the next step we will need our director UUID. type in bosh status
administrator@originalbosh:/bosh/deployments$ bosh status
Config
/home/administrator/.bosh_config
Director
Name MicroBOSH01
URL https://192.168.50.166:25555
Version 1.2427.0 (release:921db96c bosh:921db96c)
User admin
UUID c7c0f4a5-3820-42d2-945d-e08103b5c06e
CPI vsphere
dns enabled (domain_name: microbosh)
compiled_package_cache disabled
snapshots disabled
Deployment
not set
4. Setup the BOSH Manifest file. go to the deployments folder and create a new folder called bosh and create a bosh.yml file
cd /bosh/deployments mkdir bosh cd bosh nano bosh.yml
5. Just like the yml from Step 1, the indentation needs to be precise. Replace UUID, BOSH Version number, IP addreses, Passwords, and vCenter information with your own. Copy and Paste (or download the yml below)
---
name: bosh
director_uuid: c7c0f4a5-3820-42d2-945d-e08103b5c06e
release:
name: bosh
version: 80
networks:
# all of these settings depend on your own infrastructure setup
- name: default
subnets:
- range: 192.168.50.0/24
reserved: #IPs that will not be used
- 192.168.50.2 - 192.168.50.100
static: #IPs assigned to individual VMs
- 192.168.50.141 - 192.168.50.149
gateway: 192.168.50.1
dns:
- 192.168.50.5
cloud_properties:
name: Servers #the portgroup where they will be deployed
resource_pools:
- name: small
stemcell:
name: bosh-vsphere-esxi-ubuntu
version: latest
network: default
size: 5
cloud_properties:
ram: 512
disk: 2048
cpu: 1
- name: director
stemcell:
name: bosh-vsphere-esxi-ubuntu
version: latest
network: default
size: 1
cloud_properties:
ram: 2048
disk: 8192
cpu: 2
compilation:
workers: 6
network: default
cloud_properties:
ram: 2048
disk: 4048
cpu: 4
update:
canaries: 1
canary_watch_time: 60000
update_watch_time: 60000
max_in_flight: 1
jobs:
- name: nats
template: nats
instances: 1
resource_pool: small
networks:
- name: default
static_ips:
- 192.168.50.142
- name: postgres
template: postgres
instances: 1
resource_pool: small
persistent_disk: 2048
networks:
- name: default
static_ips:
- 192.168.50.143
- name: redis
template: redis
instances: 1
resource_pool: small
networks:
- name: default
static_ips:
- 192.168.50.144
- name: director
template: director
instances: 1
resource_pool: director
persistent_disk: 2048
networks:
- name: default
static_ips:
- 192.168.50.145
- name: blobstore
template: blobstore
instances: 1
resource_pool: small
persistent_disk: 20480
networks:
- name: default
static_ips:
- 192.168.50.146
- name: health_monitor
template: health_monitor
instances: 1
resource_pool: small
networks:
- name: default
static_ips:
- 192.168.50.147
properties:
env:
blobstore:
address: 192.168.50.146
port: 25251
backend_port: 25552
agent:
user: agent
password: mysecretpw
director:
user: director
password: mysecretpw
networks:
apps: default
management: default
nats:
user: nats
password: mysecretpw
address: 192.168.50.142
port: 4222
postgres:
user: bosh
password: mysecretpw
address: 192.168.50.143
port: 5432
database: bosh
redis:
address: 192.168.50.144
port: 25255
password: mysecretpw
director:
name: BOSH-director
address: 192.168.50.145
port: 25555
encryption: false
db:
user: bosh
password: mysecretpw
host: 192.168.50.143
hm:
http:
port: 25923
user: admin #can be whatever
password: admin # can be whatever
director_account:
user: admin # can be whatever
password: admin # can be whatever
intervals:
poll_director: 60
poll_grace_period: 30
log_stats: 300
analyze_agents: 60
agent_timeout: 180
rogue_agent_alert: 180
loglevel: info
email_notifications: false # if this is false you don't need to worry about the smtp section below
email_recipients:
- #put your email here
smtp:
from: #put email here
host: smtp.kendrickcoleman.c0m
port: 25
auth: plain
user: kenny
password: mysecretpw
domain: kendrickcoleman.c0m
tsdb_enabled: false # it this is false you don't have to worry about the tsdb settings. Plus you can't set it to true until you have a complete Cloud Foundry running.
tsdb:
address: 172.20.218.14 # opentsdb static IP from your Cloud Foundry deploy (optional)
port: 4242
vcenter: # must match your vCenter info
address: kcvcenter.kendrickcoleman.c0m # IP or FQDN of vCenter
user: KENDRICKCOLEMAN\kcoleman # user name provisioned for BOSH
password: mysecretpw # passowrd for BOSH
datacenters:
- name: LouisvilleLab
vm_folder: bosh_vms
template_folder: bosh_templates
disk_path: microbosh_datastore
datastore_pattern: DS411_NFS_1
persistent_datastore_pattern: DS411_NFS_1
allow_mixed_datastores: true
clusters:
- ShuttleXPC:
resource_pool: bosh
6. Set the deployer and begin the deployment
bosh deployment bosh.yml bosh deploy
Here is the expected output. Remember to type yes to begin
administrator@originalbosh:/bosh/deployments/bosh$ bosh deployment bosh.yml
Deployment set to `/bosh/deployments/bosh/bosh.yml'
administrator@originalbosh:/bosh/deployments/bosh$ bosh deploy
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Compiling deployment manifest...
Cannot get current deployment information from director, possibly a new deployment
Please review all changes carefully
Deploying `bosh.yml' to `MicroBOSH01' (type 'yes' to continue): yes
Director task 3
Started preparing deployment
Started preparing deployment > Binding deployment. Done (00:00:00)
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done (00:00:00)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Done (00:00:00)
Started preparing deployment > Binding properties. Done (00:00:00)
Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
Started preparing deployment > Binding instance networks. Done (00:00:00)
Done preparing deployment (00:00:00)
Started preparing package compilation > Finding packages to compile. Done (00:00:00)
Started compiling packages
Started compiling packages > genisoimage/008d332ba1471bccf9d9aeb64c258fdd4bf76201
Started compiling packages > nginx/383a4be04cc776893fd706d4d10aed713a6cae58
Started compiling packages > mysql/e5309aed88f5cc662bc77988a31874461f7c4fb8
Started compiling packages > libpq/6aa19afb153dc276924693dc724760664ce61593
Started compiling packages > redis/ec27a0b7849863bc160ac54ce667ecacd07fc4cb
Started compiling packages > postgres/aa7f5b110e8b368eeb8f5dd032e1cab66d8614ce. Done (00:01:59)
Started compiling packages > ruby/81fe80099130f04dff2b08c80c04e0cb33a9d3ca
Done compiling packages > mysql/e5309aed88f5cc662bc77988a31874461f7c4fb8 (00:01:59)
Done compiling packages > libpq/6aa19afb153dc276924693dc724760664ce61593 (00:02:16)
Done compiling packages > genisoimage/008d332ba1471bccf9d9aeb64c258fdd4bf76201 (00:02:20)
Done compiling packages > redis/ec27a0b7849863bc160ac54ce667ecacd07fc4cb (00:02:28)
Done compiling packages > nginx/383a4be04cc776893fd706d4d10aed713a6cae58 (00:02:43)
Done compiling packages > ruby/81fe80099130f04dff2b08c80c04e0cb33a9d3ca (00:02:16)
Started compiling packages > health_monitor/14d6a072430f6db80d92fa36422a700fd04bc97f
Started compiling packages > director/036919ec39c1ff57d756fb644debadc361b99711
Started compiling packages > nats/720422b1ba6adf981e83b46452106cbd0973e578. Done (00:00:54)
Done compiling packages > health_monitor/14d6a072430f6db80d92fa36422a700fd04bc97f (00:01:26)
Done compiling packages > director/036919ec39c1ff57d756fb644debadc361b99711 (00:06:04)
Done compiling packages (00:10:19)
Started preparing dns > Binding DNS. Done (00:00:01)
Started creating bound missing vms
Started creating bound missing vms > small/0
Started creating bound missing vms > small/1
Started creating bound missing vms > small/2
Started creating bound missing vms > small/3
Started creating bound missing vms > small/4
Started creating bound missing vms > director/0
Done creating bound missing vms > small/3 (00:00:29)
Done creating bound missing vms > small/1 (00:00:30)
Done creating bound missing vms > director/0 (00:00:30)
Done creating bound missing vms > small/4 (00:00:30)
Done creating bound missing vms > small/2 (00:00:47)
Done creating bound missing vms > small/0 (00:00:48)
Done creating bound missing vms (00:00:48)
Started binding instance vms
Started binding instance vms > nats/0
Started binding instance vms > postgres/0
Started binding instance vms > redis/0
Started binding instance vms > director/0
Started binding instance vms > blobstore/0
Started binding instance vms > health_monitor/0
Done binding instance vms > postgres/0 (00:00:00)
Done binding instance vms > redis/0 (00:00:00)
Done binding instance vms > health_monitor/0 (00:00:00)
Done binding instance vms > director/0 (00:00:00)
Done binding instance vms > blobstore/0 (00:00:00)
Done binding instance vms > nats/0 (00:00:01)
Done binding instance vms (00:00:01)
Started preparing configuration > Binding configuration. Done (00:00:00)
Started updating job nats > nats/0 (canary). Done (00:01:07)
Started updating job postgres > postgres/0 (canary). Done (00:01:18)
Started updating job redis > redis/0 (canary). Done (00:01:06)
Started updating job director > director/0 (canary). Done (00:01:27)
Started updating job blobstore > blobstore/0 (canary). Done (00:01:20)
Started updating job health_monitor > health_monitor/0 (canary). Done (00:01:07)
Task 3 done
Started 2014-05-28 19:07:27 UTC
Finished 2014-05-28 19:26:01 UTC
Duration 00:18:34
Deployed `bosh.yml' to `MicroBOSH01'
7. to make sure it works, set the bosh target to your IP address and login. bosh target 192.168.50.145
administrator@originalbosh:/bosh/deployments/bosh$ bosh target 192.168.50.145 Target set to `BOSH-director' Your username: admin Enter password: ***** Logged in as `admin'
Awesome. Now on to Part 3
Part 1 - How to install MicroBOSH
Part 2 - Deploy BOSH with MicroBOSH
Part 3 - Deploy Cloud Foundry with BOSH