ViPR 2.2 - What are the ViPR Service Catalog Block Storage Provisioning Services?

Table of Contents

Overview

This article provides ViPR self-service, provisioning users a list of the ViPR block storage provisioning services, describes the services, and presents an example of how to use the ViPR UI to provision storage for a Windows cluster.

Block storage provisioning services

The ViPR Service Catalog provides access to a set of predefined services, which includes high level operations to carry out common provisioning activities such as creating a block storage volume and exporting it to a host or cluster, as well as "building block" services, to perform more granular operations such as creating a ViPR volume, or exporting the storage to a host in separate operations.

ViPR services are organized in categories. There is a general Block Storage Services category which can be used to create block storage volumes, and export it to any type of host.

ViPR also provides a set of predefined block storage services for AIX®, AIX VIO, Linux®, Windows®, and vCenters. In addition to provisioning the storage to the hosts, these services perform operations on the host, cluster, or vCenter after the storage is provisioned.

Back to Top

Create, mount, and format a block volume on a Windows cluster

The following procedure is an example of how a self-service, provisioning, user could use ViPR to create, mount, and format a block volume on a Windows cluster.

Before you begin

Service operations can only be run after the ViPR System Administrator has:

All of the hosts must be powered on to successfully provision volumes.

When logged into ViPR with a user role you can only create resources and perform operations on resources belonging to project that you are assigned to (or are the owner of). If you are a Tenant Administrator you can run all services and choose any project to be the owner of the resource.

Procedure

  1. While in the User mode, go to the Service Catalog > Block Services for Windows > Create and Mount Volume service.
  2. Select Shared for the Storage Type.
    Shared is to provision the storage across the cluster.
    Exclusive is to provision the storage to a single host.
  3. Select the cluster for which the storage will be provisioned.
  4. Select the virtual array from which the storage will be allocated.
    Note Image
    Available virtual arrays are based on ViPR's visibility to the host initiator. If the virtual array you are wanting to select is not available in the selection list, it may be that the host is powered down.

  5. Select the virtual pool from which the storage will be allocated.
  6. Select the project to which the resources will be assigned once the storage is provisioned.
  7. Provide a name for the volume.
  8. If required, select the volume consistency group.
  9. Enter the size the volume will be after provisioned.
  10. In the File System Type field, select the volume format.
  11. Enter the drive letter for the mount point.
    If left blank, the next available letter will be used.
  12. Enter a drive label.
    If left blank, ViPR assigns the volume name as the drive label..
  13. Click Order.
    The Orders page is displayed with the progress of the order.
Back to Top

Monitor and troubleshoot the service order

Once a service is ordered, you can watch the progress of the service, and troubleshoot issues with the service from the Orders, or My Orders page.

After ordering a service, the order page opens displaying the progress of the order.

Procedure

  1. Keep the order page open to continue to watch the progress of the service operation.
    If you have left the orders page, go to the Service Catalog > My Orders page, and you will see the order in the list.
  2. Click the order to view the details of the order.
  3. Expand the Logs section to view the logs entered for the service.
    Red text indicates that an error occurred while the service was running, and provides details of the error.
  4. Expand Precheck Steps to view the steps ViPR performs before executing the service.
    The order will not proceed if any of the precheck steps fail.
  5. Expand Execution Steps to view the steps ViPR performs to complete the service order.
    Red text indicates an error occurred during the service execution and the point in the execution steps where an error occurred.
  6. Expand Tasks to view the details of each specific task run to complete the order. If an order failed, the Tasks will show the specific task where the order to fail.
Back to Top

Work with service resources

Once a service operation has completed successfully , the resources are put into the project that was assigned in the service order. The resources can then be viewed, and deleted through the Resources pages.

Before you begin

Provisioning users can only select the projects to which they have been assigned, and can only see the resources in those projects.

Tenant administrators can see all projects and all project resources.

Procedure

  1. Open the Resources menu, and select the type of resource to view:
    • Volumes
    • Block Snapshots
    • Consistency Groups
    • Export Groups
    • File System
    • File Snapshots
  2. Select the project in which the resource belongs.
    A list of the resources, of the selected type, appear in the table. For example, if you selected File System, a list of file systems that were provisioned in the selected project appears in the File System table.
    If you selected Volumes, a list of block volumes that were provisioned in the selected project appears in the Volumes table.
  3. Select the box for the row, and click Delete to delete the resource.
  4. Click anywhere in the row, to see more details for the resource.
Back to Top

Block storage systems under ViPR management

Once a volume is under ViPR management, and has been provisioned or exported to a host through a ViPR service, you should no longer use the storage system element manager to provision or export the volume to hosts. Using only ViPR to manage the volume will prevent conflicts between the storage system database and the ViPR database, as well as avoid concurrent lock operations being sent to the storage system. Some examples of failures that could occur when the element manager and ViPR database are not synchronized are:
  • If you use the element manager to create a volume, and at the same time another user tries to run the "Create a Volume" service from ViPR on the same storage system, the storage system may be locked by the operation run from the element manager, causing the ViPR “Create a Volume” operation to fail.
  • After a volume was exported to a host through ViPR, the same masking view, which was used by ViPR during the export, was changed on the storage system through the element manager. When ViPR attempts to use the masking view again, the operation will fails because what ViPR has in the database for the masking view is not the same as the actual masking view reconfigured on the storage system.
You can, however, continue to use the storage system element manager to manage storage pools, add capacity, and troubleshoot ViPR issues.

Back to Top