Sneaky Peak – NetApp Plug-in
This afternoon (well my evening actually) I got a sneaky peak at NetApp’s new plug-in to vCenter dubbed the NetApp RCU 2.1. I was joined in the web-ex by fellow blogger Scott Lowe, and by Eric Forgette, the key architect/developer for RCU – in case you don’t RCU stands for Rapid Cloning Utility. Put simply the RCU leverages the functionality of a NetApp array to quickly duplicate VMs, with the strongest usage case being VDI of course. NetApp has been doing this sometime – and the early videos of them creating numerous VMs for VDI via script has gone down in youtube history… Anyway, that functionality of cloning is available to all NetApp customers free of charge, without the need to learn any fancy scripting. Let me give you a walking tour of the new RCU. Full details will be available when it is offically launched at VMworld this year.
Firstly, the RCU automates the duplication process as can be seen from this image:
Here you can see you can easily call up N number of clones, and set their naming convention (Win2K3-NN). The RCU intregrates with your Guest Customization Settings – and so will sysprep the VMs as it clones them. If you run the new RCU on vSphere4, it will leverage the new vStorage APIs, so the ESX hosts takes NO load during the provisioning process – it merely sends instructions to the NetApp box, to say go ahead and duplicate these VMs for me. All the load is on the NetApp box not on your ESX host. You can also see that the RCU allows these VMs to be advertised either to VMware’s View product or Citrix’s Xen Desktop.
During this provisioning process – you can also provision new storage for the VMs, and set some specific NetApp parameters like enabling thin-provisioning or auto-grow…
Toward the end of the RCU process you can configure how the virtual desktop will be presented to the end-users using desktop pools within VMware View.
In my discussions with NetApp they came across as quiet neutral on what is the best method for deploying VMs for VDI. In some cases VMware Views own “linked clones” method might be more suitable than the RCU especially for desktops that have a very short life span, whereas NetApps RCU might pay more dividends for long-term virtual desktops where folks return to the same desktop time and time again. So it really does seem to depend on your circumstances and what you are trying to achieve. Interestingly, NetApp’s own R&D indicates that customers perfer to have BOTH methods at their finger tips – strategically using what ever method suits their purposes for the given scenario…
NetApp’s integration with VMware does begin and end with a Rapid Cloning feature – although for the moment the plug-ins main functionality is dominated by that very issue. There other interesting add-ons in the new plug-in. For instance it now adds a right click functionality to your NetApp NFS mount points as the screen grab blow shows:
So the new RCU allows you to handle NetApps de-duplication features, resize volumes and destroy volumes (yes, that’s a little scarey it literally shutdowns the VMs on the volume, unregisters them from ESX hosts and blows the storage away!). By the far my favourite was the resize option. It’s a right-click, increase the size – and bob is your father’s brother!
As the right-click menu shows - you can handle some deduplication settings here as well.
And it doesn’t stop there NetApp are exposing to the vSphere client advanced settings in the shape of what they are calling the Virtual Storage Console…
Verdict: All in all it looks like VMware’s Plug-in/vStorage/vNework/vWhatEver strategy is paying some early dividends. With various vendors like NetApp, EMC, Cisco and others – falling over themselves to give VMware guys more visability and control over the physical components of the virtual infrastructure right-from-within the vCenter client. Of course there will much talks of rights & privileges here, the VMware guy is getting alot of control over the storage – but heck, that is increasing the case – with many an admin being lumbered not with VM/VMware management – but storage & network as well! Additionally, there will be much talk of vCenter becoming the single-pane-of-glass window on your infrastructure – by partnering/collaborating with other companies – they’ve demonstrated whats possible. Expect more of this in the future….














August 12th, 2009 at 2:59 am
This is very cool!!!
Will NetApp support the Quest or Leostream Connection Brokers?
Most of my customers prefer either one of these connection brokers rather then the VMware or Citrix versions.
August 12th, 2009 at 8:52 am
The quick answer is – I don’t know. It looks unlikely given this preview of the RCU shows only VMware/Citrix brokers….
August 12th, 2009 at 9:36 am
Hi – maybe I can help answer that question…
The Rapid Cloning Utility can be used to provision desktop VMs, which can then be brokered via Quest, Leostream, or any other connection broker.
It’s just that in the case of VMware View and the Citrix Desktop Delivery Controller (part of the XenDesktop suite), the RCU can automatically make those brokers aware that new desktop VMs have been provisioned – by defining a new pool to use those VMs, or addding the VMs to an existing pool.
As an interesting alternative, Quest have recently released vWorkspace 6.2, which has NetApp integration built in (see http://blogs.inside.quest.com/provision/2009/08/04/quest-vworkspace-62-released/).
August 12th, 2009 at 12:33 pm
Hi,
I work as Reference Architect in the Server and Desktop virtualization business unit at NetApp and responsible for developing NetApp VDI best practices and support partner integration.
The good news is that Quest vWorkspace 6.2 now directly integrates with NetApp rapid cloning. Check out this link for further details.
http://blogs.inside.quest.com/provision/2009/08/04/quest-vworkspace-62-released/
Currently with Leostream, you can easily import the VMs into the connection broker once they are created and populated in vCenter.
Please email me at abhinavj@netapp.com if you have further questions.
Regards,
Abhinav
August 12th, 2009 at 1:02 pm
Hi Mike,
do you know if RCU 2.1 and the Virtual Storage Console will also be available for VI3 environments? Because the RCU 2.0.1 is also available for VI3.
thanks
August 12th, 2009 at 3:18 pm
Quest vWorkspace is is fully integrated with NetApp cloning and dedupe technology!
http://blogs.inside.quest.com/provision/2009/08/04/quest-vworkspace-62-released/
Enjoy!
V
August 12th, 2009 at 5:37 pm
The RCU supports VI3 today. The initial release of the VSC requires vCenter 4 and it can report on VI3 hosts but cannot automate config changes as the APIs between ESX/ESXi 3 & ESX/ESXi 4 servers is different.
August 14th, 2009 at 1:06 pm
The NetApp/VMware/CISCO Reference Architecture highlighting the joint power of VMware linked clones and NetApp RCU can be found here:
http://blogs.netapp.com/virtualization/2009/06/new-cisco-vmware-netapp-vdi-design-guide-tr3770.html
http://www.vmware.com/resources/techresources/10051
August 20th, 2009 at 1:22 pm
Great tool! What is the license model for RCU 2.1? What is NetApp’s support policy?
August 24th, 2009 at 12:50 am
Bruce – The RCU is a no cost tool which is fully supported as long as the NetApp storage arrays managed by the RCU are under support.