updated nats to 0.4.22

Change-Id: I21756e1416076e207443967d94345d4b985566a9
Release composition support

Previously BOSH Director assumed only one release being referenced
in the deployment manifest. This change allows the deployment to
contain jobs from multiple releases.

Deployment manifest now supports 'releases' section where multiple
releases can be referenced: if this section is present, every job
needs to have a reference to its release.

This change should be fully backward compatible with old deployment
manifests.

Test plan:

- tested with cf-release only (using old manifest);
- tested a combination of cf-release, bosh-release and oss-release.

Things to be aware of:

- the very first bosh deployment with this version of director will
  trigger updating all jobs, as job state now has slightly different
  key set;

- properties are still global to the whole deployment, so if job
  templates from the different releases use the same property name
  having different semantics, it should be overriden for the
  individual job in the manifest.

Example manifest section:

releases:
- name: release-1
  version: 1
- name: release-2
  version: 4

...

jobs:
- name: foo
  release: release-1
  template: bar
  ...

- name: baz
  release: release-2
  template: zaz
  ...

Change-Id: Ib268ac09eb361a8f77f20fd7f3f1469344497d73
pass env configuration param to create_vm

Change-Id: I51c53403c578fbe38cdd21a116f4cc7816eaee08
Merge "Release composition support"
disk locality in aws (CF-13)

- create_vm() uses disk_locatility as az, explicit setting or default az
  - raises an error unless all specifed availability zones are the same
- create_disk() uses az from supplied instance or default az if none is given
- fixes https://cloudfoundry.atlassian.net/browse/CF-13

Change-Id: I17c07e0a629ba5df6cc2d9ef28b8bcc38febb35c
Changes to rename job

The agent change is to fix the following.

In this example I renamed postgresql_node to postgresql_db.

root@dfebf955-73e5-4708-bb20-0461cb693583:/var/vcap/monit/job# ls -l
total 4
lrwxrwxrwx 1 root root 60 2012-05-09 22:51 postgresql_db.monitrc ->
/var/vcap/data/jobs/postgresql_node/12/postgresql_db.monitrc

Today we delete the symlink but not the target of the symlink, with this change
we delete the target as well.

Usage:
To rename a job. The user does 2 things.
1. Updates his deployment manifest with the new name of the job to be renamed.
2. Runs, bosh rename <old_job_name> <new_job_name>

Testing Done:
Renamed services jobs. Verified that cf apps using the service were not
affected.

patch to try to retrigger build

Change-Id: I8f1817d0fb1fc4b95d7d46b501bdcbded38066ce
Use final release version as base for dev version

Change-Id: I0eab53f2d51b9c51c1a16bd706d2d5e651cb19e5
Merge "updated nats to 0.4.22"
Merge "Use final release version as base for dev version"
Fix bosh vms --full output column headers

Change-Id: Ie953de8bdd34eee43e4d780cc0e9d859c5d0ac1b
Merge "Changes to rename job"
Merge remote-tracking branch 'upstream/master' into openstack
fix biff to handle booleans correctly

Change-Id: I5bcf878ca1395985a813e09db7deec3468d46c4e
Merge "fix biff to handle booleans correctly"
Decapitalize Infrastructure::Openstack class
Merge remote-tracking branch 'upstream/master' into openstack
Add grub
Delete kvm hypervisor
Build chroot tgz: add optional infrastructure argument

When building a chroot tgz via rake task, be able to optionally
specify the infraestructure target (vsphere, aws or openstack).
Actually you can only build for vsphere.
Include the infrastructure name in the resulting tar file