Several months ago, I posted an article on how and why to offload cloning from KVM to the back-end storage. I’d like to take the opportunity to update this ever so slightly with a recorded demonstration. In the original posting, I was using Data ONTAP 7.3.x – this recorded demo utilizes Data ONTAP 8.1 Cluster-Mode.
So why update now with a demo? Simple. I can type all day, but sometimes watching the magic happen is much more effective than reading about it.
NetApp FlexClone & KVM
(give it a moment to start after you hit play)
[FMP width=”720″ height=”405″]http://captainkvm.com/wp-content/uploads/2012/06/KVM_Clone_offload.mp4[/FMP]
So why is this important? Well, if you have the need to scale quickly and on-demand, this is a really big deal. Allowing the hypervisor to perform the cloning is faster than manually spinning up a VM to be sure, but what about 5 VM’s? All of that cloning takes CPU and Memory resources away from it’s core job – servicing applications.
Let’s look at this a different way. If you have a Tier 1 database running on a server, would also use that server for streaming content and/or compiling code? No, you would leave it to run it’s core function, servicing the database. Virtual machines are a hypervisor’s application. Plain and simple.
Additionally, 2 minutes to clone 1 virtual machine at the hypervisor level vs. a few seconds at the storage level is years apart if you need to scale on demand to support your business. And to that end, the RHEL, KVM, and NetApp API’s all make incorporating these features a snap.
So this all great for a single clone, but what if I want to spin up 20 VMs this quickly? Great question. Come find me in the NetApp booth at Red Hat Summit in 2 weeks and I’ll show you.
Hope this helps,