Dell, EMC, Dell Technologies, Cisco,

Wednesday, March 15, 2017

What You Can (and Cannot) Change in a vSAN ReadyNode™

#vSAN has taken the #HyperConvergedInfrastructure ( #HCI ) market by storm and more than 7,000 customers have now adopted vSAN with thousands of deployments, confirming its position as the leading product in hyper-converged infrastructure (HCI). One of the consumption models of vSAN software is ReadyNodes and today we have more than 200 ReadyNodes listed in vSAN VCG from OEM partners across the globe.

So what are vSAN ReadyNodes?

vSAN ReadyNodes are x86 servers, available from all the leading server vendors, that have been pre-configured, tested and certified for VMware Hyper-Converged Infrastructure Software. Each ReadyNode is optimally configured for vSAN with the required amount of CPU, memory, network, I/O controllers and storage (SSDs, HDDs or flash devices). Each ReadyNode listed in vSAN VCG has an SKU. You can enter that SKU into OEM partners’ system configurator and it will generate a BOM that is “flexible”.

We often get asked by our field, partners and customers that “Can a ReadyNode BOM be changed?” e.g. can we use another capacity tier device or use a better processor than listed in the BOM. The short answer is “Yes” – there are things in a vSAN ReadyNode BOM that you can change and there are things you cannot.

To provide guidelines for what can be changed in a ReadyNode, we are taking a two-phased approach.

Provide guidance to customers, partners and field on what we allow to modify within a vSAN ReadyNode BOM today by means of this blog which will be linked to the official vSAN VMware Compatibility GuideSubsequently, build a tool which enables customers, partners and field to select changed configuration automatically and create in runtime a vSAN ReadyNode BOM from supported list of components on the vSAN VCG.

In this blog, I will outline first approach “Guidance on which the tool is going to be built upon”.

https://blogs.vmware.com/virtualblocks/2017/03/14/can-cannot-change-vsan-readynode/

No comments:

Post a Comment