Some questions and discussion topics pertaining to ViPR:
Whom is ViPR for?
Organizations that need to scale with stability across EMC, third-party or open storage software stacks and commodity hardware. This applies to large and small enterprise, cloud service providers, managed service providers, virtual and cloud environments/
What this means for EMC hardware/platform/systems?
They can continue to be used as is, or work with ViPR or other deployment modes.
Does this mean EMC storage systems are nearing their end of life?
IMHO for the most part not yet, granted there will be some scenarios where new products will be used vs. others, or existing ones used in new ways for different things.
As has been the case for years if not decades, some products will survive, continue to evolve and find new roles, kind of like different data storage mediums (e.g. ssd, disk, tape, etc).
How does ViPR work?
ViPR functions as a control plane across the data and storage infrastructure supporting both north and southbound. northbound refers to use from or up to application servers (physical machines PM and virtual machines VMs). southbound refers target or destination storage systems. Storage systems can be traditional EMC or third-party (NetApp mentioned as part of first release), appliances, just a bunch of disks (JBOD) or cloud services.
Some general features and functions:
- Provisioning and allocation (with automation)
- Data and storage migration or tiering
- Leverage scripts, templates and workbooks
- Support service categories and catalogs
- Discovery, registration of storage systems
- Create of storage resource pools for host systems
- Metering, measuring, reporting, charge or show back
- Alerts, alarms and notification
- Self-service portal for access and provisioning
ViPR data plane (adding data services and value when needed)
Another part is the data plane for implementing data services and access. For block and file when not needed, ViPR steps out-of-the-way leveraging the underlying storage systems or services.
When needed, the ViPR data plane can step in to add added services and functionality along with support object based access for little data and big data. For example, Hadoop Distributed File System (HDFS) services can support northbound analytic software applications running on servers accessing storage managed by ViPR.
Continue reading in part III of this series here including how ViPR works, who it is for and more analysis.
Ok, nuff said (for now)
All Comments, (C) and (TM) belong to their owners/posters, Other content (C) Copyright 2006-2013 StorageIO All Rights Reserved