Minor patch of vCloud Availability 2.0.1 was released last week. Besides many bug fixes, improved documentation and support for Cassandra version 3.x I want to highlight two undocumented features and add upgrade comment.
Provider vSphere Web Client Plugin
This is a return from 1.0 version of an experimental feature, where the provider can monitor state of vSphere Replication Manager Server, vSphere Replication Servers and all incoming and outgoing replications from inside the vSphere Web Client plugin in the particular (provider side) vCenter Server. This is especially useful for quick troubleshooting.
Complex vSphere SSO Domain Support
Although it is not recommended to have multiple vCloud Director / vCloud Availability instances sharing the same vSphere SSO domain, it is now possible to accommodate such scenario. The reason why it is not recommended is, that it creates unnecessary dependency between the instances, limits upgradability and scale of each instance.
Upon startup vSphere Replication Cloud Service (vRCS) is querying SSO Lookup Service for Cassandra nodes and resource vCenter Servers. In order to limit the scope of such query to only those that belong to the particular vCloud Availability instance, create text file /opt/vmware/hms/conf/sites on all vRCS nodes with SSO site names that should be queried (one line per site).
There might be some confusion between vCenter SSO domain and vCenter SSO site. vCenter SSO domain name is usually vsphere.local and the domain is defined by the span of all replicated PCSs. Any single node contains all replicated data, such us IdP configurations, lookup service registrations, solution users, tags, license information, etc.
vCenter SSO domain can contain multiple SSO sites. The first site name is defined with the first PSC deployment (in vSphere 6.7 the default name is default-site).
The other SSO sites are created when joining an existing SSO domain.
So based on the example above, the /opt/vmware/hms/conf/sites file could have single line with text string default-site. vRCS will then ignore any other SSO sites in this vsphere.local domain.
You can upgrade to vCloud Availability 2.0.1 both from version 1.0.x and 2.0, however you need to use different upgrade ISO images for upgrading of the replication components (vRMS, vRCS and vRS). The installer and UI appliances are redeployed fresh as they are all stateless.