In this series of articles we will be looking at the new generation of VMware vSphere 4 plug-ins that make it increasingly easier to see your storage from the vCenter/vSphere client. In addition you will learn how the NetApp Rapid Cloning Utility is not just a virtual machine (VM) copying tool, but also allows you to quickly and easily create and mount new data stores without needing access to the storage management tools.
This is must read series for VMware admins who maintain and manage their own storage, and for storage admins who want to offload the burden of provisioning new storage to their VMware guys.
If you follow my RTFM blog frequently you will know I've been playing around with the new vStorage plug-ins for VMware vCenter for sometime. This week I was very fortunate to be granted access to NetApp's latest and greatest version of the Rapid Clone Utility (RCU) 3.0. It's currently in beta but will move into general availability (GA) very soon, and I'm very lucky to be able to give you a sneak preview. Of course, you do need to be a NetApp customer for the plug-in to work, but the beauty of the RCU is that it's totally free. And in my book, free is always good!
The RCU is a neat little tool, albeit quite poorly named. It doesn't just clone virtual machines. It will help you with your day-to-day administrations. And if you're more of a NetApp administrator than a VMware admin, it's a way of giving your VMware people the ability to manage their
Installation and post-configuration
The NetApp RCU and VSC are both installed on your vCenter server and run as services on VMware's management platform.
There's no client as such to install, which I like. The user interface of the RCU is served up as a series of webpages embedded into vCenter. Normally, I'm a bit sceptical about this; after all, presenting a webpage in vCenter is no great shake, as the HP Insight Manager plug-in demonstrates. The difference with the RCU is that you get the feel of a real application inside vCenter.
Installing RCU and VSC is a next-next installation routine. During the RCU installation the wizard asks you for the authentication details of the vCenter, so that the RCU can interact with vCenter from a plug-ins/extensions perspective.
The VSC installer opens a webpage where you input the same information. It's not clear why the plug-ins have different front-ends. I suspect different teams within NetApp wrote them.
It is possible to install the vStorage plug-ins on separate management servers if you wish, but I've found the RCU/VSC to be quite lightl and installing both of them on the same server didn't appear to affect the performance of the core vCenter services.
After installing the two components its time to crank up the vSphere client. There will be two security prompts (if you have installed both the RCU and the VSC) to confirm you trust the clients connectivity to these new services. In the Plug-in Manager dialog box you should see two new extensions -- the Virtual Storage Console and "Kamino".
Kamino is the internal project name for the RCU. I guess at some stage NetApp will change this to something like "Rapid Clone Utility". (Incidentally, for the uninitiated, Kamino is a planet that appears in Attack of the Clones. According to Wikipedia they are a "race of tall, elegant, long-necked creatures…who keep to themselves and are known for their cloning technology.")
The VSC requires no post-configuration tasks for an admin to use it, but the RCU does require some. For RCU to work you are going to have to tell the RCU what the name/IP address of your filer is and how to authenticate it. To do this you need to crank up the RCU admin page.
In the vSphere Client, navigate to Home \ Solutions and Applications Tab \ Rapid Clone Utility icon, and click the Storage Controllers tab. The Add… link over on the far right will allow you to kick things off. Start by typing either the name or IP address of the management interface of the filer, together with the username and password. In this case I'm being a very naughty boy by using root/password. You might want to create an aggregate(s) just for VMware, and then use permissions in the NetApp filer to restrict VMware folks just to their aggregate(s), effectively making a little sandpit where they can do stuff without fear of them affecting other subscribers to the storage array.
At this stage the RCU interrogates the filer and reports on all network interfaces, existing volumes and aggregates. By default the RCU also adds in aggr0.
I like to remove this from the list, as aggr0 is normally where the system that make the filer run is stored (called Data OnTap), and its not a good idea to create volumes there, even if there is free space. Use the arrows to add and remove interfaces, volumes and aggregates out of the configuration to restrict what the RCU can see and do.
Mike Laverick (VCP) has been involved with the VMware community since 2003. Laverick is a VMware forum moderator and member of the London VMware User Group Steering Committee. Laverick is the owner and author of the virtualization website and blog RTFM Education, where he publishes free guides and utilities aimed at VMware ESX/VirtualCenter users, and has recently joined SearchVMware.com as an Editor at Large. In 2009, Laverick received the VMware vExpert award and helped found the Irish and Scottish VMware user groups. Laverick has had books published on VMware Virtual Infrastructure 3, VMware vSphere4 and VMware Site Recovery Manager.
This was first published in February 2010