ViPR 2.2 - What is a ViPR compute virtual pool?
Table of Contents
Compute virtual pools can only be created in ViPR by System Administrators when there is at least one logical compute system under ViPR management. Each logical compute system contains compute elements, in the way that a UCS contains one or more chassis that contain the blades. System Administrators can add a compute system to ViPR as a physical asset. In ViPR, UCS systems are referred to as Vblock compute systems.
A Vblock system is a converged hardware system from VCE (VMware, Cisco, and EMC) that is comprised of a UCS, EMC storage systems, and networks. These Vblock components are added separately into ViPR as physical assets. They must be physically and logically connected for ViPR to carry out provisioning operations. Once added into the system, a System Administrator should create one or more virtual arrays to define storage visibility within ViPR. Once a virtual array is created, ViPR understands which UCS systems have visibility to storage and will use that information during the process of creating compute virtual pools and provisioning.
Compute virtual pools are the abstraction used to create pools of hosts. This is very similar to the ViPR concept of file and block storage virtual pools, which abstract physical pools of block and file storage. Compute virtual pools abstract physical compute elements such as UCS blades, and storage virtual pools abstract physical storage in underlying storage arrays. Compute virtual pools are used to provision hosts while storage virtual pools are used to provision storage.
When ViPR System Administrators create a compute virtual pool, they can manually assign specific blades to a compute virtual pool, or define qualifiers (such as memory, CPU speed, processors, etc.) that allow ViPR to automatically assign the blades to a pool based on the criteria of the qualifier.
For each UCS that is part of a compute virtual pool, a service profile template can be assigned. A UCS service profile template is created by a UCS administrator and contains all the required settings to set up a blade. ViPR users can then use the UCS service profile template at the time of provisioning to configure the blades.
A service profile template must be assigned for each UCS or that UCS will not be used when provisioning from that compute virtual pool. The service profile templates are discovered by ViPR to make them easy to assign to the pools.
Compute virtual pools are used to provision hosts in the Vblock system services in the ViPR Service Catalog to create new hosts. You have the option to use ViPR to provision the hosts with or without an ESX 5.x operating system. The compute virtual pool is used as the pool of UCS blades from which ViPR creates the hosts. ViPR assigns the UCS service profile template settings associated with the compute virtual pool to each of the new hosts/blades in the cluster. The service profile templates also define the layer 2 networking on each host.Back to Top