The Red Hat Summit 2012 kicked off with an evening keynote by Jim Whitehurst explaining the changes in business value over time from the raw materials to the industry that profited from standardization. He made some excellent points and summaries about what cloud is and isn’t. The root of his keynote was around what cloud can do for companies and not so much about what cloud really is. His key point was that the value didn’t reside in the nuts and bolts that hold a cloud together.
My work at Rackspace has changed a bit in the last few weeks and I’ve shifted from managing a team of engineers to a full technical focus on OpenStack Nova. Although it was difficult to leave my management position, I’m happy to get back to my roots and dig into the technical stuff again. One of the first things I wanted to tackle was understanding how a build request flows through Nova to a XenServer hypervisor.
Quite a few people who couldn’t make it to Xen Summit 2011 this year asked me to write a post summarizing my takeaways from the event. I’m not generally one to back down from peer pressure, so read on if you’re interested about the discussions at this year’s Summit. The feeling I had at last year’s summit is that Xen was on the verge of losing traction in the market. Very few distributions still had Xen support going forward and much of the discussion was around the lack of dom0 support in upstream Linux kernels.
If you haven’t noticed already, full Xen dom0 support was added in the Linux 3.0 kernel. This means there’s no longer a need to drag patches forward from old kernels and work from special branches and git repositories when building a kernel for dom0. Something else you might not have noticed is that the Fedora kernel team has quietly slipped Linux 3.0 into Fedora 15’s update channels in disguise. Click that link, scroll down, and you’ll see “Rebase to 3.
Diagram: OpenVPN to Rackspace Cloud Servers and Slicehost A recent blog post from Mixpanel inspired me to write a quick how-to for Fedora users on using OpenVPN to talk to instances privately in the Rackspace Cloud. The diagram at the right gives an idea of what this guide will allow you to accomplish. Consider a situation where you want to talk to the MySQL installation on db1 directly without requiring extra ssh tunnels or MySQL over SSL via the public network.