Create a Deployment Manifest for Cloud Foundry on BOSH-Lite
Page last updated:
If you deploy BOSH-Lite to an AWS Vagrant VM, you must specify a system domain in a manifest stub. If you are deploying to a local Vagrant VM this step is not necessary.
By default, BOSH-Lite uses the system domain
bosh-lite.com, which resolves
to the address
10.244.0.34. Update the system domain property to one of the
following two values:
- The domain that you configured to point to the public IP address of the BOSH-Lite box that you previously created.
xip.iodomain the corresponds to the public IP address given to your BOSH-Lite vagrant box:
YOUR_PUBLIC_IP.xip.io. For more information about xip.io, see xip.io.
--- properties: system_domain: bosh-lite.com # Replace with your system domain
bosh alias-env command with the address of your BOSH Director to
connect to the BOSH Director. Log in with the default user name and password,
admin, or use the username and password that you set when you
$ bosh -e MY-ENV alias-env https://bosh.my-domain.example.com Your username: admin Enter password: ***** Logged in as 'admin'
$ git clone https://github.com/cloudfoundry/cf-release.git
Ensure that you have the most up-to-date version of the Cloud Foundry code and all required submodules.
cf-releasedirectory that you cloned when you created the manifest, run the update script to fetch all the submodules.
$ cd cf-release $ ./scripts/update
gem install bundlerto install bundler.
scripts/generate-bosh-lite-dev-manifestcommand to create a deployment manifest and set it as the current BOSH deployment.
$ cd cf-release $ ./scripts/generate-bosh-lite-dev-manifest
(Optional) If you have deployed your BOSH-Lite to AWS, or have otherwise created any stubs with custom configuration, you should pass them as additional arguments:
$ ./scripts/generate-bosh-lite-dev-manifest PATH-TO-STUB ...
(Optional) If you want to deploy container-to-container networking, see the Enable on BOSH-Lite section of the Administering Container-to-Container Networking topic.