Renaming VCF SDDC manager objects

Products

• VMware Cloud Foundation

Issue/Introduction

VCF design in versions up to VCF 5.2 relies on the names of various SDDC objects, including compute clusters, datacenters, DVS, portgroups, datastores, and NSXT edge clusters, for configuration and lifecycle management. However, customers express a desire to rename these objects once they have provisioned clusters and resources.

This renaming capability allows them to organize their workloads into different categories and adhere to organizational naming conventions.

Nonetheless, the automation of VCF workflows and inventory heavily depends on the names of these objects to facilitate various use cases such as cluster expansion, shrinkage, lifecycle management, and vxrail integration.

This document, subjected to change, serves as a comprehensive reference guide outlining which objects can be renamed and the extent of support provided by SDDC Manager.

Resolution

In VCF versions up to VCF 5.1, only 3 objects can be renamed as a supported feature from SDDC manager, find the details below

• Workload Domain rename
• vSphere cluster rename
• Network Pool rename

Find the list of components that cannot be renamed. It is important to note that steps exists but implementing these below object renaming would result in an unsupported configuration, potentially leading to unforeseen implications in Day N workflows since it would need to be subjected to extensive testing.

• ​​​​​​​Fault domains should not be renamed ​​​​​​​
• DVS and its port group renaming from vSphere cluster is not supported and will cause issues for SDDC manager upgrades.
• NSXT edge cluster renaming is not allowed
• None of the components of VSAN ready node

As per the VCF 5.2 Release Notes it is supported to make out of band changes to the vCenter inventory in VCF 5.2 and later, including renaming components such as datacenter and datastore objects. After changing the object name in vCenter, the change should be automatically reflected in SDDC Manager.