The overview screen shows ESX clusters and KVM compute nodes that are capable of hosting virtual machine instances. ESX clusters appear on the overview screen after they are imported from vCenter Server. KVM compute nodes appear on the overview screen when they are assigned a DHCP lease from the Cloud Management Network.
The status of the ESX cluster or KVM compute node determines if it is ready to host virtual machine instances.
| Screen component | Description |
|---|---|
| Contains |
Number of currently hosted virtual machine instances. Click the instance link to navigate to the Instances overview screen. |
| Virtualization technology |
Hypervisor software on the compute node. |
| Number of hosts |
Number of hypervisor hosts in the cluster. In non-cluster systems, this value is 1. |
| Operating System |
Operating system installed on the compute node hypervisor. |
| Capability |
ESX cluster feature enabled on the compute node, for example High Availability (HA) or Dynamic Resource Scheduler (DRS). |
ESX clusters are imported from vCenter Server. The import cluster action retrieves cluster information from vCenter Server and brings the cluster into the CloudSystem Console. You have the option to activate the cluster when it is imported. Activated clusters are available for hosting virtual machine instances. Clusters that are imported, but not activated, have a status of Unknown until the cluster is activated.
| Screen component | Description |
|---|---|
| VMware vCenter |
Select a vCenter Server registered in the CloudSystem Console. The Datacenter options are populated based on the vCenter Server selected. See Register VMware vCenter Server. |
| Datacenter |
Select a Datacenter. The cluster options are populated based on the Datacenter selected. |
| Cluster |
Select the cluster within the vCenter Server and Datacenter to import as a compute node. |
| Activate |
Choose to activate the cluster during import.
|
Activated ESX clusters and KVM compute nodes are available for hosting virtual machine instances.
Enter the following information to activate a KVM compute node. Specifying this information is not required to activate an ESX cluster.
| Screen component | Description |
|---|---|
| User name |
User name for the operating system running on the KVM compute node. The user name is defined when the KVM compute node hypervisor is provisioned. |
| Password |
Password for the operating system running on the KVM compute node. The password is defined when the KVM compute node hypervisor is provisioned. |
| Cloud data trunk devices |
The Cloud Data Trunk interfaces that are used to connect network devices to the KVM compute node. If there are multiple interfaces, separate them with a comma. Examples
|
| Action | Description |
|---|---|
| Import |
Import an ESX cluster from vCenter Server. This action retrieves cluster information from vCenter Server, saves it in the CloudSystem appliance database, and displays it in the CloudSystem Console. See Import a cluster. |
| Activate |
Install and configure software on the hypervisor that makes the compute node available to the cloud. See Activate a compute node. |
| Deactivate |
Revert resources to their pre-configured state. The names of deactivated compute nodes appear in gray on the Compute Nodes overview screen. Deactivated nodes are not visible in the CloudSystem Portal. See Deactivate a compute node. |
| Delete |
Remove a deactivated ESX cluster from the appliance database or expire the DHCP lease on a deactivated KVM compute node. See Delete a compute node. |