Configuring cloud resources

The cloud resources that you can configure and manage in Foundation are shown in the following table.

Prerequisites 

  • Minimum required privileges: Infrastructure administrator

  • Data Center Management network connects the 3PAR storage system, the vCenter Server, and/or the enclosure that contains the compute nodes with the CloudSystem Console management hypervisor.

  • For ESX clusters, the vCenter Server is registered in the CloudSystem Console on the Integrated Tools screen.

Configuring cloud resources

CloudSystem Foundation Task
 

A Provider Network is part of the Cloud Data Trunk, which is the physical network hosting the VLANs that OpenStack networking makes available to users. The Cloud Data Trunk provides communication for compute nodes and virtual machine instances.

 

An image is a template for a virtual machine file system. It contains information about the operating system to provision to a virtual machine instance.

 

Block storage drivers define the specific characteristics of the volume types that are created for storage systems. They deliver technology or vendor specific implementations for the OpenStack Block Storage functionality. Foundation supports the 3PAR FC, Direct-Attach and iSCSI drivers. These drivers require connectivity to the management console of a supported HP 3PAR storage system.

 

In Foundation, a volume type describes the characteristics of a class of volumes that may be selectable by a cloud user. For the HP 3PAR drivers, each volume type is associated to a block storage driver and a Common Provisioning Group (CPG). The host type (KVM or ESX) is also defined in the volume type.

 

Flavors define the size of compute resources (number of virtual CPUs, memory and ephemeral storage capacity) that can be assigned automatically to virtual machines.

 
  1. Import ESX clusters or add KVM compute nodes

Create ESX clusters in vCenter Server and then import them to the CloudSystem Console Server.

Create KVM compute nodes manually on a KVM hypervisor. Once created, they appear on the Compute Node screen in the CloudSystem Console in an inactive state.

 

Your KVM compute nodes or ESX clusters must already be visible in the CloudSystem Console. Activating a KVM compute node installs OpenStack agents on the compute node. (Activating an ESX cluster does not install any software.) After activation, the ESX clusters or KVM compute nodes are ready to serve as targets for resource provisioning.

See also Using CloudSystem Foundation at a glance