Sunday, July 3, 2022

Adventures of a Small Time OpenStack Sysadmin Chapter 006 - Shut down vSAN

Adventures of a Small Time OpenStack Sysadmin relate the experience of converting a small VMware cluster into two small OpenStack clusters, and the adventures and friends I made along the way.

Adventures of a Small Time OpenStack Sysadmin Chapter 006 - Shut down vSAN

The reasoning behind the vSAN shutdown being you can’t have vSAN cluster failures while shutting down individual ESXi hosts if you’re not using vSAN anymore.

Historically performance over NFS was not as good because my NFS server was provisioned for capacity not speed (so HDDs and 1G ethernets, instead of all SDDs and 10G ethernet).  NFS performance is/was temporarily usable, in the past I successfully moved entire workload to NFS or shut it down during appliance firmware upgrades and appliance hardware upgrades.

If I had to do it all over again I would not have spent time completely wiping vSAN after all workloads were removed.  I did not want false alarms popping as ESXi hosts shut down so it seemed a wise investment at the time.

The main problem I ran into and had to Google for was vCenter will not let you shut down a vSAN, and WILL NOT TELL YOU WHY, if the cluster has High Availability HA running.  If you shut off HA then vCenter will let you shut off vSAN.

The secondary problem I ran into was I wanted to wipe the vSAN partitions just to make sure nothing weird tried to resurrect itself after a reboot, for whatever reason.  vCenter does not make it easy to wipe partitions but it is eventually possible with some Google search work.  This was probably a waste of time, in retrospect.

After shutting down at the cluster level and host level and partition level, I also removed my vSAN VLAN from the ethernet network, removed DNS entries for the former, now deleted, dedicated VMK interfaces, removed allocations for the VLAN and the ip addresses and space and device interfaces from Netbox.  "Paperwork" took longer than the technical work as is usually the case.

Enough deleting and removing; time to start designing and adding.

Stay tuned for the next chapter!

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.