What are the ViPR Service Catalog Vblock System Services?

Table of Contents

Overview

ViPR users can review the list of ViPR Service Catalog, VCE Vblock System Services, and learn the ViPR administration requirements, and ViPR steps to create clusters on Vblock compute systems, and create a block volume from the Vblock storage system to attach to the newly created cluster.

ViPR users can also learn how to monitor a service operation, and work with the resources created as a result of the service operation.

Back to Top

Vblock System Services

The VCE Vblock System Services is a category of services in the ViPR Service Catalog that are used to manage the compute resources in a Vblock system

Back to Top

Use the VCE Vblock System Services to create clusters on the Vblock compute system

Before you begin

Before you can successfully provision a cluster, ViPR system administrators, and tenant administrators must have configured the necessary projects, physical assets, and virtual assets in ViPR as described in: Wok with service resources.

The Provision Cluster service performs the following tasks in a single ViPR operation:

Procedure

  1. Go to the Service Catalog > VCE Vblock System Services > Provision Cluster service.
  2. Complete the order form as follows:
    Option Description
    Project The project in which the cluster will be added after it is created.
    Name The name of the cluster that will be created on the Vblock system and vCenter.
    Virtual Array The virtual array in which the Vblock networks, and boot LUN storage are included.
    Compute Virtual Pool The compute pool containing available compute elements to use in provisioning.
    VCE Vblock Compute Image (OS) The operating system that will be installed on the cluster hosts. A ViPR System Administrator must add the compute image to the ViPR Physical Assets, before the service can be ordered.
    Hosts The host information for each host created in the cluster.Click Add for each additional host to add to the cluster.
    Host Name (FQDN) The fully qualified domain name that will be assigned to each host created in the cluster.
    IP Address The IP Address that will be assigned to each host created in the cluster.
    Netmask Netmask that will be used by all of the hosts in the cluster.
    Gateway Gateway that will be used by the hosts.
    Management Network The Management VLAN over which ViPR will use to communicate with the hosts for management purposes. The management network is required to add the ESX hosts to a vCenter and for any communication between ViPR and the ESX hosts.
    NTP Server NTP Server that will be used by all of the hosts in the cluster.
    DNS Servers Comma separated list of DNS Servers that will be used by the hosts.
    Host Root Password The password that will be assigned to the root user for all the hosts in the cluster.
    Block Virtual Pool The block virtual pool from which the boot LUN will be created.
    Size of Boot Volume The size of the volumes that will be used to boot the hosts.
    vCenter The vCenter in which the datacenter, to which the cluster will be added, resides. A ViPR Tenant Administrator must add the vCenter to ViPR before the service can be ordered.
    Datacenter The vCenter Datacenter to which the cluster will be added. A ViPR Tenant Administrator must add the vCenter to ViPR before the service can be ordered.
  3. 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 the service order has completed successfully, the service resources are put into the project that was assigned in the service order. The newly created hosts are added to the hosts, clusters, and vCenters in the ViPR Physical Assets. The service resources, other than the hosts, and clusters, can then be viewed, and deleted through the Resources pages.

Before you begin

Procedure

  1. To view the service resources, 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

Create a new block volume and attach it to the ESX cluster as a datastore.

Once the ESX cluster has been created and added to a vCenter by ViPR you can use the ViPR, Block Storage Services to create a new block volume from the Vblock storage system to allocate to the ESX cluster.

Procedure

  1. Go to the Service Catalog > Block Services for VMware > Create Volume and Datastore.
  2. Complete the order form:
    Option Description
    Datastore name The datastore name.
    VMwarevCenter The vCenter in which the datastore will be created.
    VMwarevCenter Datacenter The vCenter datacenter in which the datastore will be created.
    Storage Type Either, Shared to manage the storage for the entire cluster, or Exclusive to manage the storage for an individual host.
    ESX Host/Cluster The ESX host or cluster to which the storage will be allocated.
    Virtual Array The virtual array from which the storage will be allocated.
    Virtual Pool The virtual pool from which the storage will be allocated.
    Project The project to which the resources will be added.

    If the Project option is not displayed the service has been locked to a project and is for use only by members of that project.

    Name The volume name.
    Consistency Group Provides protection for the provisioned resource.

    The selection list contains the consistency groups previously associated with the project. Consistency groups are only required if the virtual pool configuration requires it, otherwise it is optional to choose consistency groups.

    Size The size of the volume.
    Multipath Policy VMware multipath policy to use with ESX hosts or clusters. Options are:
    • Default — To allow ViPR to define the policy.
    • Fixed — Uses the designated preferred path flag, if it has been configured. Otherwise, it uses the first working path discovered at system boot time. If the ESX host cannot use the preferred path or it becomes unavailable, the ESX host selects an alternative available path. The host automatically returns to the previously defined preferred path as soon as it becomes available again.
    • Most Recently Used – Selects the first working path. If the path becomes unavailable, the ESX host switches to an alternative path.
    • Round Robin — Uses an automatic path selection rotating through all available paths.

    Refer to VMware documentation for further details.

    HLU The Host Logical Unit (HLU). Use -1 to have ViPR automatically assign the HLU.
  3. Click Order.
    The Orders page is displayed with the progress of the order.
Back to Top