Releases: cloudfoundry/bosh-vsphere-cpi-release
v57
Known Issues
When use_policy_api
is set to true
and NSGroups are used, deleting VMs may fail with the error Invalid expression node count X in group. Total count of operators and operands in expression should be an odd number.
, due to a bug in NSgroup membership expression logic. This bug is corrected in v62
Notes
[Feature] When using NSX-T Policy mode, metadata is set on the NSX-T segment ports of BOSH-deployed VMs. Metadata includes the default BOSH metadata (e.g. the keys "deployment", "index", "instance_group", etc.) as well as any top-level tags. Note that metadata is a key/value pair, and the on the NSX-T segment, the key (called "Scope" in NSX-T) is always prepended with "bosh/".
v56
Known Issues
When use_policy_api
is set to true
and NSGroups are used, deleting VMs may fail with the error Invalid expression node count X in group. Total count of operators and operands in expression should be an odd number.
, due to a bug in NSgroup membership expression logic. This bug is corrected in v62
Notes
[Bug Fix] url-encode square brackets for NSX-T group names when Policy API is enabled.
[Feature Enhancement] Add the ability to add/remove VMs from server pools when using Policy API.
v55
Known Issues
When use_policy_api
is set to true
and NSGroups are used, deleting VMs may fail with the error Invalid expression node count X in group. Total count of operators and operands in expression should be an odd number.
, due to a bug in NSgroup membership expression logic. This bug is corrected in v62
Notes
[Bug Fix] When the cluster-VM affinity type is "should", consider the entire cluster's hosts and resources available for selecting placement into the cluster.
[Feature] Add experimental support for NSX-T Data Center's new Policy API.
- To use the Policy API select the CPI property,
use_policy_api
. - The first feature to use this API is NS Groups.
v54.1.1
v54.1.0
- Support for a Network name that matches multiple distributed virtual port groups with CVDS.
- If all the port groups are backed by the same NSX-T logical switch with VDS 7 - CPI will not throw "Multiple networks found" error.
v54
Bugs
- Fixes File uploads by trying through a host that is under BOSH orchestration.
- Provides absolute fallback to vCenter in case of upload through host fails.
- PKS 341, PKS 433, PKS 507
The change causes CPI to return disk UUID instead of SCSI Unit number when disk.EnableUUID (advanced vmx option) is set on a VM. - Fixes a race condition when trying to find a network.
- Retries ~10 minutes to find a network
NSXT
- Enables remote authentication for NSX-T via vIDM.
- NSX-T Cert/Key auth
- Support NSXT 3.0 on VDS 7.0 (VC 7.0)
VC
- Multi SDK support for VC (7.0, 6.7 and 6.5)
- Makes host group - VM group affinity configurable with MUST(mandatory) vs SHOULD(prescriptive).
- Adds support for VC 7.0 and NSXT 3.0
Misc
- Bump cpi ruby release to ruby-2.6.5-r0.29.0
- General CI & Test Improvements
v53.0.11
v53.0.9
Adds support for VC 7.0 and NSXT 3.0
Fixes deployment problem in v53.0.8
v53.0.8
DO NOT USE - ISSUES WITH DEPLOYMENT
Adds support for VC 7.0 and NSXT 3.0
Changes are backward compatible for VC6-7 and NSXT2.3+
v53.0.7
BACKWARD COMPATIBLE WITH OLD HOST GROUP FORMAT
Makes host group - VM group affinity configurable with MUST(mandatory) vs SHOULD(prescriptive).
Makes SHOULD as the default.
SHOULD rule allows VMs to fail-over from a non-functional host group while MUST does not.
Sample Cloud Config
azs:
- name: z1
cloud_properties:
datacenters:- clusters:
- vcpi-cluster-1: {host_group: {name: 'vcpi-cl1-hg-1', drs_rule: 'MUST'}}
- clusters:
- name: z2
cloud_properties:
datacenters:- clusters:
- vcpi-cluster-1: {host_group: {name: 'vcpi-cl1-hg-1', drs_rule: 'should'}}
- clusters: