Updated for Cloud Foundation 5.2.1.1
Refer to the New Features Available with the VMware Cloud Foundation Import Tool blog post to learn about the last updates available with VCF 5.2.1.1.
VMware Cloud Foundation (VCF) 5.2 introduced the VCF Import Tool, a command-line interface (CLI) designed to streamline the transition to a private cloud. This tool extends SDDC Manager’s fleet management capabilities—such as certificate management, password management, and lifecycle management—to existing vSphere or vSphere with vSAN deployments. Integrating SDDC Manager’s fleet management with your current infrastructure is seamless, without impacting running workloads, the vCenter server, vSphere APIs, or your management processes. https://blogs.vmware.com/cloud-foundation/2024/12/20/new-features-available-with-the-vmware-cloud-foundation-import-tool/
Once added to Cloud Foundation, your vSphere infrastructure becomes the starting point of your private cloud journey. It is now centrally managed, allowing customers to use NSX virtual networking and paving the way for adopting a more efficient and automated way of deploying and operating infrastructure.
Watch this six-minute video to see a demo of VCF Import in action.
About VCF Import
In VCF 5.2.x, VCF Import is implemented as a set of scripts. These scripts can be downloaded from the Broadcom software portal and copied to the SDDC Manager appliance.
Note that the scripts are released independently of the SDDC Manager appliance. This allows Broadcom to introduce new features more efficiently over time in order to support a wider variety of configurations. Please refer to the Cloud Foundation Administration Guide for the most up-to-date information on supported configurations.
Importing vSphere Infrastructure to a VCF Private Cloud
After you have copied the scripts to the SDDC Manager appliance you can connect through SSH and run commands to validate your vCenter inventories and convert/import them as Cloud Foundation workload domains. At a high level, the process includes:
- Scanning the vCenter inventory to ensure compatibility with VCF.
- Registering the vCenter Server and its associated inventory with the SDDC Manager.
- Installing an NSX management cluster and preparing the vSphere hosts for NSX.
Once the import is complete, the vSphere environment becomes a VCF workload domain centrally managed through the SDDC Manager as part of your private cloud.
The VCF Import Tool has four main parameters: check, convert, import, and sync.
Check
The check parameter verifies your vCenter inventory before a conversion or import attempt. This function identifies potential configuration issues that could hinder a successful import. Running the check will return a detailed report on your inventory, highlighting both successful and failed checks. Notably, the check operation does not modify the inventory, enabling you to re-run checks as needed.
Convert
Use the convert parameter when you do not have an instance of the SDDC Manager appliance deployed. Begin by deploying an instance of the SDDC Manager appliance on the vSphere cluster that you want to convert to the management workload domain. Then, use secure copy (SCP) to copy the import tool CLI to the appliance. Once this is complete, run a check on the environment, and when ready, proceed with the convert operation to convert the vSphere environment into a Cloud Foundation management workload domain.
The SDDC Manager appliance is initialized during the management workload domain conversion. A new resource pool is created in the vCenter inventory. The SDDC Manager and vCenter Server appliances are relocated to this resource pool. After the conversion, an SDDC Manager workflow is initiated to deploy an NSX management cluster and prepare the hosts for NSX. NSX is configured by default with VLAN-backed distributed port groups in the converted management workload domain. There is no requirement to change existing networking configurations for the converted domain. The entire process is transparent to any running workloads, and all clusters in the vCenter inventory will be added to the workload domain.
The convert parameter can only be used once per VCF instance. After the management domain conversion, switch to using the import parameter to add additional vCenter instances as Virtual Infrastructure (VI) workload domains.
Note that you don’t need to use the convert parameter if you already have an SDDC Manager deployed from the Cloud Builder. In this case, simply upgrade your existing SDDC Manager to VCF 5.2.x, copy the VCF import CLI tool, and then use the import parameter to import your vCenter server instances as (VI) workload domains.
Import
Once you have established a Cloud Foundation management workload domain, utilize the import parameter to add additional vCenter Server instances as VI workload domains. Similar to the convert process, importing a VI domain does not change the vSphere environment and is non-disruptive to running workloads. Begin by verifying the environment with the check command.
Upon successful validation, use import to import the vCenter inventory as a VI workload domain. Once the import completes, an SDDC Manager workflow is initiated to deploy an NSX management cluster for the domain and prepare the hosts for NSX. All clusters in the vCenter inventory will be added to the VI workload domain. This is transparent to the running workloads, and there is no requirement to change the networking for the imported domain.
You repeat the import operation for each vCenter Server instance you wish to add, with a maximum of 25 supported domains in Cloud Foundation 5.2.x.
Sync
When managing vSphere infrastructure within a Cloud Foundation private cloud, you may occasionally need to change the vSphere environment directly, bypassing the SDDC Manager. In such cases, the changes made in vCenter may not be reflected in the SDDC Manager. When this happens, you use the sync function to synchronize the changes and prevent configuration drift. Consider scheduling regular synchronizations, e.g., every 24 hours.
Conclusion
The VCF Import feature simplifies converting existing vSphere infrastructure into a Cloud Foundation private cloud. Leveraging this, you can continue to utilize your existing vSphere infrastructure without purchasing new hardware, deploying a new environment, or fussing with complex workload migrations. The CLI tool offers a user-friendly interface that is easy to use and non-disruptive to your running workloads.
Additional Information:
- VCF Import Demo Video
- For more information, refer to the Cloud Foundation Administration Guide.
