Here is something that I get asked periodically – what’s with the goofy blog and twitter handle of “Captain KVM” Continue reading “Why the name, “Captain KVM”?”
In my last post, I described “the how” NetApp got involved with oVirt, but I really didn’t get into “the why”, except for leaving off with “integration”. And that is exactly where this post picks up. Continue reading “Why is NetApp involved in oVirt?”
Last week, I was in San Diego for the oVirt Workshop and LinuxCon, where I presented on “Integrating oVirt with Enterprise Storage”. I’d like to go over some of the major points that I covered in my discussion, but I’d also like to explain why NetApp is involved in oVirt in the first place. In order to keep the posts brief, I’ve broken things up and I’m starting with how NetApp got involved with oVirt in the first place. Here goes… Continue reading “How did NetApp get involved with oVirt?”
Several months ago I highlighted the use case for mixing thick and thin hypervisors in the context of Red Hat Enterprise Virtualization. Today, I’d like to build on that to provide more detail on using an agent on the thick hypervisor (RHEL 6 and KVM) to streamline the process of backing up data volumes. And as the title suggests, we’re offloading that backup requirement away from the hypervisor. Why?
Because we can (and should). Continue reading “Using Snap Creator to Offload Backups in RHEV & KVM”
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. Continue reading “Offload VM Cloning from KVM to the Back-end Storage, pt2”
Disclaimer – This is actually a re-post of a colleague’s Google+ post. I did not author this, nor am I claiming credit for this. Andrew Cathrow originally posted this on April 8. I just thought enough of it to repost it here. Additionally, while my preference/bias is clearly slanted towards KVM, VMware does have a solid product. They’re just not up front about their dependencies…
VMware has a lot of rather deceptive marketing around KVM and Linux. They have gone to great pains to hide their complete reliance on open source and Linux in particular. You may be saying to yourself “that was in the past but today with ESXi there is no more Linux because they removed the service console”.
You’d be wrong, actually you’d be really, really wrong. Continue reading “Vmware Dependency on Linux”
I’m happy to report that my updated technical reports around RHEL 6, KVM, and NetApp storage have been published. Whether you are looking for the best practices, how to deploy the best practices, or simply need something to get you to sleep (‘cuz the Ambien isn’t cutting it), these are for you!
Thanks again for following!
If you’ve checked out both RHEV 3 as well as running KVM on RHEL 6, you’ve no doubt found pros and cons for going one way or the other with your hypervisors. RHEV-H offers a simple appliance approach that is already tuned and configured. KVM on RHEL 6 allows for customization while still offering the benefits of the high-speed KVM hypervisor. Which one should you use?
A few weeks ago, I addressed the concept of using the back-end storage to clone RHEL boot LUNs as opposed to repeated Kickstarts. The reasoning is simple enough – cloning on the backend is significantly faster that creating from scratch. Work smarter, not harder.. Right?
So what happens when we apply the same logic to individual virtual machines? In a word?