Configure ViPR Object Storage on ViPR-Managed File Storage Systems

Table of Contents

Back to Top

Introduction

ViPR object storage is the enabler for a range of ViPR data services. ViPR object storage can be configured to use ViPR-managed file storage systems (Isilion, VNX, and NetApp are supported) or storage provided by commodity nodes. This article describes how to configure object storage where it uses ViPR-managed files systems as the backing storage.

This article applies to EMC ViPR 2.0.

Where you intend to use ViPR-supported file storage systems to support ViPR object storage, you need to install one or more data services node vApps to provide access to this storage.

If you are using commodity nodes to provide your object storage capability, you should refer to the ViPR Installation and Configuration Roadmap.

Back to Top

Where next?

Once you have complete the steps in this article and configured object storage on ViPR-managed file systems, your next steps depend on the Data Services that you want to use.

Back to Top

Understanding ViPR Object Storage on ViPR-Managed File Systems

ViPR object storage on ViPR-managed file systems uses NFS exports as the data stores which underpin the object storage capability. The data stores must be associated with an object virtual pool as it is the object virtual pool that an object client sees and in which it creates buckets.

The link between a virtual pool and its data stores is made through the virtual array: a virtual pool is associated with one or more virtual arrays and will have all of the data stores that belong to its associated arrays.

You can have more than one virtual pool, which means that different pools can have different performance and protection characteristics based on the virtual arrays (and their constituent data stores) that are assigned to the object virtual pool. Hence, if you want a virtual pool to have specific performance and protections characteristics, you should ensure that all data stores created in a virtual array have the same characteristics.

The first virtual array that has a data store associated with it becomes the system virtual array. The system virtual array is used to store metadata for the object store, such as indexes and other structures, and the data stores associated with this virtual array cannot be deleted.

The figure below shows how a virtual pool is associated with one or more virtual arrays, which have one or more data stores, and shows that a virtual pool can extend across more than one ViPR VDCs/sites.

Virtual pool to virtual array relationship

Back to Top

Step-by-step: Configure object storage using ViPR-managed file storage

This topic provides an overview of the sequence of steps that you will need to perform to configure object storage on ViPR-managed file systems. The details of each step are provided in the topics that follow.

Before you begin

  • Ensure that you have installed one or more ViPR data services nodes.

    Refer to the article: Install ViPR Data Services Node.

  • Ensure that you have created a file virtual pool that can provide the backing storage for your object stores.

    Refer to the article: Create Virtual Pools for File Storage in ViPR.

  • A project must have been created for the tenant so that it can be assigned as the default project for the tenant. You must have access to the project in order to perform the assignment. If a project does not exist, you should ask the Tenant Administrator to create the project and give you access to it.

    For more information on projects, you can refer to: Create ViPR Projects.

  • To set up object storage you will need to have the System Administrator role and, for some configuration tasks, the Security Administrator role.

  • If you are using EMC Isilon, your DNS server must be configured to delegate resolution of the Isilon SmartConnect name to the SmartConnect service. The SmartConnect service returns the IP address used to connect to the Isilon cluster based on the load balancing policy that has been selected.

Procedure

  1. Create one or more data stores that will provide backing storage for your object store.
  2. Create an object virtual pool. This can also be geo-replicated.
    An object virtual pool comprises one or more virtual arrays and all of the data stores within a selected virtual array will be added to the object virtual pool.
  3. Set up the tenant to use the object storage.
    Before object storage can be used, a namespace must be assigned.
  4. (Optional). If tenants want to use Data Services using existing s3 clients, add a Base URL that will map their existing URLs to the ViPR object store.

Results

Once the steps have been performed, you have an object storage capability able to support various ViPR data services.

Back to Top

Create an object data store on a ViPR-managed file system

Where object storage is provided by ViPR-managed file storage systems, an object virtual pool is backed by one or more data stores. A data store is a file system export created from a storage pool on a ViPR-managed array. The physical storage pool that hosts the data store is chosen automatically by ViPR based on the file virtual pool chosen.

Before you begin

This operation requires the System Administrator role in ViPR.

Procedure

  1. In the Admin mode, select Virtual Assets > Data Stores.
  2. At the Data Stores page, select Add.
  3. Enter a name for the data store.
    The data store name can reflect the underlying file system storage that provides the data store.
  4. Optionally, add a description for the data store.
  5. Select the virtual array that will provide the data store.
    The first virtual array that has a data store associated with it becomes the system virtual array. The system virtual array is used to store metadata for the object store, such as indexes and other structures, and the data stores associated with this virtual array cannot be deleted.
  6. Select the file virtual pool that will provide the file system that underlies the data store.
    The file virtual pools that you are be offered are those associated with the selected array.
  7. Enter the size of the data store.
    A value of at least 50 GB must be specified.
  8. Select Save.

Results

The state field in the Data Stores table is initially "Initialized". When the data store has been created and is ready, "Ready to Use" is displayed.

Back to Top

Create an object virtual pool

Object storage is provided by object virtual pools, where an object virtual pool comprises all of the object storage associated with one or more virtual arrays. Where you have multiple ViPR sites, an object virtual pool can span more than one site.

Before you begin

The following prerequisites apply:
  • This operation requires the System Administrator role in ViPR.
  • If you are using ViPR-managed file systems to support object storage, one or more data stores must have been created for any virtual array that you want to associate with an object virtual pool.

  • If you want to configure the object virtual pool for geo-replication, you must first set up a ViPR multisite configuration.

Procedure

  1. Select Admin > Virtual Assets > Object Virtual Pools.
  2. Select Add.
  3. Enter a name and a description for the virtual pool.
  4. To add a virtual array, select the VDC and choose an array from the selected VDC that will contribute object storage.
    The object virtual pool will use any data stores that have been created in the virtual array. If you have data stores associated with more than one virtual array, you can also add those virtual arrays.
  5. To add other virtual arrays from the same site, or from a different site if you have a multisite configuration, click Add Virtual Array and choose a further VDC and associated virtual array.
    Adding virtual arrays from another site (VDC) will cause data to be replicated across the sites.
  6. Select Save.
    The virtual pool will be displayed on the Admin > Virtual Assets > Object Virtual Pools page.

Back to Top

Configure a tenant to use Data Services

You can use the ViPR UI to configure the namespace for a tenant and configure default values for the object virtual pool and the project to which object storage for this tenant should be assigned.

Before you begin

  • The System Administrator role is required to access the User > Tenant Settings > Data Services Settings page.
  • A virtual pool with at least one data store assigned must exist and be available to the tenant.
  • A project must have been created for the tenant so that it can be assigned as the default project for the tenant. You must have access to the project in order to perform the assignment. If a project does not exist, you should ask the Tenant Administrator to create the project and give you access to it.

The root user account has these roles and can be used to perform this task.

Procedure

  1. Select User > Tenant Settings > Data Services Settings.
  2. If more than one tenant has been created, select the tenant for which you want to set the namespace from the tenant drop-down menu.
  3. Enter the identity of the namespace to use for this tenant.
    The namespace must be unique for each tenant in the same ViPR virtual data center.
  4. Select the default virtual pool.
    This is the default virtual pool in which to store, and from which to retrieve, objects. When using the ViPR Object Service, if a client does not specify a virtual pool, the contents of the default virtual pool that is visible to the logged in user will be returned by ViPR.
  5. Select the project that you want to assign as the default for the tenant from the list of projects to which you are assigned.
    When buckets are created they are assigned to projects so that the project can be used to meter operations on the object store.
  6. Select Save.