نصب و پیکربندی EMC ViPR for dammies

نصب و پیکربندی EMC ViPR for dammies

On EMC ViPR and ViPR SRM we could listen on a recently EMC Forum 2014 conference in Warsaw. It is quite a new solution from EMC, showing exactly how the company sees the software-defined storage. What really is ViPR? In the huge simplification, this is a storage management (monitoring and reporting) system. At some stage replaces the storage management consoles (eg. Isilon, VNX, and others) providing a consistent interface between users requirements (for space) with the function of the management and distribution of space for those users (eg, individual or bussines groups). What ViPR is not? It is not a storage virtualizer (please keep this in mind). The same solution is very cheap, for $ 10k you get a full set of license for a huge number of Terabyte. Fortunately, we do not need to buy EMC ViPR for testing purposes, they can be downloaded directly from EMC(version for three or five nodes) with unlimited time license (for 300T). Or traditionally,from me (single-node version). As the ViPR appliance is quite demanding with respect to RAM (installed with 16GB but works fine on 8GB), a one-node version for test is enough. In this post I will show you how to take the first steps in ViPR so we do not get lost. This will help you get an idea of what lies behind this solution. In test we  use as a backend earlier installations of EMC Isilon and EMC VNX for File.

The first stage is a standard appliance OVA upload, providing all the necessary parameters.

Log in to web interface as root/ChangeMe, after logging in (and change the password) you must upload the license file (ViPR_Controller_License.lic). After this step, we have to wait for a while:

Then, go to the “Settings -> Configuration properties -> Upgrade” and enter the address of our proxy (if you have) and EMC account through which we will authorize in the EMC:

Now go to the section “Settings -> Upgrade” and install the latest version of ViPR:

After the upgrade, which takes quite quickly, we can proceed to set up a whole environment so as to be able to export the disk resources. We start by going to the “Security-> Authentication Providers” where we add the “user source”, in 99% of cases this will be an Active Directory domain (if you omit this step, we will have to do everything as root):

Now go to the “Tenant Settings -> Tenants” and create our first tenant. In the same place, map users who can access it, attributes can be any (compatible with AD). For example, this may be the name of the AD group. Added user has basic rights, can log into ViPR and apply for resources (and nothing else).

Create and map the tenant roles. Mapping the role is nothing else that grant of the relevant group (or user) from Active Directory high level permissions in tenant:

Next we create our first project in which resources will be allocated, in this case we will do it as root. Or you login in a tenant and prepare a project within its own structure (object added as root are available globally):

Tenant issues, projects and relevant permissions have terminated. Time to go to configure “physical” resources and translate them into “virtual”. Go to the section “Physical Assets -> Storage Systems” and add our storage systems:

Every time storage added, ViPR inspect the system, analyze and automatically adds available pools:

For file services, it is worth remembering that the “port” should match the FQDN of the storage issuing the service. The figure below is equal to the port name called SmartZone with Isilon. If at this point will be traveling (eg. name of the SmartZone or VNX interface do not correspond to the DNS names of devices), it will be not possible to export volumes via NFS. (End up with a message: “Operation failed, diagnostic report: Unable to resolve hostname ‘xxx’.” on vCenter side):

The next step is to create our first virtual disk array and give acces to it to our tenants:

Next, go to the section “Physical Assets -> Networks” and add a new “network”. The network is nothing else, that the point of joining the “Storage Ports” in the groups that we can assign to the virtual array. In this way, we can quite freely mix access to data resources for specific tenants (eg. Business groups).

In this momment we configure File resources, so we go to the “Virtual Assets -> File Virtual Pools” and add a new pool. This resource must be assigned to a specific virtual array:

In the hardware, available resources are prompted automatically (our Isilon) in accordance with selected settings (if poorly “Networks” configured, we do not go this step). At this point, we have a fully configured and equipped virtual disk array:

It remains for us to add vCenter to which we export volumns via NFS. This step is not mandatory, we might as well define single hosts (Windows, Linux, whatever). ViPR will recognize the full configuration of vCenter, including information about the hosts and clusters.

Now we have everything that we need to prepare our first file system and export it to our vCenter. We can do this as root, but of course it would be better to do it as a tenant member. A new resource conclude in the “Service Catalog -> View Catalog -> File Services for VMware vCenter.” Depending on how you make the privileges, resource get immediately or we will have to wait for the approval of our request.

These two steps are completed as the root user, thus added vCenter is available globally for all tenants. But it is enough relogin to the user who manages the tenant and see that it can add another vCenter themselves (vCenter can not be duplicated).

And that’s basically all when it comes to ViPR controller operation logic. Very encourage you to test this solution, in the next post I will try to show the principle of the EMC ViPR SRM operation. And finally, answer the question “is it worth it?” Initially, the idea itself seemed quite strange, but the longer I use it, the more I find that it is sensational. EMC ViPR does not replace the administrative panel of the storage, you can not set anything complex in the ViPR. However, replaces and simplifies all operations on volumes (create, export). The more complex storage environment is, the more useful is the ViPR !

EDIT:

Error: ViPR VM lost network.

Reason: You move ViPR to another vApp, do not this, the VM settings are get from vApp settings.