ViPR 2.2 - Create ViPR Virtual Pools for Vblock Compute Systems Using the REST API

Table of Contents

Overview

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.

This article is part of a series

Compute virtual pools can be added to ViPR at anytime. If, however, you are setting up the ViPR Controller virtual data center for the first time, before you continue to provision storage, complete the following steps.
  1. Authenticate with the ViPR REST API
  2. Add physical assets to ViPR:
  3. Create ViPR virtual assets:
    1. Create and configure a virtual array
    2. Create virtual pools:

Back to Top

Create a Compute Virtual Pool using the REST API

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

Before you begin

Procedure

  1. Create a compute virtual pool using POST /compute/vpools. The new compute vpool is returned.
    Request
    POST https://<ViPR_VIP>:4443/compute/vpools
    Content-Type: application/xml
    X-SDS-AUTH-TOKEN: <AUTH_TOKEN>
    
    <compute_vpool_create>
         <name>compute_vpool_west1</name>
         <description>vpool for west</description>
         <system_type>Cisco_UCSM</system_type>
         <min_processors>3</min_processors>
         <varrays>
            <varray>urn:storageos:VirtualArray:ac294bc7-0518-48dd-9f54-4980f0012f86:vdc1</varray>
         </varrays>
         <use_matched_elements>true</use_matched_elements>
         <service_profile_templates>
              <service_profile_template>urn:storageos:UCSServiceProfileTemplate:6c6236dd-e98d-47da-b2e6-749c09554ccd:vdc1</service_profile_template> 
        </service_profile_templates>
    </compute_vpool_create>
    Response
    HTTP 200 OK
    Content-Type: application/xml
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <compute_vpool>
       <creation_time>1422389775019</creation_time>
       <global>false</global>
       <id>urn:storageos:ComputeVirtualPool:75ec968b-8001-4889-abd7-80090c4010a9:vdc1</id>
       <inactive>false</inactive>
       <internal>false</internal>
       <name>compute_vpool_west1</name>
       <remote>false</remote>
       <tags/>
       <vdc>
          <id>urn:storageos:VirtualDataCenter:99c5c185-ebb0-468a-8fe7-3ea6e65b7b57:vdc1</id>
          <link rel="self" href="/vdc/urn:storageos:VirtualDataCenter:99c5c185-ebb0-468a-8fe7-3ea6e65b7b57:vdc1"/>
       </vdc>
       <available_matched_compute_elements/>
       <description>vpool for west</description>
       <in_use>false</in_use>
       <matched_compute_elements/>
       <min_processors>3</min_processors>
       <service_profile_templates>
          <service_profile_template>
             <id>urn:storageos:UCSServiceProfileTemplate:6c6236dd-e98d-47da-b2e6-749c09554ccd:vdc1</id>
             <name>ST-ServerTemplate</name>
          </service_profile_template>
       </service_profile_templates>
       <system_type>Cisco_UCSM</system_type>
       <use_matched_elements>true</use_matched_elements>
       <varrays>
          <varray>
             <id>urn:storageos:VirtualArray:ac294bc7-0518-48dd-9f54-4980f0012f86:vdc1</id>
             <link rel="self" href="/vdc/varrays/urn:storageos:VirtualArray:ac294bc7-0518-48dd-9f54-4980f0012f86:vdc1"/>
          </varray>
       </varrays>
    </compute_vpool>
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.

Storage

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.

Network

  • 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.

Policies

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

Back to Top

Additional REST API calls to manage your Compute Virtual Pools

The table shows some additional APIs that are used to manage your Compute Virtual Pools.

Back to Top