bosh/255.4
You can find the source of this version on GitHub at cloudfoundry/bosh. It was created based on the commit e628c2a0
.
Release Notes¶
New Features:
- Added addons
- Switched to using instance IDs in the Health Monitor
- Potentially breaks backwards compatibility in how alerting/monitoring destination is expecting HM events
- director.remove_dev_tools
property forces removal of dev tools (e.g. compilers) from non-compilation VMs
- Currently defaults to false
but eventually will be turned on by default
- Only newer stemcells follow this configuration
- director.generate_vm_passwords
property forces generation of unique VM passwords
- Generated passwords are not stored so bosh ssh
CLI command remains the primary way to SSH into the VMs
- Currently defaults to false
but eventually will be turned on by default
- env.http_proxy
property can be set for the Director and Health Monitor
- Switched to using instance groups
vs jobs
in error messages
- Show deployment name for each Director tasks in bosh tasks
CLI command
- Already existing tasks will not be updated
- Added VM extensions (docs coming) to pull out IaaS specific configuration
- spec.address
accessor can be used to access default IP address of the job
- director.enable_post_deploy
property allows to run post-deploy
scripts
- Currently defaults to false
but eventually will be turned on by default
- bosh attach disk
CLI command allows to attach orphaned disks to stopped instances
- Added new level of Director UAA scoping for future service brokers
- Clients and users with bosh.teams.X.admin
will only see deployments that belong to team X
Improvements:
- --no-redact
for the bosh deploy
CLI command to show all property values
- Make registry for resilient to network failures on AWS when fetching IAM credentials via IAM instance profile
- Updated postgres-9.4
job to use Postgres 9.4.6
- You can opt into using this job in the manifest by removing postgres and adding postgres-9.4
- bosh logs
CLI command now works while deploy is in progress
- Remove bosh validate job
CLI command
- blobstore.s3_signature_version
property forces specific S3 signing algo
- director.workers
property forces
- Resurrector tasks report error at the end if any resolutions failed
- Allow instance groups with 0 jobs
- Show as many template rendering errors as possible
Fixes: - Redact multi-line properties - Redact properties recursively through arrays and hashes in properties - Transitive dependencies of packages are correctly calculated when importing compiled releases
Dev:
- Added BOSH_MICRO_ENABLED
env variable to disable builtin release building
- Disables bosh Ruby and prebuilt archive
- Log lock id when trying to acquire the lock
- Use stemcell name in place of operating system if operating system is not supplied in the stemcell’s stemcell.MF
- Added stemcell verification tests for stigs: V-38603, V-38604, V-38500, V-38582, V-38605, V-38609, V-38671
Usage¶
You can reference this release in your deployment manifest from the releases
section:
- name: "bosh" version: "255.4" url: "https://bosh.io/d/github.com/cloudfoundry/bosh?v=255.4" sha1: "d921c3ee7c570d3277eec8c5a15b33bc5f73cc94"
Or upload it to your director with the upload-release
command:
bosh upload-release --sha1 d921c3ee7c570d3277eec8c5a15b33bc5f73cc94 \ "https://bosh.io/d/github.com/cloudfoundry/bosh?v=255.4"