I'm trying to follow the design, but I may actually do just that.
We already have vSAN clusters in single image mode, but now applying it to standalone servers essentially triples the wasted time managing 470+ individual images instead of the 3 different platforms...
Original Message:
Sent: Jun 13, 2025 10:03 AM
From: Alexandru Capras
Subject: I didn't think Lifecycle Manager Single Images could get worse - I was wrong again! (another rant)
Not really a rant if you see it as a chance to throw a solid idea at the VMware devs, but yeah, I get the struggle.
I know that you can still use baselines in vSphere 8 regardless - is this not an option for you anymore?
Original Message:
Sent: Jun 13, 2025 12:07 AM
From: Carl Power
Subject: I didn't think Lifecycle Manager Single Images could get worse - I was wrong again! (another rant)
After upgrading to vSphere 8, it dawned on me what was before me - single images for standalone servers, my new nightmare.
Now you may see this as not a big problem, but heres my current environment:
- 160+ standalone physical servers (all are ML30 Gen10)
- 150+ secondary servers for vSAN witnesses
- 160+ vSAN clusters (2 hosts + witness, all are DL360 Gen10)
Where baselines were able to be implemented at the root folder and apply to all child items, I now have 470+ unique single images to manage in my environment, and each needs to be independently updated every time I want to update my environment...
Please VMware Gods, allow me to link single images to a master image!!!