Posts tagged Virtualization
ipHouse releases VMware based server services
Apr 24th
Virtualization, one of the buzzwords flying around the Internet today, is a method of running separate servers (guests) with separate operating systems on shared physical hardware (the host). I wrote a quick summary back in February, 2009 that should help give some context.
Here at ipHouse, we have chosen to use VMware for our virtualization products. We chose VMware because of its reliability, great support for many guest operating systems, and integrated set of management tools for both the hosts (the physical servers) and the guests (the running virtual machines). In fact, ipHouse is an official licensee of the VMware Service Provider Program (VSPP), a requirement to sell virtual server services to 3rd parties (and as far as I know, the only authorized hosting provider in Minnesota, though I would love to be corrected).
Dubbed ‘SV’ internally, there are 4 different server editions available.
But before I get into the servers (and their configurations) themselves, I’d like to list the supported operating systems (and Linux distributions), many of which are ready for quick deployment where only the final configuration options need to be entered.
Immediately we support:
- Microsoft Windows Server 2003, Standard and Enterprise, 32/64bit
- Microsoft Windows Server 2008, Standard and Enterprise, 32/64bit
- FreeBSD 7.x, 32/64bit
- Ubuntu 8.04 (Hardy Heron), 32/64bit
- RedHat Enterprise Linux 5, 32/64bit
These systems are available with and without operating system maintenance handled by ipHouse, and if you choose to maintain your own system(s), we have an interface in place to facilitate your needs for a virtual console that will give you the ability to power on, power off, and reset the system, as well as doing recovery in case of a configuration error.
How does this work? Here is a tutorial I whipped up (with editing help from Ben) using the client tools we will supply.
(and it was fun to make, but really needs a voice over)
Virtualization War II (VWII)
Apr 4th
Oooh, the virtualization wars are reaching a new level, and with this new video from Microsoft we have reached a new level of marketing misdirection with some future capabilities included.
The video focuses on 10 items that VMware says they have over Hyper-V…that are being refuted by the marketing and tech guy in the video.
Right away the viewer is presented with the first (of many) misdirection(s). There is a claim that Hyper-V supports live migration (compared to VMware vMotion), but you need to listen closely, it is in Windows Server 2008 R2, which hasn’t been released yet. They even say that, but it is quite subtle and could easily be missed. To do this kind of feature, a clustered filesystem is needed, which they talk about in the video…but it also is not released yet. This is just marketing for future enhancements, it isn’t a fact fighting battle, it is more of a tweedle beetle battle.
Two items are are ‘announced’ within the first 90 seconds. Ignore the techno error of Windows presenting the same LUN – Windows isn’t doing this, the SAN is doing so.
There is more, but I don’t want to ruin your viewing pleasure. So check it out, giggle where you need to, learn something new where you can.
One item in Microsoft’s favor is hardware support – only requirement is Hyper-V requires Intel-VT or AMD-V, otherwise, whatever Windows Server 2008 supports works out of the box. No issues on whether you can use straight SATA disks or this random RAID controller from the corner computer store. If it has a Windows driver…you can virtualize.
Virtualization and you – the business user
Feb 16th
Why virtualize? Better yet, why use virtualized server services for your business?
I’ll try to answer that question in this blog post, though from a service provider point of view, but I’ll try to remove my bias where feasible.
Summary: For many business needs, a virtualized server on a hosting providers infrastucture is very cost effective, very secure, and highly reliable. When those 3 items are combined, the argument to use separate, physical servers becomes moot. Virtualized server services are not for everyone, nor for ever task at hand, but for many, it is the more right solution.
Now that the summary is done, you can can read on for details as to why I think the above statements are true or just head on over to ipHouse and talk to sales and see what we can do for you, or both.
First, virtualization has a few meanings, but for this context, I am talking about the concept of taking a physical server (call it a host) and carving it into many virtual systems (call them guests) running concurrently. Here’s a picture from using VMware atoms to help visualize what I am getting at:
VM -> Host visualization
This allows the ability to spread the cost of a fast and expensive physical server amongst multiple guest systems.
Virtualization and you – general questions
Feb 16th
In my own opinion and some googling around, I have found that there are some basic questions that you should ask yourself when you are looking at using virtual server (machine) services.
I’ll update this list as I come up with new information or receive feedback valuable to most people.
The questions are in no particular order after question #1.
Questions #2 and #3 are exclusive of each other as mixing them can be problematic.
Prepping for VMware virtualization for customers
Feb 13th
I chose Dell as my hardware platform, VMware for my host hypervisor, and I am starting with a 2 system ‘cluster’. (I use the word ‘cluster’ not because they are clustered in a way that most people think of things, but in that they will share SAN LUNs for their storage allowing migration from one server to another.)
Last week was like having a birthday – I received two systems from Dell for our virtualization initiative that we’ll be launching in the near future. Very exciting.
Measured power utilization of the new servers is quite reasonable at 4.6A maximum current draw using 14 of the 16 cores running at 100%.
I did this by running SETI@Home over approximately 36 hours using 3 4 vCPU systems and 1 2 vCPU system.
