Over the past few months I have been working with a variety of customers on either enabling vSAN encryption on existing / scaling vSAN clusters or working with large scale customers enabling it for the first time.
I had a great opportunity to bring stories together into a single presentation with the team at VMware Learning Zone.
I had great fun on this Webinar episode discussing the vSAN Encryption architecture, touch points and most importantly the day 2 operation considerations of running this technology at scale.
As promised the diagram and mind map I used in the webinar are available below.
One of the important areas of any physical design is to create an appropriate bill of materials (BOM).
Matching infrastructure or software features that meet business requirements is an important skill, initially for design success, but also in a lot of cases for the impact to the cost of projects at the running phase.
For example, understanding feature use, scaling factors at different phases of a road map plan and any EULA restrictions (Number, site locality, combination, etc) are critical to aid operational management.
Over the past few weeks, I have had the pleasure to present a series of “Operationalising vSAN” workshops. Although not specifically involving licensing, a common question is “What feature, to which vSAN Edition” & “What are the guidelines”.
Here is my mind map which I have used when discussing the subject.
Recently I have had some very interesting conversations on the use of “2 Node” and “ROBO” with vSAN.
Where does it fit in the enterprise? When should a business use this approach etc?
It appears that the use of the terms “ROBO” and “2 Node” have also become interchangeable with respect to vSAN.
With the flexibility and features within the vSAN editions, it could be easy to misunderstand the concepts and use cases for this architectural approach and not consider the opportunity that is there for a ROBO deployment.
Based on a variety of workshops and discussions I thought I would highlight;
Some common architectural thoughts for vSAN ROBO.
vSAN ROBO is designed for platforms outside of a companies HQ or datacenter.
It is not a 2 node only SMB solution, it is a scalable architecture with can start with 2 nodes running workloads & grow to maximums such as 64 nodes.
Using a repeatable design approach in & outside the corporate DC can help simplify storage needs, cost, time & operational management.
From an architecture perspective, 2 nodes can be used with any vSAN version,while ROBO is a licensing approach with flexible deployment configurations based upon the number of VMs rather than sockets.
It is possible to expand a 2 node platform to a larger platform without an outage.
A 25 VM limit is based on powered on VMs and can be flexibility split between the site / VM number combination (ie 25 VMs across 4 locations) providing some real cost savings but still maintaining enterprise level storage experience.
There are different network requirements with ROBO topologies that can potentially make vSAN appropriate to provide availability, security, and automation for applications which have to run locally with localized constraints and limited IT.
To aid discussions I have created a summary mindmap on the subject and listed some useful links below for more information.