ViPR 2.2 - Configure and Add Vblock Compute Systems to ViPR Using the ViPR REST API

Table of Contents

Overview

ViPR System Administrators can learn about ViPR support requirements, prerequisite information to prepare Vblock Compute Systems (Cisco Unified Computing System™ (UCS)) and the steps to add a compute system to ViPR.

For additional information, see ViPR Support for VCE VblockTM Systems.

Support requirements

See the ViPRSupport Matrix on the EMC Community Network (community.emc.com) for the compute system versions supported by ViPR.

This article is part of a series

Vblock Compute Systems 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

Add a Vblock compute system to ViPR

You add a Vblock compute system to ViPR using POST /vdc/compute-systems.

Before you begin

The following steps describe how to add a Vblock compute system to ViPR using the REST API. To use the ViPR UI to add a Vblock compute system to ViPR see the Configure and Add Vblock Compute Systems to ViPR article.

Procedure

  1. Add a Vblock compute system to ViPR by sending a POST /vdc/compute-systems request. The request returns a task whose URI can be queried to determine the status of the task.
    Request
    POST https://<ViPR_VIP>:4443/vdc/compute-systems
    Content-Type: application/xml
    X-SDS-AUTH-TOKEN: <AUTH_TOKEN>
    
    <compute_system_create>
        <name>compute_west_1</name>
        <ip_address>192.168.0.0</ip_address>
        <port_number>443</port_number>
        <use_ssl>true</use_ssl>
        <user_name>admin</user_name>
        <password>Password1</password>
        <system_type>ucs</system_type>
        <os_install_network>630</os_install_network>
    </compute_system_create>
    
    Response
    HTTP 202 Accepted
    Content-Type: application/xml
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <task>
        <creation_time>1421861349322</creation_time>
        <global>false</global>
        <id>urn:storageos:Task:4434fb76-4f6f-4525-996c-2659ffb2624b:vdc1</id>
        <inactive>false</inactive>
        <internal>false</internal>
        <link rel="self" href="/vdc/tasks/urn:storageos:Task:4434fb76-4f6f-4525-996c-2659ffb2624b:vdc1"/>
        <name>DISCOVER COMPUTE SYSTEM</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>
        <associated_resources/>
        <description>discover a compute system.</description>
        <op_id>4b661145-702d-417e-951d-cec23e062d26</op_id>
        <progress>0</progress>
        <resource>
            <id>urn:storageos:ComputeSystem:a9e3a23e-1020-40ca-b3d6-e5dc9b80c906:vdc1</id>
            <link rel="self" href="/vdc/compute-systems/urn:storageos:ComputeSystem:a9e3a23e-1020-40ca-b3d6-e5dc9b80c906:vdc1"/>
            <name>compute_west_1</name>
        </resource>
        <start_time>1421861349321</start_time>
        <state>pending</state>
    </task>
  2. Query the Vblock compute system create task, using the task URL from the response body of the POST request. When the message attribute of the task is Operation completed successfully, the operation has completed and the Vblock compute system has been successfully discovered.
    Request
    GET https://<ViPR_VIP>:4443/vdc/tasks/urn:storageos:Task:4434fb76-4f6f-4525-996c-2659ffb2624b:vdc1
    Content-Type: application/xml
    X-SDS-AUTH-TOKEN: <AUTH_TOKEN>
    Response
    HTTP 200 OK
    Content-Type: application/xml
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <task>
        <creation_time>1421861349322</creation_time>
        <global>false</global>
        <id>urn:storageos:Task:4434fb76-4f6f-4525-996c-2659ffb2624b:vdc1</id>
        <inactive>false</inactive>
        <internal>false</internal>
        <link rel="self" href="/vdc/tasks/urn:storageos:Task:4434fb76-4f6f-4525-996c-2659ffb2624b:vdc1"/>
        <name>DISCOVER COMPUTE SYSTEM</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>
        <associated_resources/>
        <description>discover a compute system.</description>
        <end_time>1421861354723</end_time>
        <message>Operation completed successfully</message>
        <op_id>4b661145-702d-417e-951d-cec23e062d26</op_id>
        <progress>100</progress>
        <resource>
            <id>urn:storageos:ComputeSystem:a9e3a23e-1020-40ca-b3d6-e5dc9b80c906:vdc1</id>
            <link rel="self" href="/vdc/compute-systems/urn:storageos:ComputeSystem:a9e3a23e-1020-40ca-b3d6-e5dc9b80c906:vdc1"/>
            <name>compute_west_1</name>
        </resource>
        <start_time>1421861349321</start_time>
        <state>ready</state>
    </task>
    
Back to Top

ViPR discovery of Vblock compute systems

Once the Vblock compute system is added to ViPR, ViPR automatically discovers the compute system and the compute system resources as follows:

Back to Top

Vblock System configuration in ViPR

You must add each Vblock system component to ViPR as an individual physical asset: Compute (UCS), Storage System, and Networks. Once all of the physical assets of the Vblock system have been added to ViPR, you can set up storage visibility using the ViPR virtual arrays. After configuring virtual arrays, you can configure ViPR compute virtual pools.

Back to Top

Additional REST API calls to manage your Vblock Compute Systems

The table shows some additional APIs that are used to manage your Vblock Compute Systems

Back to Top