Skip to main content

Upgrading VMware ESXi Lab

Let's start with the definition of a VMWare lab. It's a non production scale system that has enough hardware and software to perform the function under test. In my case that's a couple of different Intel NUC devices with 500GB to 1TB of SSD, 32GB DDR3 or DDR4 RAM and an i5 or i7 CPU. I also have run everything under ESXi as the host OS.
The decision to use ESXi was a tough one. VMWare offers a free version however there are limits to it's capability like access to APIs which permits docker-machine to spawn client instances. I could have installed CoreOS and run everything in Docker containers but that has it's limits too.
Things get even more sketchy because the CLI version of the updater has a number of limits. For example if the /tmp folder partition is not big enough the update process will complain about insufficient disk space... and worse yet the only documented work around does not work.

Here's how I managed my latest upgrade:

[1] log into vmware and get the latest patch file as a .zip

[2] enable SSH services on the target host
[3] suspend or shutdown all of the active clients on the target host
[4] SSH-mount the target host
[5] upload the .zip file from step (1)
[6] ssh into the target host

[7.1] list the contents of the .zip file and determine which patch to apply
esxcli software sources profile list -d /vmfs/volumes/SSD_01/

[7.1] perform the upgrade (get the target path correct)
esxcli software profile update -p ESXi-6.7.0-20190402001-standard -d /vmfs/volumes/SSD_01/

[8] probably require a reboot... as indicated in the result. It's a good idea to connect a monitor so you can see the results. I have one machine that will refuse to boot from time to time.

[9] restart or resume the guests on the target host

Here is a good reference but I would double check the URLs very carefully to make sure i was not running anything that make my systems vulnerable... like downloading the patch from a 3rd party and there are plenty of those.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

Agile is still dead and has been since 1991

[updated 2011.09.30] yet another response to Agile is good.
When you have so much of you career invested in something like Agile, XP etc... it can be hard to see the forest for the trees. I had a consulting job in The Haag many years ago. IBM was the incumbent contractor at the customer site (a bank) but after 5 years on the job they had not written a single line of functioning code. In the office there were two teams of software people... both behind closed doors. The first team was the Data team and the second team was Functional. They rarely spoke and they never shared information. I was there for a week, introduced the client to OO and we had a functioning prototype. Smart people do smart things, You cannot make an underachiever exceptional by using Agile. Either they get "it" or they don't.
I just commented on a blog. I'm sure there is some validity to his post beyond observing that Agile Scrum is broken. It certainly is not what it was originally intended but for…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…