ViPR 2.2 - Create ViPR Virtual Pools for Vblock Compute Systems

Table of Contents


ViPR system administrators can learn the steps to create a compute virtual pool. UCS administrators can learn the ViPR requirements for the service profile template that will be used by ViPR to provision the UCS blades.

Back to Top

Create a Compute Virtual Pool

Compute virtual pools are a pool of compute system elements (blades for UCS). When a Vblock System Service is run, ViPR pulls required compute resources from the selected compute virtual pool.

Before you begin


  1. Go to the Virtual Assets > Compute Virtual Pools page.
  2. Click Add.
  3. Complete the following fields.
    Option Description
    Name Enter the name of the virtual pool.
    Description Optionally, enter a virtual pool description.
    System Type The type of compute system for example, CiscoUCS.
    Virtual Arrays Select one or more virtual array. The compute system, from which you will be assigning compute elements to the compute virtual pool, must have connectivity to the selected virtual array. ViPR identifies which compute systems are part of a virtual array by the networks (VSANs) that were added to the virtual array. When a network (VSAN), to which a compute system is connected, is added to a virtual array, ViPR includes the compute system in the virtual array topology, and determines which compute elements (blades) are available in the selected virtual arrays.
    Access Control Optionally, assign the tenants who will have access to the compute virtual pool.
    Optionally, enter minimum and maximum values to eliminate blades, which do not match the criteria, from the list of available blades that will appear in the Compute Element list. When no minimum is set, ViPR defaults to zero. There is no default maximum value. The maximum is unlimited when it is not set. For example:
    • If processors are set with a minimum of 6 and no maximum, then only blades with 6 or more processors will be available to use in the compute virtual pool.
    • If processors are set with no minimum, and a maximum of 16, then any blade with 16 or less processors will be available to use in the compute virtual pool.
    • If no minimum or maximum value is set for processors ViPR will include available blades with any number of processors in the virtual pool.
    Compute Elements

    Choose whether to manually assign the compute elements to the virtual pool, or to allow ViPR to automatically assign the compute elements to the pool based on the criteria defined in the Qualifiers.

    If Manual was selected, chose the compute elements to include in the virtual pool.

    The compute elements are populated from any compute systems determined to be in the selected virtual arrays. The compute elements must be registered and available. If qualifiers were defined, only the compute elements within the constraints of the qualifiers will be presented. If no qualifiers were assigned, all the available compute elements from the compute system are presented.

    Compute elements that are not available in the Compute Virtual Pools have been used by ViPR for a ViPR operation.

    System Type Configuration For UCS, select the Service Profile Template that contains the configuration definitions to apply to the blades in the virtual pool.
  4. Click Save.
Back to Top

UCS blades and service profile templates

Some compute systems are blade servers with hardware virtualization. This means that many properties of the servers that were traditionally burned into the hardware are actually soft settable. The UCS uses the concept of "service profiles" as a container for all the required settings to stand up a blade.

Service profiles are associated to blades to assign the required settings. Additionally, the UCS has the concept of, "service profile templates," that can be set up by UCS administrators. These service profile templates can be used by non-admin users to create the service profiles that turn a blade into a bare-metal server.

ViPR does not perform the functions of the UCS administrator, rather ViPR utilizes service profile templates to assign the required properties to blades. A UCS administrator will need to create service profile templates that ViPR can use to provision servers and hosts.

Back to Top

ViPR requirements for service profile templates

The following sections explain the requirements to configure a service profile template for ViPR provisioning operations.

Note Image
If existing service profile templates do not match the following requirements, clone one of the service profile template to create a new service profile template and alter the settings as required by ViPR.

General properties

  • The service profile template must not be associated to a server pool. Blade selection is performed by the ViPR Compute Virtual Pools.
  • The service profile Type must be Initial Template. It cannot be an updating template.
  • UUID assignment must be from a valid UUID Suffix Pool set up in the UCS with available addresses.


ViPR currently supports Fibre Channel boot for UCS servers. The following lists the Fibre Channel requirements:

  • World Wide Node Name (WWNN) assignment must be from a valid UUID Suffix Pool set up in the UCS with available addresses.
  • The Local Disk Configuration Policy must be set to a local disk configuration policy where the Mode is set to No Local Storage.
  • There must be at least one vHBA interface.
  • For each vHBA, the World Wide Port Name (WWPN) assignment must be from a valid WWPN pool set up in the UCS with available addresses.
  • The VSAN set on each vHBA must be a valid network discovered by ViPR. The VSAN must match one of the networks in a ViPR virtual array.
  • Policy settings on the vHBAs are not set by ViPR provisioning and are at the administrator's discretion.


  • Policy settings on the vNICs are not set by ViPR provisioning and are at the administrator's discretion.
  • There must be at least one vNIC interface.
  • For each vNIC, the MAC Address Assignment must be from a valid MAC pool that was set up in the UCS with available addresses.
  • Each vNIC must have at least one VLAN.

Boot Policy and Boot Order

There are no Boot Policy requirements. ViPR ignores all Boot Policy settings in the service profile template and overwrites any existing parameters when it creates service profiles.


ViPR does not set any policies. The UCS administrator is responsible for setting the policies.

Back to Top