Releases: cloudfoundry/bosh-openstack-cpi-release
Releases · cloudfoundry/bosh-openstack-cpi-release
v25
Fixes:
New Features:
- Define root disk size in deployment manifest (#35 thanks @kanekoh and @dkoper)
- Example of an
m1.small
instance with custom root disk size of 50GB:
- Example of an
resource_pools:
- name: default
network: default
stemcell:
name: bosh-openstack-kvm-ubuntu-trusty-go_agent
version: latest
cloud_properties:
instance_type: m1.small
availability_zone: east
root_disk:
size: 50
Misc:
- Switch to
block_device_mapping_v2
forboot_from_volume: true
(#33 thanks @dkoper and @kanekoh) - Bumped to fog-openstack 0.1.6
- changes endpoint for
boot_from_volume: true
to/servers
- removes dependency to fog-xml and nokogiri. Faster installations, yay!
- changes endpoint for
- Get rid of development dependencies in distributed release. (#32 thanks @coreyti, @ljfranklin, and @friegger)
- Release size down to ~16MB from ~31MB
v24
- Support for multiple manual networks
- Use VM names provided by BOSH
- When using
human_readable_vm_names: true
, VM names now use instance ids instead of index if the Director provides them
- When using
- Remove
ca_cert
content from excon debug logs
v23
- Human-readable VM names -
The CPI can set more meaningful names for VMs now! Instead of UUIDs such asvm-4971ee11-f956-406f-9220-8e1ee1a1873c
you get names such asrunner_z1/0
- set
openstack.human_readable_vm_names: true
- configure your registry with the
registry.endpoint
property to include basic auth credentials - Existing VMs will not be touched, continue to work, and still have their UUID-based name
- set
- Custom RootCA support for OpenStack Endpoints - If you previously set
openstack.connection_options.ssl_validate_peer: false
, you can now provide your custom RootCA certificate instead!- Set
openstack.connection_options.ca_cert
to the necessary certificate(s) - configure your registry with the
registry.endpoint
property to include basic auth credentials
- Set
v21
- Support for Bosh blobstore in AWS S3 regions China and Frankfurt (which require version 4 signing), thanks @flawedmatrix
- Added new manifest properties
blobstore.s3_region
andblobstore.s3_signature_version
- Added new manifest properties
v20 – DO NOT USE
Due to a bug in our continuous integration pipeline this release is broken. DO NOT USE.
v19 – DO NOT USE
Due to defaults set in the CPI deployment manifest, this release might break compatibility with older stemcells, if you use an external blobstore for your Director. DO NOT USE.
v18
- bump httpclient to 2.7.1, thanks @coreyti and @ljfranklin!
- Improved error messages
v17
- Support PowerPC, thanks @hashmap!
- Improve
Entity Too Large
error message - Make test pipeline setup easier to have it run against your own OpenStack installation
v16
- Renamed job
cpi
toopenstack_cpi
- Note: This breaks current bosh-init deployment manifests! Be sure to change
director.cpi_job
,cloud_provider.template
, andtemplates
properties to specifyopenstack_cpi
.
- Note: This breaks current bosh-init deployment manifests! Be sure to change
- User can specify security groups on
resource_pool
- You can still use existing manifests which specify security_groups on the network. See docs.
- Note: After implementing this feature we have removed configure_networks CPI implementation which means that changing floating IP for a VM will actually recreate that VM
v15
- Keystone v3 support
- Adds
openstack.domain
andopenstack.project
properties
- Adds