One of the more cooler features of VMWare 5 is that it is capable of running itself. Â While it
may seem silly at first, this is a great way to build a virtual environment where you can test scripts for provisioning (and destroying) stuff, along with testing API level calls without having to worry about screwing up production, begging for a ‘lab’ environment, or even better snapshotting the whole thing so you can revert whatever it is you are doing at a block level. Â In short virtual datacenters really rock, especially for people like me who like to play in a really destructive manner.
So the first thing is that for this test I’m going to use a ‘freebie’ ESXiÂ that I’ve been using for quite some time. Â Naturally this should work for version 6, but since the stuff that I’m testing is all in 5.0 and 5.5 (the majority being 5.5) I wan to build a 5.5 environment. Â In my insane scenario I have deployment access to a 2003 R2 x64 server with .net 2.0, and the majority of the environment I care about is VMWare ESX 5.5 along with vCenter. 5.5 on Windows 2008 servers. Â So trying to mirror this a bit, that means that I’m going to skip the new fangled appliance, I don’t know if it really matters for what I want, but for the sake of trying to keep things the same I’m going to match what I can.
I setup a generic ‘Other 2.6.x Linux (64-bit)’ VM, with a single socket, dual core processor, 4GB of RAM, a LSI SAS controller, with a 32GB disk, and 3 NIC’s with the VMXNET3 driver. Â For some reason I had to change the CPU to explicitly allow for hardware MMU emulation.
It’s also worth mentioning that when you are going to run ESXi on ESXi that any physical adapters that you want your virtual ESXi host to be able to lauch VMs and have them communicate onto you will need to enable the ‘Forged Transmits’ setting in the vSwitch properties.
With that in place, I was able to use my ESXi 5.5 ISO, and install into the VM. Â There isn’t much to really say the installer will install ESXi, and reboot and you get the console.
I went ahead and gave this ESXi server a static address, and that was pretty much it for the server.
I went ahead and used an eval copy of 2008 R2 that is available at Microsoft here. Â The installation is really simple, not much to say but for my needs I gave the VM a static address, HOWEVER I did NOT install Active Directory as you cannot install vCenter onto a DC, and I really was not in the mood to have a DC along with a vCenter 2008 VMs as I’m only interested in doing API testing I don’t care about authentication plugins I’m only concerned with other aspects. Â Obviously if you do care, then you’ll want to install 2 2008 servers. Â I gave my 2008 server a static address of 192.168.1.12 so that I could easily find it on the network post-install.
Since I have no imagination, I renamed the server “vcenter” which of course will factor into the login credentials later on.
My ‘client’ gave me the ISO for vCenter “VMware-VIMSetup-all-5.5.0-3254792-20151201-update03.iso” which of course needs to be installed onto the 2008 server.
I did the easy install, as again I’m not building a real enterprise. Â However I should point out that the easy install has a habit of popping alerts and prompts UNDER the current window so you could be waiting for quite a long long time for this to install when it really shouldn’t take all that long. Â I also kept the option for the 2008 Express edition as I’m not going to try to stress the count of VMs 50 is far more than I require as again I’m only interested in limited stuff at this point.
Again I just selected the defaults for the install as I’m not all that worried. Â Phew with all of that done, it’s now ready to use!
Now I went ahead and hit the following site:
I went ahead and installed the pluggin for a more ‘full’ experience with the web client. Â The link is on the bottom of the page.
With all of that in place, I finally could use the web/flash site to login, using the local administrator account. Â However upon logging in the domain was barren, no vcenters no data centers, nothing.
Obviously I must have screwed something up! Â Even worse using the ‘fat’ C#/J# client (that I still love…) I would simply get this fun error:
What? I don’t have permission?
A little digging around, and I found out of course, that it is because I don’t have an Active Directory, and that for ‘workgroup’ installs like this, you need to simply login as [email protected] or ‘[email protected]’ in my case,Â using the password that had to be set during the SSO installation.
And now I was prompted to create my data-center, and add in the ESXi server into the virtual data-center.
So now I have a virtual vCenter, along with an ESXi host to deploy stuff onto, and destroy all I want. Â Even better VMWare PlayerÂ & VMWare Fusion can also run ESXi nested, so you can take your virtual data-center with you on a laptop! Â You can bootÂ 2008 with vCenter in 2GB of RAM, although it really should have 4GB if not more, and with 4GB for an ESXi server that would be 8GB+ on any laptop or desktop. Â However I’m lucky my ESXi server has 32GB of RAM, and my laptop has 16. Â So it’s also a great excuse to upgrade!
Yeah, that’s a really cool feature we’ve been using for some time in our test/demo datacenters now. The nested ESX can even be newer (to a certain degree, I guess?) so you can test ESX 6.5 before switching your whole datacenter to it.
If you want to test with some more ESX versions feel free to contact me, I have archived versions of almost every ESX and vCenter install ISO going back to the GSX days 😉
You can also add your local “Administrators” group to the SSO config so that you can log in with your usual windows credentials.
And as sad as it is, you should really get used to the web client some more, as with 6.5 the classical client will not be included and won’t work anymore. Yeah, the web client is still kinda slow and clunky but now there’s no way around it (and it *has* gotten a ton better in the last few years… no comparison to the one in 5.5)
> with 6.5 the classical client will not be included
I hope they have a HTML 5 console viewer now, then, because having to install a browser plugin for console viewing, plus another plugin for .ovf deployment is a pain! Oh well, I guess we’ll learn to live with whatever VMware forces us to do.
I guess it leaves space for some enterprising person to use the API and make their own FAT client. Maybe using something to proxy the traffic in a more low traffic effective manner?
then again I don’t have time, I have to talk to old shitty firewalls.