About VMware vCenter Server Integration

 

Cloud Automation Platform integrates with VMware vCenter Server to provide several features. Primarily, a ESX and ESXi virtualization host can be registered with both Cloud Automation Platform and VMware vCenter. Additionally, Cloud Automation Platform can import VMware vCenter Server virtual machine templates into the Cloud Automation Platform environment, and export Cloud Automation Platform server configurations into vCenter as templates.

 

Important Considerations:

 

  • The ESX and ESXi hosts that will be used in both Cloud Automation Platform and vCenter environments must:

 

  • The VMs that are used in both Cloud Automation Platform and vCenter environments:
    • Cannot have had the vCenter "Convert to Template" option applied
    • Cannot use the legacy single-file format (i.e., do not use any version earlier than ESX 3.5)
    • Cannot use vMotion on any VMs pooled and used by Cloud Automation Platform: policy is automatically modified to disable vMotion
    • Cannot be placed in VMware Resource Pools. (i.e., VMs managed by Cloud Automation Platform may only be put into Cloud Automation Platform resource pools)
    • Cannot be placed in VMware folders (although hosts can be)
    • Can be spread across multiple VMware data centers.

 

Notes:

  • Refer to the Installation and Administration Guide for details about supported versions of ESX.
  • Quest Software recommends that you use the Surgient_Image_Tool.iso to prepare VMware vCenter Server virtual machine templates before importing them into the Cloud Automation Platform environment.

 

For more information about how Cloud Automation Platform integrates with VMware vCenter Server, see:

 

 

Related Topics