ViPR was launched with tremendous fanfare at EMC World last year (how time flies!). The product went GA in Sept 2013.
The key premise behind ViPR is that data center management has become too complex. As obvious as this problem is, it is a herculean task to address. I doff my hat to the ViPR team. They have taken a very complex challenge and built a product that they can be justifiably proud of.
Over the last few months, a number of customers have deployed VPLEX together with ViPR and used ViPR to simplify their management infrastructure. Our team has put together some demos to help explain how ViPR and VPLEX integrate.
We will be adding voice-overs at a later point in time but it seemed useful to make these available to customers to help them understand the value of VPLEX with ViPR.
Configuring VPLEX within ViPR
This demo shows you how to configure VPLEX within the ViPR context. ViPR takes over after the basic configuration of VPLEX (i.e. set up from a network accessibility standpoint).
- A VPLEX cluster gets configured as a virtual array within ViPR. For a VPLEX Metro, this equates to creating two virtual arrays.
- From there, you need to expose the network elements from the SAN to the specific VPLEX cluster.
- You can now create virtual pools describing what type of storage to provision. Based on the SAN exposed, you get options for which storage can be exposed to which VPLEX cluster. Based on the configuration of the pools, you can assign different properties to VPLEX pools
Note that this is a one-time configuration for a given virtual pool. This sets you up for end-to-end provisioning!
Provisioning VPLEX within ViPR
This now operationalizes what was set up in the prior demo. The first step relates to selecting the virtual array and a virtual pool and then creating a distributed volume. THe next step involves taking this volume and exposing this volume to the host. No zoning, no moving between multiple GUIs, all available with ease.
Deprovisioning VPLEX within ViPR
This is the flip side to the prior demo. Here the volumes that are exposed to the host are deprovisioned. Again, same paradigm as before. The orchestration happens through the ViPR controller and it is all in one interface.
Migration of Pools through ViPR
This takes the migration use-case and converts it into the catalog view. The change pool catalog request results in migration of volumes from one array to another. THe orchestration is at the pool level so you can migrate from one array or one tier to another.
This is just the beginning – we are looking at more complex use-cases to deliver a seamless experience to our end customers. You will hear more about this in the near future. What do you think?