bosh/262
You can find the source of this version on GitHub at cloudfoundry/bosh. It was created based on the commit 59545a5.
Release Notes¶
New Features:
- Integration with upcoming
bbrbinary for backups/restore- Added
bin/bbr/backupandbin/bbr/restorescripts to director and blobstore jobs
- Added
- Integration with CredHub for secure configuration management (docs coming)
- Added
variablesCLI command to list which variables are in use by a deployment
- Added
- Added
orphan-diskCLI command - Added
eventCLI command - Tag persistent disks via
set_disk_metadataCPI call - Added
bosh.releases.uploadandbosh.stemcells.uploadUAA scopes to allow release and stemcell uploads - Added ability to specify deployment level addons in the deployment manifest
Enhancements:
- Continued improving DNS functionality in the Director
- Correctly clean up DNS blobs periodically
- Parallelized scanning of persistent disks in cloud check
- Allow export of compiled releases against same stemcell in parallel
- [breaking] Required Director SSL certificates to be always specified
director.ssl.certanddirector.ssl.keyproperties- It’s recommended to use
cloudfoundry/bosh-deploymentrepository for managing Director manifest
- Improve handling of Health Monitor meltdown state
- [breaking] Removed
postgresjob in favor of usingpostgres-9.4- Please use
postgres-9.4job if you haven’t done already.
- Please use
- Fixed date header in HM email plugin to conform with RFC5322
- Now storing tasks event and result log in the Database
- Related to future clustered Director work
- Record events when running errands
- Record Blobstore logs in Common Event Format (CEF)
- Record Director and worker start up events
Fixes:
- Fixed bug in
bosh cleanupto avoid having to re-run it again immediately - Stopped producing spurious HM alerts when SSH-ing to VMs
- [breaking] Changed
object_idtoobject_namein/eventsendpoint - Correct an edge case when IP may have been switched for instance without need
- Stopped orphaning new persistent disks if mounting fails
Usage¶
You can reference this release in your deployment manifest from the releases section:
- name: "bosh" version: "262" url: "https://bosh.io/d/github.com/cloudfoundry/bosh?v=262" sha1: sha256:
Or upload it to your director with the upload-release command:
bosh upload-release --sha1=sha256: \ "https://bosh.io/d/github.com/cloudfoundry/bosh?v=262"