Red Hat released Red Hat Enterprise Virtualization for Servers on November 3rd. A couple of weeks before the release, I emailed Red Hat media relations contact Kerrin Catallozzi and asked for an interview with some Red Hat employees regarding Red Hat Enteprise Virtualization.
It took a several weeks to get the answers back mainly because the official product release happened... and after I had the chance to download, print and read the documentation, most of my questions had been answered... and I ended up coming up with all new questions. Kerrin found Andy Cathrow (Product Marketing Manager) and Jim Brennan (Senior Product Marketing Manager) of Red Hat to provide the answers. Andy Cathrow will be referred to as "AC" and Jim Brennan will be referred to as "JB".
Jim Brennan serves as Senior Product Marketing Manager for Desktop Virtualization at Red Hat. He is responsible for the market strategy and positioning of Red Hat Enterprise Virtualization for Desktops. Jim has over 12 years of experience in the development, management, and marketing of technology products.
Prior to joining Red Hat, Jim spent eight years with Internet Security Systems (now part of IBM), where he held positions in research and development, product management, and product marketing for various information security products and technologies.
Andy Cathrow serves as Product Marketing Manager at Red Hat and is responsible for Red Hat's virtualization products. Andrew has also managed Red Hat's sales engineers.
Prior to joining Red Hat in 2006, Andy worked in product management for a configuration company, and also for a software company that developed middleware and messaging mainframe and midrange systems. Earlier in his career, Andrew held various positions at IBM Global Services.
[Update: - Dec. 9, 2009 - I got a chance to chat with Andy and Jim in real-time and ask several additional questions at the Red Hat Virtual Experience 2009 online conference. See the comment below the main interview for a transcript.]
I wrote a comment to an LWN news blurb referring to a story about the future of Linux was in Google Chrome OS. The post was so long that I decided to cross post it here. :)
- - - - -
I assume you (the person on LWN who wrote the comment I was replying to) were being sarcastic when you said that 10-20 million Linux desktops don't count. I'd argue that the numbers are actually larger than that (probably by as much as 2x) but let's stick with a medium number of 15 million... for my discussion below.
Some people want commercial software on Linux, some don't. I attended the Utah Open Source Conference 2009 in Oct. and attended a presentation by a big wig from Adobe where he talked about FLOSS and Adobe. Of course the usual question came up about when will we get Photoshop and various other Adobe products for Linux and the answer was something like, "when there are enough Linux users to guarantee sales of at least 50 million copies". That is a rather high hurdle. Seriously, you have to sell 50 million copies of something before it becomes profitable? What a poorly run company you must have.
Shorewall and Proxmox VE Cluster Configuration
This is a follow up article describing how to use Proxmox VE and Shorewall together. This article focus on using Shorewall within your Proxmox cluster. If you have not read the first article I recommend that you do so, it will aid your understanding with what is going in this one.
Network Layout and Shorewall Configuration
We are going to be using a bridging configuration. This is what Proxmox VE uses with by default. Bridging allows for easy migration of hosts without having to re-configure the firewall each time a machine is migrated.
I haven't seen it mentioned on Slashdot or LWN yet... and I even emailed LWN informing them... but Red Hat released Red Hat Enterprise Virtualization for Servers and the accompanying Red Hat Enterprise Virtualization Hypervisor products today. There are a slew of press releases and demo videos. They even had a webcast press conference. Oh, and hey, they also released all of the manuals too.
Didn't we see this coming?
Those who have been paying attention were expecting these releases... but I must admit that once I learned the details, I was shocked. Why? Because the Management side of the product requires Microsoft Windows products. What products? Windows Server 2003 is needed to run the management server. What services is the Windows Server running? IIS, Microsoft SQL Server, and it'll need to be connected to a Microsoft Active Directory Server for authentication and management.
Then of course once you have the proper Windows environment established you can actually install the RHELfS management app provided by Red Hat. Oh, if you don't have your own Microsoft SQL Server setup already, they can install the Express edition for you.
The Management server software includes a local management client app you can run on the management server but it also has a web-based version of the management app for remote management. Yeah, at last open standards! Not so fast. What browsers are supported by the web-based management app? Microsoft Internet Explorer 6 and up. Other browsers (according to the docs) are "untested". What? They haven't even tested them? What, you aren't curious if Firefox works? To clarify it appears as if the web-based management app sends Active-X based content to the web client... and that .Net technology is also used.
Ok, after reading those last few paragraphs, I'm guessing you are shocked too.
Proxmox VE does not come with a firewall by default there are several solutions to this problem but the most flexible and robust is integrating the Shorewall firewall. This document assumes a basic knowledge of the Shorewall program and will not cover all of Shorewall capabilities but will give you a good working model to get you started. For more advanced topics check out the Shorewall documentation.
Shorewall will have 3 zones: 1) the fw zone which is the Proxmox host, 2) the net zone which is the Internet and 3) the dmz zone which is where the virtual machines will reside. The hardware just has one network interface card; vmbr0 is a just a bridge interface.
This was my first year attending the Utah Open Source Conference. I was lucky enough to have Warren Sanders and Andrew Niemantsverdriet (both from the BillingsLUG) go with me and help staff the OpenVZ booth. I'm very thankful to Warren for providing transportation and doing all of the driving.
The weather cooperated and the 413 miles from Belgrade to Salt Lake City went quite smoothly. Warren and Andrew had an additional 150 miles from Billings to Belgrade. We left Belgrade about 11AM and arrived at the hotel in Sandy, Utah about 6PM.
We stayed at the official hotel for the conference which was the Residence Inn and the official special event price was $89 a night. I must say the accommodations were excellent with a full kitchen, king size bed, and pull out couch. All three of us stayed in the same room so Warren and Andrew had to put up with my snoring and funny smells.
Here is the video of my presentation from the Utah Open Source Conference 2009 entitled, "Introduction to OS Virtualization, Containers and OpenVZ". Warren Sanders manned the camera. I used Kdenlive to edit it and create the title screen. Attached below you can find PDFs for my slides, the OpenVZ Brochure we were handing out, as well as white paper from the Linux Foundation about who writes the Linux kernel.
For those interested in a much higher quality Ogg Theora version, you can find that here:
(right-click, save link as...)
Wow, I really wasn't watching the calendar. Someone just dropped by my office asking if there was a meeting tonight. I said no because it is always the last Thursday of the month. What? Today is the last Thursday of the month? Yikes. I don't have anything planned.
I sent an email to the BozemanLUG mailing list with the info... suggesting that the meeting be cancelled unless someone wants to email me or give me a call at work saying they want to have a meeting without a topic.
994-3931 work, firstname.lastname@example.org
Too bad no one spoke up earlier asking.
I've been aware of Proxmox VE for a couple of years now. I've installed it a few times and tested it out. I have recommended it to others and know a few local people using it in production (at MSU-Bozeman and Rocky Mountain College for example). Since I'm involved in the OpenVZ community I've also noticed some of the contributions to OpenVZ that have come from Proxmox VE (vzdump for example) and have run into Martin Maurer in the comments section of this site. I asked him if he would be interested in doing an interview and he accepted.
What is Proxmox VE?
Proxmox VE is a very light-weight Debian-based distribution that includes a kernel with support for both KVM and OpenVZ. This means you get the best of both virtualization worlds... containers (OS Virtualization) and fully-virtualized machines (Machine Virtualization). Proxmox VE also includes a very powerful yet easy to use web-based management system with clustering features. Boot the Proxmox VE install media, answer a few simple questions, and within 10 minutes you have a very powerful virtualization platform you can manage from a web browser. Install it on one or more additional machines that are networked together and use Proxmox VE's cluster management tool to create a virtualization cluster that allows for centralized management, automated backups, iso media and template syncing, as well as virtual machine migration features. Proxmox VE really is a time saving turnkey solution... and it is freely available under a GPL license.
The family and I are visiting the in-laws in Great Falls over the holiday weekend. My family picked me up from work so I wasn't involved in the packing... and it just so happens that my wife didn't pack my laptop. :( As luck would have it, my father-in-law has two recently purchased laptops... and he also had a Dell Mini 9 he was working on for a friend... and he was kind enough to let me play with them.
MontanaLinux from LiveUSB thumbdrive
I usually have one or more USB thumbdrives in my pants pocket and almost always one of them is a bootable LiveUSB of a recent built of MontanaLinux i386 (my own remix of Fedora 11)... so at least I had something I could test with and get my Linux fix. The build I used was dated August 26th, 2009 so it had all of the Fedora updates released on or prior to that date.
Now onto the three laptops I tried out.