release: / 240

Github source: cf65a6e9 or master branch

The cf-release v240 was released on August 09, 2016.

Contents: - CC and Service Broker APIs - DEA-Warden-HM9000 Runtime - Buildpacks and Stacks - Identity - Routing - Loggregator - Internal Components - Job Spec Changes - Recommended BOSH Stemcell Versions - Recommended Versions of Additional Releases

CC and Service Broker APIs

Contains CAPI release v1.1.0. Release notes for v1.1.0

DEA-Warden-HM9000 Runtime

  • No changes

Buildpacks and Stacks


updated to 1.72.0 (from 1.69.0)





updated to v1.0.3 (from v1.0.2)



updated to v1.7.11 (from v1.7.8)





updated to v1.5.18 (from v1.5.15)





updated to v4.3.17 (from v4.3.14)





updated to v1.5.8 (from v1.5.7)



updated to v1.6.20 (from v1.6.19)



updated to v1.3.10 (from v1.3.9)



Updated to UAA release 3.4.2


Routing release bumped to 0.136.0 - Release Notes - Authors of components that use route-registrar can now provide a route_service_url so that requests to the route are proxied to the route service details - route-registrar process is no longer run as root details - route-registrar source has been moved to routing-release and is symlinked in cf-release details, more details


Internal Components

postgres-release (includes postgres job)

  • Extracted this release out of cf-release into its own separate release (with no functional changes). [repo][][details]

etcd-release (includes etcd and etcd_metrics_server jobs)

  • Bumped from v58 to v63. Functional changes:
    • Bumped version of Golang used by this release from 1.6.1 to 1.6.3 details

consul-release (includes consul_agent job)

  • Bumped from v92 to v101. Functional changes:
    • Fix consul_agent job when running on BOSH VMs with multiple dynamic networks. details
    • Bumped version of Golang used by this release from 1.6.1 to 1.6.3 details
    • BOSH manifest configuration for consul_agent job only requires certificates and keys necessary for the configured mode of operation, i.e. in “server” mode, client certificate and signing key does not need to be configured, and in “client” mode, server certificate and key does not need to be configured. details
    • The consul_agent job in server mode is now resilient to job name changes, to support transitioning from a “BOSH 1.0”-style deployment to a “BOSH 2.0”-style deployment that is likely to collapse multiple jobs across AZs into a single instance group using the migrated_from and azs features. details

nats-release (includes nats and nats_stream_forwarder jobs)

  • Bumped from 219e93bd to 6c1a563b. Functional changes:
    • Bumped version of Golang used by this release from 1.6.1 to 1.6.3 details

Job Spec Changes

  • Added cc.run_prestart_migrations (default true) that can be disabled on deployments where the CCDB is collocated with the Cloud Controller and is unavailable during pre-start.

Recommended BOSH Stemcell Versions

  • real IaaS: 3262.4
  • BOSH-Lite: 3262.2

Note: For AWS you should use the Xen-HVM stemcells rather than Xen.

These are soft recommendations; several different versions of the stemcells are likely to work fine with this version of cf-release and the corresponding versions of the additional releases listed below.

Recommended Versions of Additional Releases

These versions are soft recommendations, as several different versions of these releases may work correctly with this version of cf-release. - Diego release v0.1481.0. Release notes for v0.1481.0. - Garden-Linux release v0.339.0. Release notes for v0.339.0. - etcd release v63. Release notes for v63 · v62 · v61. - cflinuxfs2-rootfs release v1.21.0. Release notes for v1.20.0 · v1.19.0.

Upload this release version to the Director:

$ bosh upload-release --sha1 7dba7cc0c9c4beca699d8c876ac046890e13bb9e

Modify deployment manifest to use this release in addition to any other used releases:

- name: cf
  version: "240"

Finally add needed deployment jobs and specify values for required properties.

Optionally download sha1: 7dba7cc0c9c4beca699d8c876ac046890e13bb9e release tarball locally:

# ...or download it directly using curl
$ curl -L -J -O

# or with wget...
$ wget --content-disposition