What Happens in Vegas (Amcom at EMC Global Forum)
0 likes1,327 views
The document discusses advancements in data management and storage solutions, highlighting products like the vnxe3200 and dssd, along with new software features such as vipr 2.0. It outlines improvements in system performance, integration capabilities, and compliance, emphasizing the shift toward more agile and scalable technology for businesses. Additionally, the document touches on upcoming events and opportunities for collaboration and learning in the field of data services.
What Happens in Vegas (Amcom at EMC Global Forum)
- 3. Pivotal 3 › Spin out from EMC and GE Focused on: › Platform-as-a-Service (PaaS) › Pivotal Web Services › Pivotal CF › Big Data › Extraction of business value from the Data Lake › Agile Software Development › Open Source
- 4. Information Value 4 › How much is your information worth to you? › How much is it worth to your business? › How much is it worth to your competitors? AFR – 12 May 2014
- 6. Data Lake 6
- 7. VNXe3200 7 › New Entry Level System › 8 Sandybridge cores › 48GB of system memory › 8x10GbE ports › Up to 4x8Gbps FC ports › 25 spindles in 2U (expandable) › Full FAST-VP/CACHE on entry level platform › 3x uplift in system performance (compared to previous generation) › Full protocol support (FC, FCoE, iSCSI, NAS) › VSI/ESI integration
- 8. VNX D@RE 8
- 9. Data Domain 2200 9 › DD2200 will replace 1xx systems › Hardware Features: › Includes new quad-port 10Gb SLIC › Up to 860TB logical capacity (17.2TB useable) › Performance Features: › Up to 4.7TB/hr for aggregate writes using DD Boost › Up to 3.5TB/hr for aggregate writes using CIFS › Increased Stream Counts for backup and archive workloads › VTL Enhancements: › VTL Configuration backup and restore utility, Library and driver emulation enhancements and option changes
- 10. ViPR 2.0 10
- 11. ViPR 2.0, Extending Array Support 11
- 12. ViPR 2.0 12 › ViPR 2.0 – Controller Enhancements: › Enhanced Native Array Support › Commodity Platform Support › 3rd Party Plug-in Support › Centerra-level compliance › Brownfield Deployment › Improved VPLEX & RecoverPoint management › Multi-tenant and Multi-site capable › ViPR 2.0 – Service Enhancements: › Geo-replication and Geo-distribution › ViPR Block – ScaleIO › Services on commodity hardware › Compliance › ViPR CAS
- 13. ViPR 2.0, SRM 3.5 13 › Improved ViPR Controller Integration › Improved virtual-physical mapping › New ViPR/VPLEX chargeback › VPLEX Integration › VPLEX topology reporting › Service Level Mapping › New performance reporting
- 14. ViPR: Software Defined Storage 14 ViPR 2.0 data services bits will be available in the same way that as ViPR controller Open, and freely for non-production use. Current bits: http://www.emc.com/getvipr?pid=pands-vipr-100314
- 15. VPLEX VE 15 › VPLEX VE: hardware-independent virtual appliances for ESX › Managed through vSphere › Continuous operations › Instant non-disruptive load balancing › Stretched ESX cluster › iSCSI only
- 16. Project Unity 16 This VNXe 3200 release merges in the MCx code into the C4 package: It’s critical to internalize this. In the VNXe, while it shares “familiness” and functional codebase with the VNX (common features, user experience)… the VNXe has a single linux-based kernel (no “block stack” + “file stack”), and fits it all into a much smaller footprint (no “Storage Processors” + “Datamovers”). A litmus test is that VNXe has no trace of any Windows kernel.
- 17. Project Liberty: aka vVNX 17 The Unity codebase in the VNXe is also the right vehicle for making the “SDS version” of the VNX code stack (for it’s data services) widely available. It’s simpler, it’s smaller, and it’s kernel is linux and can be redistributed and therefore be “free” of some of the external restrictions that have made the current “VNX VM” be held under lock and key inside the walls of EMC and EMC vLab. This is the essence of “Project Liberty” (more on this in an upcoming post – wait for it!!!). What could it be used for? One example would be for Test/Dev, one would be for a multi-tenant use case (everyone gets their own VNX!… All running on a big ScaleIO pool). http://virtualgeek.typepad.com/virtual_geek/2014/05/vnx-architectural- evolution-keeps-rolling-vnxe-3200-project-liberty.html
- 18. Who wants $1,000,000? 18 › Free snapshots: no performance impact, no limits. The OLTP use cases with XtremIO just got more Xtreme. › AIX support! › ViPR Controller support is coming shortly.
- 19. vHANA 19
- 20. DSSD Acquisition 20 › True “top of rack, pooled server-memory-flash” › New density and performance envelope in a “new category band”
- 21. It’s about the app 21 2nd Platform vs 3rd Platform requirements
- 22. DSSD – In memory models 22 › What do these new “in memory” models need, or for that matter low-latency NoSQL/SQL distributed databases? Frankly – commodity servers, but with gobs of bandwidth, INCREDIBLY low latency, and gobs of memory (and in this case, latency is everything).
- 23. DSSD Architecture 23 › DSSD is TRUE “top of rack, pooled server-memory-flash”. It has a density and performance envelope in a “new category band”. › DSSD Architecture: DSSD is very dense package of flash (for a ton of IOps), each with a small controller (all grouped and pooled together) and even lower latency memory to “buffer” the flash latency – and interconnect to hosts via a super-low-latency interconnect. How dense? Think “order of magnitude” over current options. Add in the software to manage, pool, automate – and ultimately present in different ways, and you have our “5th Phylum”.
- 24. DSSD – Draft Architecture 24 › DSSD – doesn’t require any of the file/block semantics between the flash read/write model. It can expose this via libHDFS or object semantics, or directly mapping to key value stores (with a PCIe/NVMe connection). If you want direct memory mapping over RDMA and over direct PCIe NVMe, it can do that too! › Here’s how the stack compares with local server HDD and SSD/PCIe- attached “DAS” vs. DSSD’s shared direct access model.
- 25. Where does DSSD fit the ecosystem? 25
- 26. Futures 26 › MetroPoint – combination of VPLEX and RecoverPoint › New Syncplicity App › Project Mercury › Per VM replication from vSphere kernel › Independent of storage vendor
- 27. More Information 27 › EMC World Online http://www.emcworld.com/virtual/index.htm?cpm=emc-335228- TY&M=81D15A02-8731-4F18-A880-E8E2DED0AD04 › EMC World TV http://www.emcworld.com/emctv.htm › EMC Forum http://australia.emc.com/campaign/global/forum2013/event.htm − Sydney 13 August, Melbourne 16 August − Amcom are sponsoring, hope to see you there
- 28. What Was Cool 28 › Hundreds of Hands-On-Labs › Replication of information to vCHS › Ability to discuss with Engineers about the products › Discussions with other vendors such as SAP, Cisco, Oracle, VMware › Networking with APJ colleagues › Futures Sessions – Area 52 and Area 53 › More Information than we could take in!
- 29. Questions? 29
- 30. Thanks 30