diego/0.1469.0

Changes from v0.1468.0 to v0.1469.0

• Verified with garden-linux-release v0.337.0.
• Verified with etcd-release v45.
• Verified with cflinuxfs2-rootfs-release v1.1.0.

Significant changes

IMPORTANT: This version of Diego is vulnerable to CVE-2016-3091, which is related to the Diego executor’s parsing of log output at UTF-8 boundaries. We strongly recommend that all operators on Diego v0.1468.0 through v0.1470.0 upgrade to Diego v0.1471.0 or later. Diego v0.1472.0 is recommended for use with the recently released CF v237 and should be compatible with CF v236.

IMPORTANT: This version of Diego completes the extraction of the cflinuxfs2 rootfs to its own release. In order to deploy Diego for use by CF, upload the cflinuxfs2-rootfs release to your director and ensure that you are using the cflinuxfs2-rootfs-setup job from that release on the cells in place of the rootfses job. If you are installing additional certificates in the cflinuxfs2 trust store, change those certificates to be under the cflinuxfs2-rootfs.trusted_certs property instead. The diego-release manifest-generation scripts handle the job-template and property change transparently.

IMPORTANT: This version of Diego also removes the CC-Bridge jobs that were previously copied to capi-release and linked into cf-release. On the cc_bridge VMs in the Diego deployment, change the release of the cc_uploader, stager, nsync, and tps jobs from diego to cf. The diego-release manifest-generation scripts handle the job-template changes transparently. This version of Diego also then requires CF at version 236 or later for those jobs to be present and fully functional. For the time being, the BOSH properties for those jobs are the same, but an upcoming version of CF will change those properties from the diego namespace to capi.

BBS Benchmarks

• BBS benchmarks should include load from an event-stream subscriber

BBS Relational Datastore (Experimental)

• As a Diego operator, I should be able to generate a Diego manifest with connection info for a relational store
• SQL convergence: tasks with missing cells and tasks pending for too long should be marked completed
• LRP convergence in SQL should not error when emitting metrics when there are no desired LRPs
• Document BBS benchmarks configuration required to target either etcd or MySQL
• As a Diego developer, I expect inigo and component integration test suites to run against both MySQL and etcd in CI (in flight)
• As a Diego developer, I expect BBS unit tests to run against both MySQL and etcd in CI
• As a Diego operator, I should be able to follow documentation to provision an RDS MySQL instance to support my AWS Diego deployment

Volume Support (Experimental)

• Volume Drivers are discoverable
• Volume Drivers are activated the first time they are used
• Volume Driver requests are retried with backoff before failing
• Clean up certification suite so other teams can use it
• Refactor driver discovery so that driver registry is owned by volman and acted upon by the driver syncer
• Update Driver.Activate to return an array of ‘Implements’ as required by the docker spec
• Refactor Driver routes to actually match the docker volume API; i.e. /create -> /VolumeDriver.Create
• Volman can discover docker drivers in an ordered list of folders
• move system to gunk
• fix failing inigo volman tests

Rootfs Release Extraction

• Remove ‘rootfses’ job from diego-release

CC-Bridge Transfer

• CAPI Release - Diego can only use Bridge components from CF

Dependencies

• Update Golang in diego-release to 1.6.2+

Test Suites and Tooling

• Investigate Failed Units run 2330
• Fix race in bbs mysql cmd suite.

Cleanup

• Remove diego.rep.stack from rep job spec

BOSH job changes

• rootfses job deleted in favor of cflinuxfs2-rootfs-setup from the cflinuxfs2-rootfs release.
• cc-uploader job deleted in favor of cc-uploader from capi-release or cf-release.
• nsync job deleted in favor of nsync from capi-release or cf-release.
• stager job deleted in favor of stager from capi-release or cf-release.
• tps job deleted in favor of tps from capi-release or cf-release.

BOSH property changes

• Removed all properties under diego.cc_uploader.
• Removed all properties under diego.nsync.
• Removed all properties under diego.stager.
• Removed all properties under diego.tps.
• Removed diego.rep.stack property.
• Removed diego.rootfs_cflinuxfs2.trusted_certs property.
• Removed spec default of ["cflinuxfs2:/var/vcap/packages/rootfs_cflinuxfs2/rootfs"] for diego.rep.preloaded_rootfses.

- name: "diego"
  version: "0.1469.0"
  url: "https://bosh.io/d/github.com/cloudfoundry/diego-release?v=0.1469.0"
  sha1: "89d7d5cd923fdde62df061ffc6c36c64981f2bb3"

bosh upload-release --sha1 89d7d5cd923fdde62df061ffc6c36c64981f2bb3 \
  "https://bosh.io/d/github.com/cloudfoundry/diego-release?v=0.1469.0"