Running Unmanaged VMs in a VCD Managed vCenter - Guidelines and Caveats

Products

• VMware Cloud Director

Issue/Introduction

• Need to clone or deploy VMs directly into a VMware vCenter linked to VMware Cloud Director
• Concerns about inventory mismatches or inconsistencies in VCD
• Desire to run workloads exclusively from vCenter without involving VCD

Environment

VMware vCenter Server

VMware Cloud Director

Cause

• This scenario arises when there may be a need to manage certain VMs natively in vCenter, bypassing VCD’s control.
• Without precautions, this can lead to inventory sync errors or unexpected VCD behaviour.

Resolution

It is possible to run non-VCD managed workloads in a vCenter instance that is also used by VCD.

However, to avoid issues:

• Do not use VCD-managed resource pools, folders, or networks, unmanaged VMs should be kept in separate clusters or resource pools.
• Avoid importing or creating these VMs through VCD, all actions should occur directly in vCenter.
• Ensure no VCD metadata is present, unmanaged VMs should not have a cloud.uuid set.
• Use distinct naming conventions for folders and resource pools to clearly separate managed and unmanaged workloads.
• Maintain clear separation of networking - unmanaged workloads should use their own network constructs, not those defined in VCD.
• Do not register these VMs with any VCD organisation or provider VDC.

Additional Information

Impact/Risks:

Mixing unmanaged VMs with VCD. managed resources can result in:

• Inaccurate inventory reporting
• VCD database inconsistencies
• Issues during VCD inventory sync or cleanup tasks
• Accidental deletion or mismanagement of resources

Best Practice:

Maintain dedicated vCenter environments for VCD managed and unmanaged workloads where possible. If sharing a vCenter is required, enforce strict boundaries between managed and unmanaged resources.

For further information, see: Managing Dedicated vCenter Server Instances in VMware Cloud Director