Chris Evans of Architecting IT Blog comments:
Every so often another attempt is made by the vendor community to put a definition to what we call “software defined storage” or SDS. The current discussion is on VMware Virtual SAN (VSAN) and VVOLs, software features focused on storage within the vSphere hypervisor ecosystem. This seems like a good opportunity for me to review what I’ve written in the past and see if there’s an improvement to be made to my existing definitions. It’s also an opportunity to explain why I don’t think VSAN or vVOLs are truly software defined.
An interesting take from Chris on the new storage offerings from VMware. Do you think they fit into the software defined mold?
Read more at: Why VSAN and VVOLs are Not Software Defined
- Unmasking Bad Actors with Gigamon - December 7, 2017
- Dedicated Wireless Troubleshooting Doesn’t Have To Break The Bank - November 28, 2017
- Are Vendors and VARs The Enemy? - November 15, 2017
- Pluribus Networks Is the Definition of “Software Defined” - November 2, 2017
- First American Title And Viptela: A Story of Resilience - October 4, 2017
- Flexible NFV with Array Networks - August 7, 2017
- Cloud onRamp – Making The Cloud More Local For Your Users - July 26, 2017
- Feeling Your Flow with Plixer - July 19, 2017
- What Are ASICs? A Human Example - July 11, 2017
- Migrating to Healthcare Cloud Apps With Acadia and Viptela - June 5, 2017