Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

424

July 9th, 2014 06:00

ViPR Federation

In a multiple federated ViPR deployment (3 distinct controller instances for example), if an instance is taken offline  for maintenance like a data center power down, would a user be able to go to one of the other instances and be able to control both that are still on line?

In other words, is one identified as the "master" or do they all federate and synchronize to each other?

July 9th, 2014 11:00

Hi,


The just-released ViPR 2.0 Controller introduces the capability of Geo Scale Deployment for file and block storage. This capability supports single sign-on, global namespace for ViPR Projects and Tenants as well as aggregated reporting across all ViPR instances. No one ViPR instance needs to be identified as “master”. The key use case for having separate ViPR instances is to be able to manage those datacenters individually while having common security configurations across the entire environment. The physical storage systems, SANs and hosts as well as ViPR abstractions of virtual storage array and virtual storage pool are local to a ViPR controller instance for block and file storage. 

Customers  who want to centrally manage all the data centers should use a single ViPR instance. With ViPR 2.0, a ViPR administrator can manage ViPR-supported storage, SANs, and users from a single pane of glass regardless of physical location. ViPR’s distributed model makes it very robust in case of virtual machine (VM) failures. Since ViPR is a virtual appliance, ViPR VMs can be moved to another data center through VMware Site Recovery Manager and can be powered up, if there is connectivity in that site to ViPR  managed systems.

For more information, read the article about how to plan and deploy multisite EMC ViPR on EMC.com.

Thanks,

Dee

No Events found!

Top