Resource handlers

Add one resource handler for each vCenter, cloud account, or subscription you want CMP to work with. CMP then creates, powers on and off, resizes, and deprovisions servers there, and imports existing resources, all through a single interface.

Supported technologies

You can create a resource handler for any of these technologies. The technology picker groups them into four sections, shown in the order below. Technologies marked as disabled by default do not appear in the picker until enabled, as described in Enable a resource handler.

Public Cloud

• Alibaba Cloud
• Amazon Web Services
• AWS China - 亚马逊
• Azure
• Google Cloud Platform
• IBM Cloud
• MacStadium Orka (disabled by default)
• Oracle Cloud Infrastructure
• Outscale (disabled by default)
• vCloud Director (not installed by default)

Private Cloud

• Azure Local (disabled by default)
• H3C CAS (disabled by default)
• Hyper-V
• Nutanix Acropolis
• OpenShift Virtualization (disabled by default)
• OpenStack
• Oracle Linux Virtualization Manager (disabled by default)
• Proxmox Virtual Environment (disabled by default)
• SCVMM
• VMware Cloud on AWS (disabled by default, and deprecated: use VMware vCenter for new connections)
• VMware vCenter

Gov Cloud

• Amazon Web Services - JIT (disabled by default)
• AWS GovCloud (US)
• IBM Cloud for Government

Bare Metal

• IPMI
• MAAS
• MetalSoft

Legacy technologies

You cannot create a new resource handler for these technologies. Handlers previously created for them continue to work.

• Azure Stack
• QEMU-KVM
• XenServer

Capabilities by technology

The table shows which server features CMP supports for each technology. A dash means the feature is not available. Power covers power on, power off, and reboot. Server stats are the performance statistics on a server’s Stats tab.

1. Includes AWS GovCloud (US) and AWS China. AWS servers change size with the Resize VM server action rather than by editing CPU and memory. See Resize VMs. AWS is also the only technology that imports public cloud billing data.
2. Azure and Azure Stack servers change size with the Resize VM server action. See Resize VMs.
3. Includes IBM Cloud for Government.
4. * Depends on the handler’s Nutanix API version. Changing CPU and memory, adding disks, and adding NICs need v3 or v4.0. The console needs v3. Tags need v4.0.

Enable a resource handler

Nine technologies are disabled by default and can be enabled with a feature flag:

• Amazon Web Services - JIT
• Azure Local
• H3C CAS
• MacStadium Orka
• OpenShift Virtualization
• Oracle Linux Virtualization Manager
• Outscale
• Proxmox Virtual Environment
• VMware Cloud on AWS

To enable vCloud Director, run the script described in Enable the vCloud Director resource handler below.

Enable a feature-flagged resource handler

1. SSH into your CMP server as the root user.

2. Open /var/opt/cloudbolt/proserv/customer_settings.py for editing.

3. Add the following line:

   from settings import FEATURE_REGISTRY
   

4. Add the corresponding line for your desired resource handler and save the file:

   Resource handler	Setting
   Amazon Web Services - JIT	FEATURE_REGISTRY["resourcehandler::awsjit"] = True
   Azure Local	FEATURE_REGISTRY["resourcehandler::azurelocal"] = True
   H3C CAS	FEATURE_REGISTRY["resourcehandler::h3ccas"] = True
   MacStadium Orka	FEATURE_REGISTRY["resourcehandler::orka"] = True
   OpenShift Virtualization	FEATURE_REGISTRY["resourcehandler::ovirt"] = True
   Oracle Linux Virtualization Manager	FEATURE_REGISTRY["resourcehandler::olvm"] = True
   Outscale	FEATURE_REGISTRY["resourcehandler::outscale"] = True
   Proxmox Virtual Environment	FEATURE_REGISTRY["resourcehandler::proxmox"] = True
   VMware Cloud on AWS	FEATURE_REGISTRY["resourcehandler::vmc_aws"] = True

5. Reset the feature configuration:

   /opt/cloudbolt/manage.py features --reset
   

6. Restart the Apache HTTP Server:

   systemctl restart httpd
   

7. Confirm the flag is active:

   /opt/cloudbolt/manage.py features --list
   

Enable the vCloud Director resource handler

1. SSH into your CMP server as the root user.

2. Run the following commands:

   cd /opt/cloudbolt/
   initialize/create_objects.py initialize/vcloud_director.py
   

Create a resource handler

1. Go to Admin > Resource Handlers and select Add.

   (opens full-size image in a new tab)

2. Select the tile for your technology. The tiles are grouped under Public Cloud, Private Cloud, Gov Cloud, and Bare Metal. To search across all of them, type a provider name in Filter providers.

3. Enter the credentials for your chosen technology. See the individual resource handler pages for the fields each one needs.

4. Select Continue.

5. Name the resource handler, set its remaining options, then select Done.

A technology is missing from the picker in two cases: it is disabled by default and not yet enabled, or it is IPMI and one already exists. CMP supports a single IPMI resource handler.

Resource handler ID

Each resource handler has a numeric ID that appears in its URL. Plugin code uses this ID to look up a handler, as the test in Check infrastructure health with CIT does.

Locate a resource handler ID.

1. Select Admin > Resource Handlers.
2. Select a resource handler name.
3. In the URL, note the number following resourcehandlers/

The REST API identifies a handler differently, by a global ID beginning with RH-. Read it from the resourceHandlers endpoint rather than from the URL. See REST API.

Delete a resource handler

Deleting a resource handler removes it from CMP. Nothing in your hypervisor or cloud provider changes; the virtual machines, networks, and other resources there remain as they are.

If no environments or servers are using the handler, the dialog asks only for confirmation.

If any are using it, the dialog reports how many and requires you to clear them first. Selecting the checkbox marks those server records as historical and removes those environments from CMP, and Delete stays disabled until you select it. The servers in your hypervisor or cloud provider are not affected, and imported networks are not deleted.