BOSH is an open source tool for release engineering, deployment, lifecycle management, and monitoring of distributed systems. We will install BOSH server (Director) using BOSH CLI. Once VM with Director is running we are going to use BOSH CLI to send commands to the Director.
How it works
Example component interaction; how components interact when creating a new VM.
- Through the CLI, the
operatortakes an action (
scale up) which requires creating a new VM in the cloud.
- The CLI passes the instruction to the
Spotinstto launch an EC2 Instance.
Spotinstprovides the Director with information (IP addresses and IDs).
CPIto update the Registry with the configuration information for the EC2 Instance.
- The Agent running on the VM requests the configuration information for the VM from the Registry.
- The Registry responds with the IP addresses and IDs.
- The Agent uses the IP addresses and IDs to configure the VM.
BOSH CLI is a command line interface to the Director. Follow these instructions to install it.
2. Setup IaaS providers
Clone the Director templates
git clone https://github.com/cloudfoundry/bosh-deployment deployment
3. Setup BOSH environment & Download the Spotinst Manifest
An environment consists of the Director and deployments that it orchestrates. First, we need to deploy the Director which then would be able to manage other deployments.
We are going to use
bosh create-env command to install the Director.
bosh create-env command provides a way to install initial VM with BOSH Director on any IaaS. In our case, we will use both Spotinst and AWS as our infrastructure providers.
First, get configuration files for your BOSH environment and run
bosh create-env as follows:
$ git clone https://github.com/cloudfoundry/bosh-deployment deployment
Then, download the
Spotinst CPI manifest.
# wget http://spotinst-public.s3.amazonaws.com/integrations/bosh/aws/cpi.yml
The Spotinst CPI exposes several cloud properties that can be configured in the VM Types section. For example:
vm_types: - name: default cloud_properties: instance_type: m3.medium availability_zone: us-east-1a spotinst_product: Linux/UNIX spotinst_risk: 100
spotinst_product [String, optional]: Product name. Defaults to
Linux/UNIX (can be set to
Linux/UNIX (Amazon VPC) if your account has both EC2 VPC and EC2 Classic platforms).
spotinst_risk [Integer, optional]: The percentage of Spot instances that would spin up from the target capacity. Set to 0 to use On-Demand instances. Defaults to
100 (all instances should be Spot).
spotinst_disabled [Boolean, optional]: Set to
true to disable the Spotinst CPI for a specific deployment. Defaults to
false (use Spotinst CPI always).
4. Create a new state directory
Create a new state directory. This state is used by BOSH to store information about your BOSH Director, keep track of both managed infrastructure and configuration.
$ mkdir state
5. Create a new variables file
Create a new variables file. For example,
export SPOTINST_TOKEN="redacted" export SPOTINST_ACCOUNT="act-12345" export AWS_ACCESS_KEY="AKI..." export AWS_SECRET_ACCESS_KEY="redacted" export AWS_REGION="us-west-2" export AWS_ZONE="us-west-2a" export AWS_KEY_NAME="key" export AWS_SECURITY_GROUPS="[bosh]" export AWS_SUBNET_ID="subnet-12345" export AWS_ELASTIC_IP="188.8.131.52" export SSH_PRIVATE_KEY="/path/to/private.key"
6. Create a new environment
Finally, create the environment using
$ source .envrc && bosh create-env deployment/bosh.yml \ --state state/state.json \ --vars-store state/creds.yml \ -o cpi.yml \ -o deployment/external-ip-with-registry-not-recommended.yml \ -o deployment/jumpbox-user.yml \ -v director_name=bosh-aws \ -v internal_cidr=10.0.0.0/24 \ -v internal_gw=10.0.0.1 \ -v internal_ip=10.0.0.6 \ -v spotinst_token=$SPOTINST_TOKEN \ -v spotinst_account=$SPOTINST_ACCOUNT \ -v access_key_id=$AWS_ACCESS_KEY \ -v secret_access_key=$AWS_SECRET_ACCESS_KEY \ -v region=$AWS_REGION \ -v az=$AWS_ZONE \ -v default_key_name=$AWS_KEY_NAME \ -v default_security_groups=$AWS_SECURITY_GROUPS \ -v subnet_id=$AWS_SUBNET_ID \ -v external_ip=$AWS_ELASTIC_IP \ --var-file private_key=$SSH_PRIVATE_KEY
7. Configure an alias for your environment
Once the instance with BOSH Director is running, point your CLI to it, saving the environment with the alias
$ bosh -e $AWS_ELASTIC_IP alias-env spotinst --ca-cert <(bosh int state/ creds.yml --path /director_ssl/ca)
8. Log into your Director
$ export BOSH_CLIENT=admin $ export BOSH_CLIENT_SECRET=$(bosh int state/creds.yml --path / admin_password) $ bosh -e spotinst login
Now we are ready to deploy!
Each BOSH deployment needs to provide a specially structured configuration file – deployment manifest. This file defines what resources are going to be deployed, what services are going to be running on each of resources and properties that will be passed to services configuration files.
Here is an example to deploy a simple
First, we need to upload Stemcell. A Stemcell is an operating system image that BOSH uses to create VMs.
$ wget --content-disposition https://s3.amazonaws.com/bosh-aws-light-stemcells/light-bosh-stemcell-3541.2-aws-xen-hvm-ubuntu-trusty-go_agent.tgz $ bosh -e spotinst upload-stemcell light-bosh-stemcell-3541.2-aws-xen-hvm- ubuntu-trusty-go_agent.tgz
Then, we need to download the Zookeeper deployment.
$ wget https://raw.githubusercontent.com/cppforlife/zookeeper-release/master/manifests/zookeeper.yml
And finally, we can run deploy by providing a path to deployment manifest.
$ bosh -e spotinst -d zookeeper deploy zookeeper.yml