
Configuring cloud resources in CloudSystem Console
CloudSystem Foundation Task
1. Add a Provider Network
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.
2. Add one or more images
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.
3. Add a block storage driver
A block storage driver defines the characteristics of the volume type that is created for storage systems. Drivers
deliver technology or vendor-specific implementations for the OpenStack Block Storage functionality. CloudSystem
supports the 3PAR FC, Direct-Attach and iSCSI drivers. These drivers require connectivity to the management
console of a supported HP 3PAR storage system.
4. Add volume types
A volume type describes the characteristics of a class of volumes that can 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 hypervisor type (KVM or ESX) is also defined in the volume type.
5. Verify or add flavors
Flavors define the size of compute resources (number of virtual CPUs, memory and ephemeral storage capacity)
that can be assigned automatically to virtual machines.
6. Create compute nodes
You create and manage ESX compute hosts in vCenter Server. All compute hosts are configured as clusters. You
impot these clusters into CloudSystem.
You create KVM compute nodes on KVM hosts. After a KVM compute node is created, it appears on the Compute
Node screen in the CloudSystem Console with an Unknown status, meaning it is not yet activated.
7. Import ESX clusters
CloudSystem retrieves information about an ESX cluster when you import it. The cluster is added to the Compute
Nodes overview screen in an Unknown state, meaning it is not yet activated.
8. Activate a compute node
Your ESX cluster or KVM compute nodes 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.
Maximum supported configuration values for each CloudSystem
Each instantiation of CloudSystem Foundation software supports a maximum of configured resources
as shown in the following table.
Maximum number supportedConfigured resource
5,000Managed virtual machine instances
100Managed hypervisor hosts
32CloudSystem Portal users
5CloudSystem Portal users simultaneously creating virtual
machine instances
Maximum supported configuration values for each CloudSystem 71
Komentáře k této Příručce