Each Resource Handler you set up will connect one Environment to each Acropolis Cluster.
Connections to Acropolis use SSL (HTTPS) by default, and require a username and password for an account that has read and write privileges within Prism: e.g. an account that can provision VMs, modify/delete existing VMs, and read information about VMs. Connections also require a port (which defaults to 9440) and hostname. Because connections use SSL by default, you may need to apply a host SSL certificate to your Acropolis cluster (contact Nutanix support for further details) where the hostname matches the hostname you enter into CloudBolt.
CloudBolt provisions new VMs on Acropolis from Disk Images hosted in the Image Service. These images may need to be customized based on typical Acropolis requirements, e.g.:
- CentOS servers require the acpid yum package to be installed to support power controls from Acropolis. (CloudBolt issues shutdown and reboot commands using Acropolis’ ACPI operating system-based power control support as opposed to performing hard shutdown/power cycle. CentOS does not support ACPI out of the box compared to, e.g., Windows.)
- On Linux servers, your network interfaces need to be ready for cloning operations. (e.g. your image needs to be configured so that eth0 connects on VM startup, instead of attempting to connect to eth1.)
If you are not using the Image Service today, you will need to create images from existing VM disks by using the acli command-line utility. CloudBolt Software has found that the easiest way to do so is to run the following example commands by SSHing into your Acropolis cluster:
# This command clones the VM Disk on a VM named "centos6-template" to an # image named "centos6". acli image.create centos6 clone_from_vmdisk=vm:centos6-template:scsi.0 # This command marks the newly-created image as a disk-type image. (As # opposed to a CDROM ISO.) acli image.update centos6 image_type=kDiskImage