The below video shows how you can start (very) small with Nutanix, and scale to 1 Million IOPS and beyond in a linear fashion, in one node, or one block (4 node) increments and enjoy linear scalability.
http://www.youtube.com/watch?v=B-RBDtKgQTo&feature=youtu.be
So next time your looking to buy storage, why not buy what you need today, and not what you might need in 3 or 5 years time, and scale incrementally as required without the need for controller head swaps, or throwing out any equipment.
Problem Statement
What is the most suitable storage protocol for a Virtual Desktop (Horizon View) environment using Linked Clones?
Assumptions
1. VMware View 5.3 or later
Motivation
1. Minimize recompose (maintenance) window
2. Minimize impact on the storage array and HA/DRS cluster during recompose activities
3. Reduce storage costs where possible
4. Simplify the storage design eg: Number/size of Datastores / Storage Connectivity
5. Reduce the total solution cost eg: Number of Hosts required
Architectural Decision
Use Network File System (NFS)
Justification
1. Using native NFS snapshot (VCAI) offloads the creation of VMs to the array, therefore reducing the compute overhead on the ESXi hosts
2. Native NFS snapshots require much less disk space than traditional linked clones
3. Recomposition times are reduced due to the offloading of the cloning to the array
4. More virtual machines can be supported per NFS datastore compared to VMFS datastores (200+ for NFS compared to max recommended of 140, but it is generally recommended to design for much lower numbers eg: 64 per VMFS)
5. Recompositions/Refresh activities can be performed during business hours, or at Logoff (for Refresh) with minimal impact to the HA/DRS cluster, thus giving more flexibility to maintain the environment
6. Avoid’s potential VMFS locking issues – although this issue is not as important for environments using vSphere 4.1 onward with VAAI compatible arrays
7. When sizing your storage array, less capacity is required. Note: Performance sizing is also critical
8. The cost and complexity of a FC Storage Area Network can be avoided
9. Fewer ESXi hosts may be required as the compute overhead of driving cloning has been removed thus reducing cost
10. VCAI is fully supported feature in Horizon View 5.3
Implications
1. The Storage Array supports NFS native snapshot offload to enable the full benefit of NFS (VCAI clones) however all other benefits remain without VCAI support.
Alternatives
1. Use VMFS (block) based datastores via iSCSI or FC/FCoE and have more VMFS datastores – Note: Recompose activity will be driven by the host which adds an overhead to the cluster. (Not Recommended)
At this months vForum in Sydney, Australia, I will be presenting “Taking vSphere to the Next Level with Converged Infrastructure”.
The session discusses where the virtualization market is today along with problems that exist along the journey to 100% virtual and how converged infrastructure helps solve these challenges allowing vSphere architects and administrators to take their virtual environments to the next level.
The session is scheduled for Day 2 of the conference (October 22nd) at 11AM in Parkside 110A room.
I invite everyone who will be at vForum Sydney to attend the session, and for those of you who cannot make the event, the presentation will be posted on this blog along with follow up articles covering any questions from the session.