How it works

Associated appliances
Storage
Physical servers
User authentication

The following graphic illustrates the relationship between Foundation, the Foundation virtual appliances, Enterprise, and the underlying network infrastructure.

CloudSystem appliances and network infrastructure

CloudSystem appliances and network infrastructure

Associated appliances

The following appliances are automatically created after the Cloud Networking settings are saved.

For more information, see Networks in CloudSystem Foundation.

Software Defined Networking (SDN) appliance

Manages the network infrastructure for the CloudSystem Console

Network node appliances

Manage network services, such as DHCP and L3 (routing) services, for provisioned virtual machines and provisioned virtual networks. Three network node appliances are created when the Cloud Networking settings are saved.

The following appliance is automatically created after an ESX cluster is imported. (No Proxy appliances are started in a KVM-only environment.)

Proxy appliance

Acts as a communication mechanism between OpenStack technology and vCenter Server, and runs the OpenStack agents for up to twelve clusters for each vCenter Server. Additional appliances are started when new clusters are added to the cloud.

Storage

CloudSystem works with HP 3PAR StoreServ Storage, a cluster-based storage architecture that incorporates data management and fault tolerance technologies that can meet the storage needs of smaller sites and can be scaled for global organizations.

3PAR storage is required to create block storage for VM guests.

Storage for manually provisioned hypervisor hosts is more flexible, and can include local disks.

With 3PAR, you can create virtual storage for boot and data disks.

Virtual server storage

Virtual server storage connects the 3PAR storage system to virtual machine instances. Options include:

  • Fibre Channel Storage Area Network (FC SAN), which provides block-level storage that can be accessed by the applications running on any networked servers

  • iSCSI, which is block-level storage that uses traditional Ethernet network components for connectivity

  • Direct-Attach Fibre Channel Storage, a single layer Fibre Channel storage network that eliminates SAN switches and HBAs (host bus adapters)

Physical servers

ESX clusters and KVM hosts can be used as management hosts or compute nodes.

Management hosts

Hypervisors that host the virtual machine appliances that comprise the CloudSystem solution. There are three possible configurations:

  • An ESX management cluster that hosts the CloudSystem virtual machine appliances and Integrated Tools virtual machine appliances.

  • A standalone ESX management hypervisor that hosts the CloudSystem virtual machine appliances and Integrated Tools virtual machines appliances. See Integrated Tools.

  • A KVM management hypervisor that hosts the CloudSystem virtual machine appliances.

Compute nodes

ESX clusters and KVM hosts that provide the pool of physical resources used to provision virtual machine instances.

User authentication

You can choose either of two methods of user authentication. If you use local logins, CloudSystem provides local authentication for users authorized to access CloudSystem. The Infrastructure Administrator enters user data, which is saved in the appliance database. When anyone tries to access the console, the login information entered is checked against the user attributes stored in the database.

Alternatively, you can disable local logins and use an external authentication directory service (also called an enterprise directory or authentication login domain) to provide a single sign-on for groups of users instead of maintaining individual local login accounts. An example of an authentication directory service is a corporate directory that uses LDAP (Lightweight Directory Access Protocol). For more information, see Settings: Security.