Changes from v0.1474.0 to v0.1475.0
- Verified with garden-linux-release v0.338.0.
- Verified with garden-runc-release v0.3.0.
- Verified with etcd-release v55.
- Verified with cflinuxfs2-rootfs-release v1.15.0.
Significant changes
IMPORTANT: The rep
job template now relies on a post-start script to verify that the rep process is healthy after being started. This feature requires a BOSH director at version 1.3213.0 or later, available in BOSH-release v255.4.
BBS Relational Datastore (Experimental)
- As a Diego operator, I should be able to follow documentation to deploy an HA standalone CF-MySQL cluster on my infrastructure
- As a Diego operator, I should be able to use Postgres as a backing relational store for the Diego BBS (in flight)
- As a Diego operator, I would like the examples/aws boosh-strapping to include subnets for MySQL in each AZ so that I do not have to create them manually
- As a Diego operator, I expect the BBS to recover from catastrophic data loss in the relational store so that the system remains functional (in flight)
- As a Diego operator, I would like the option to use the Postgres instance in the CF deployment as a relational backend for the BBS so that I do not have to deploy a separate deployment (in flight)
Performance Tuning
Garden-RunC Integration
Component Logging and Metrics
Security
Documentation
- The
ResolvingTask
andDeleteTask
methods should be included in theExternalTaskClient
BBS interface (in flight) - Document the public LRP API and related types on the BBS (in flight)
- Document additional Volume types and fields added with Persi work (in flight)
BOSH job changes
Added post-start script for rep
job template.
BOSH property changes
- Add
diego.bbs.sql.db_driver
: Driver for BBS to use against a SQL store.