Virtualization, Cloud, Infrastructure and all that stuff in-between

Interesting Blog to keep an eye on here http://shippingseven.blogspot.com/ allegedly from an engineer working on the new Windows OS, be good to see what comes out – MS haven’t said very much at all about it.

Mmmm, interesting.

They’re aiming for virtualizing much more than just the OS.. VMWare obviously realise the Hypervizor game is coming to an end where ESX will be a free/commodity release and all the add-ons/management will make the money.

This makes an interesting foray into application level virtualization – more anlysis here.

Another other interesting but unrelated point here is about how RSS feeds break news far quicker than Google can index it!

I’ve not tried this before but it seems to work, my config is as follows – note this is a home/test system so I don’t suppose this is supported for a production platform

• Single ESX 3.5 host
• 1 x Windows 2003 VM with Virtual Center 2.5, licence manager, update manager and convertor plug ins, SQL Express database for VC (not supported for production)
• VM is connected to the same IP network as the ESX service console.

Because I was short on hardware I built the 1st Virtual Centre server as a VM on my laptop with VM Workstation 6 as a linked clone from my standard VM server image.

Once everything is up and running I used VM Convertor from Virtual Centre to do a P2V migration of itself over the network (weird!) into ESX – technically a V2V 😉

I then powered up the VC VM on the ESX box and changed it’s IP address to avoid conflicts.

Then shut down and killed the VC VM on my workstation.

It worked – I can connect to the virtual VC box and use it as before.

I also installed the VI client directly on my laptop so I could manage the virtual VC box over the network without RDP’ing into it.

I set the VC VM to auto-start with the ESX host and physically rebooted the ESX box to make sure – and it all rebooted fine and both the ESX and VC VM started up, I believe the ESX host caches licence data in case of a short-term VC server failure – this seems to get around the issue of not being able to power on a VM without a licence and seems to work ok for me.

Whilst I’m having a rant, the licence manager for VMWare has to have the worst documentation and weirdest UI ever – VMWare have licenced it from Macrovision and it’s a multi-vendor app but I’ve yet to encounter anyone who has managed to follow the documentation 1st time to install a centralised licence server for a VMWare farm and I always forget how to do it…

So, here it is in simple terms for reference.

Install the licence server on a Windows box somewhere (VC node or elsewhere)

Ignore the LMTools app for now.

get your VMWare licence key file.

When you purchased ESX you would get a licence activation key (LAC) in an email – it looks something like the following

ABC-12ABC-ABC1A-ABC0A-1AB1A

You need to go to the Vmware site, logon with your account that is tied to the licence key request

Plug in the LAC

then go and activate your licences, if you’ve purchased a bunch of licences this will involve selecting how many instances of CPU licences you want to bundle into the licence key file – you can add more later.

download the file it generates

Rename it VMWARE.LIC (don’t think this is 100% required, but works for me)

Stop the “VMWare Licence Server” service

on your licence server navigate to C:\Program Files\VMware\VMware License Server\Licenses

overwrite the default vmware.lic file with the file you downloaded

Start the “VMWare Licence Server” service

Run VMWare Licence Server Tools from your start menu

and then go to the server status tab and click “Perform Status Enquiry”

You should see something like the following

Hint – you can look in the .lic file yourself to check it’s contents- it’s just plain text and I think you can put multiple .lic files in this directory.

There is a default licence file in the licenses directory – this is a dummy one and it says so in the text.

The LMTools GUI is a bit weird, if you run this first and select “Configuration using License File” from the default tab (which would be the logical thing) then it doesn’t seem to do this file copy and you keeps using the dummy vmware.lic file which is really confusing as nothing works and when you try to point ESX nodes at it via VC they all fall back to unlicenced.

Also, the ESX server itself seems to cache the licence data a reboot seems to flush it out and it becomes properly licenced.

ok, it’s free so I can’t complain too much (well, I can as I would have had to pay for the ESX licence to use it in this way!).

I want to import a bunch of my VM Workstation VM’s into an ESX server; why can’t I multi-select, or even browse for these VM files to import – I have to do them one by one cut & pasting the UNC path from Windows explorer.

Come on – that’s not good UI design is it – how difficult would it be to have a “browse” button on there!

Rant over..!

As eric and some people here and here very helpfully pointed out last week the HP Compaq D530 desktop PC has hardware that is compatible with ESX 3.5’s new SATA drivers.

I managed to get a 2.8GHz HT one from eBay with 4Gb RAM and a 500Gb SATA disk for approx £315 GBP delivered, including VAT.

And I’m pleased to report ESX installed 1st time straight from the CD, no fiddling required, this is very handy as until about 6 months ago I had a Compaq ML570 G1 (4x 700 MHz Xeon CPU and 12Gb RAM plus external disk shelf) which was fine until my electricity supplier caught up with the fact they had been seriously under-billing me for my electricity consumption, so the rather large bill for running it for a year led to it’s powering down for a majority of the time.

I’m in the process of migrating all my home VM’s from VMWare Server (I used to run Windows as the actual host OS) to ESX 3.5.. don’t have a “proper” licence yet, but I will do at some point before the eval times out, with the power saving it will more than pay for itself!

Whilst this is lowly desktop PC hardware it uses about 1/8th of the power of the ML570 and performance is probably on-par.. although slower disks (I previously had 14 x 18Gb U3 SCSI for my VM volumes)

Will post more results when I’ve finished, seriously considering picking up another one and enabling vMotion; I’ve used OpenFiler in the past to get a reasonable iSCSI “SAN” up and running – although I suspect my very old Cisco 10/100 hub is going to need replacing next!

Why? you might ask – well, because I can and my Garage has rack-space 😉 I’ve always had a decent sized home network, maybe I’ll blog about what I run at home later and it’s always handy to “eat your own dogfood”  – I work with this stuff, so it’s useful to use it myself and have something I can rip apart/trash as required without having to buy expensive hardware or fill out lots of change-control forms!

I like this idea of this. it sounds like a product for automating a lot of what I blogged about in my Build a better test lab series (much delayed in publishing… must find some time to post further!).

We had a lot of trouble with the out of the box p2v tools; would be great if they could deliver this, I’ve asked to join the beta via our partner manager – fingers crossed!

Interesting ideal posted here about a company build floating datacentres on old container ships. plenty of water for cooling and bio Diesel for power and land docked for power/connectivity.

Combined with a fluid infrastructure (no pun intended!) based virtualized systems  as proposed on blade watch, and you have a portable datacentre. in the event of disaster VMotion all your VMs to another ship and move, when you get there bring them back.

Also a further advantage would be with a global energy market in flux, it does give you the option to move your Data centre to an entirely different country which may have cheaper power rather than an investment in bricks and mortar which is hard-tied to the local power grid.

if you could get good ship to shore comms with high bandwidth you could maybe do away with the land tether for reasonable periods of time to keep running whilst you relocate, or even keep it outside a nations waters for legal reasons – like they tried at Sealand (and) in the English Channel, wow a real container load of pr0n 🙂

Not without practical problems, but Interesting

Speculation here.

This would be a great feature – I’ve been playing with Fusion on a Mac Book Pro recently – I would love this, it’s a great feature!

Proper support for ESX under VMWare would be great for those of us that have to do demo/dev work – even if it’s not supported for production along the same lines as the way MS provided initial support for SQL 2005 DB mirroring when it first came out.

Sorry for lack of posts – technically on Christmas holiday until the new year – but plenty on!

Very handy – quick visual reference to the various Exchange 2007 roles downloadable here

As the Exchange team blog mentions a printed copy is coming in TechNet magazine if you subscribe – as it’s got a lot of detail on it and needs to be printed big to be readable.