VMware vCenter

CloudBolt supports vCenter version 5.1 → 6.7

Account Username & Password
The credentials for the vCenter account that CloudBolt will use to perform server creation, power management, synchronization, deletion, and other actions.
Clusters
Clusters are required to deploy using CloudBolt. If you are attempting to deploy to a single node, first create a cluster using vCenter. A CloudBolt Environment will automatically be created for each cluster selected, and the cluster-specific options (such as the resource pools and datastores) will be imported.
Network Requirements
CloudBolt communicates with VMware using the standard HTTPS connection on port 443. Network rules must allow traffic on port 443 between the CloudBolt server and all vCenters and ESX hosts.
VM Customization

By default, CloudBolt will use the compatible guest customization tools in vCenter templates to customize newly provisioned VMs with parameters such as hostname, IP address, DNS server, WINS servers, domain membership, and more.

Windows Sysprep answer files, often called unattend.xml, can be passed to vCenter from CloudBolt to provide finer-grained control over how a Windows VM is customized. To use this feature, add the parameter labeled “Sysprep Answer File” to a vCenter-backed Environment, and set its contents to the XML stored in a Sysprep answer file. This file is templatized by CloudBolt, so dynamic values such as {{ server.hostname }} can be used.

NOTE: Using a sysprep answer file will ignore the default guest customizations parameters described above, therefore if using an answer file, ALL customizations for a VM must be specified as part of the supplied answer file.

Modifying or Adding Disks

vCenter does require you to determine the datastore and disk provision type when adding disks.

The accepted parameters to use with the CloudBolt modification API are as follows:

disk_size: The size to change the original disk to.
new_disk_size: The size for the new disk to be added.
vmware_datastore: The datastore you want to provision the disk to
vmware_disk_type: The type of disk you want to provision (ie, Thin Provision)

NSX

If your vCenter supports advanced network configurations like vxlans and edge appliances, you will want to go to the NSX tab and configure the following:

NSX Endpoint
Defines and manages the NSX Manager connection endpoint used to create vxlans, edge appliances and support all advanced network concepts. See Virtual Networks for more info.
Edge Gateway Configuration

Add default values that should be used when creating an NSX Edge Services Gateway appliance like Provider Network, Cluster, Datastore, CLI Credentials and other attributes.

NOTE: In order to determine the IP to be used for the uplink interface of the ESG it is necessary that the provider network defined in the NSX Edge Configuration object be associated with an IP Pool. The provider network should also be fully configured in CloudBolt with appropriate values for Gateway and Netmask.