diego/0.1462.0
You can find the source of this version on GitHub at cloudfoundry/diego-release. It was created based on the commit 97ed8d35
.
Release Notes¶
Changes from v0.1461.0 to v0.1462.0
- Verified with garden-linux-release v0.335.0.
- Verified with etcd-release v43.
Significant changes
The Diego team is proceeding with experimental support for the BBS to use a relational database as its backing datastore, starting with support for MySQL. Work is currently proceeding in the BBS codebase, but we expect it to be exposed through BOSH configuration and manifest-generation in the near future. Please note that this work is strictly experimental and hence is not yet supported for production deployments.
This version of the Diego BOSH release also uses Golang 1.6 throughout. If you are building Diego components locally, please upgrade your Golang runtime to 1.6.
The Diego and Persi teams have been working on experimental support for volume mounts in the executor and the BBS. Any additions to the Diego APIs to enable this work are completely experimental and may change at any time.
The Buildpacks and Diego teams have started work to extract the ‘rootfses’ job in the Diego BOSH release into its own independent release. For now, Diego manifests can be used unchanged. If you are using the manifest-generation scripts and templates in diego-release, you can opt-in to using the new release with the -r
flag (don’t forget to create and upload the rootfs release before deploying!).
The CAPI and Diego teams have also started work to transfer the CC-Bridge jobs (stager, cc-uploader, nsync, and tps) from Diego to the new CAPI release. This transfer requires no manifest changes at present. Since the manifest-generation scripts already rely on the presence of a CF release and deployment, we expect to be able to make this transition transparent, with the option to opt-in early via a flag on the manifest-generation script.
BBS Relational Datastore (Experimental)
Performance Tuning
SSH
Volume Support (Experimental)
- tasks can create and mount a volume (in flight)
- LRPs can create and mount a volume (in flight)
- Volume Drivers have an HTTP transport using .json file (in flight)
- executor advertises available volume drivers (in flight)
Rootfs Release Extraction
- Extract diego-release ‘rootfses’ job and related packages and blobs into a cflinuxfs2-rootfs-release (in flight)
- cloudfoundry-incubator/diego-release #148: This is a work in progress to separate the rootfs bosh release
CC-Bridge Transfer to CAPI
- CAPI Release - CC Bridge components (in flight)
- fix app and task freshness bumping in nsync bulker
- refactor processor
Manifest Generation
- Ensure all diego-release job defaults are in the job specs, instead of in ERB or spiff templates (in flight)
- Change order of jobs in job template lists to start consul first
Dependencies
- Upgrade Golang in diego-release to 1.6+ (in flight)
- Upgrade cflinuxfs2 rootfs in diego-release to
1.47.0+1.48.0+
Documentation
Licensing
BOSH job changes
None.
BOSH property changes
- Added
diego.auctioneer.consul_agent_port
: Port on which the Auctioneer connects to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.bbs.consul_agent_port
: Port on which the BBS connects to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.cc_uploader.consul_agent_port
: Port on which the CC-Uploader connects to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.converger.consul_agent_port
: Port on which the Converger connects to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.file_server.consul_agent_port
: Port on which the File-Server connects to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.nsync.consul_agent_port
: Port on which the Nsync-Bulker and Nsync-Listener connect to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.rep.consul_agent_port
: Port on which the Cell Rep connects to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.route_emitter.consul_agent_port
: Port on which the Route-Emitter connects to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.ssh_proxy.consul_agent_port
: Port on which the SSH-Proxy connects to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.ssh_proxy.allowed_ciphers
: Allowed cipher algorithms for connections to the SSH-Proxy. - Added
diego.ssh_proxy.allowed_macs
: Allowed MAC algorithms for connections to the SSH-Proxy. - Added
diego.ssh_proxy.allowed_keyexchanges
: Allowed key-exchange algorithms for connections to the SSH-Proxy. - Added
diego.stager.consul_agent_port
: Port on which the Stager connects to the HTTP API of the local consul agent. Defaults to 8500. - Added
diego.tps.consul_agent_port
: Port on which the TPS-Listener and TPS-Watcher connect to the HTTP API of the local consul agent. Defaults to 8500.
Usage¶
You can reference this release in your deployment manifest from the releases
section:
- name: "diego" version: "0.1462.0" url: "https://bosh.io/d/github.com/cloudfoundry/diego-release?v=0.1462.0" sha1: "e34152798fbc6938bb2c6c471041780e07130380"
Or upload it to your director with the upload-release
command:
bosh upload-release --sha1 e34152798fbc6938bb2c6c471041780e07130380 \ "https://bosh.io/d/github.com/cloudfoundry/diego-release?v=0.1462.0"
Jobs¶
- auctioneer
- bbs
- benchmark-bbs
- canary
- cc_uploader
- converger
- file_server
- nsync
- rep
- rootfses
- route_emitter
- ssh_proxy
- stager
- tps
- vizzini