What David said ^^^ above.
IMO, don't even bother without having a LAB first - you are making HUGE
jumps with both hypervisor and ACS version, and that needs to be tested
"the hell out of it" to put it that way - 4.11 sounds like a feasible
mid-version. XCP-ng needs to be 7.4 or 7.6 at most (pleas
I suspect the answer is a qualified "maybe/yes"? A couple (humble) thoughts as
it sounds like you've got the two upgrades in mind:
- focus first on the upgrade path to the latest ACS 4.*.* that still supports
XS 6.2.0
- determine the upgrade path from XS 6.2.0 to XCP 8.2 (not sure - just
some
Hello David,
We have an ACS 4.3 install with somes XS 6.2.0 clusters.
Would you think we could perform an upgrade from these XS 6.2.0 to ACS 4.11
with the same way ?
The finality would be to move our ACS 4.3 to ACS 4.15 in order to convert
in fine our XS 6.2 to XCP 8.2
@Andrija, would you think
Reporting in on this - turns out was fairly painless (I never ended up goofing
around with host tags at all).
Here's an updated to-do list (with some observations):
1. In XenCenter – if HA is enabled for the XenServer pool, disable it
2. Stop ACS management/usage services
3. Do MySQ
Andrija,
I appreciate you sharing your thoughts on this. I'm getting my ducks in a row
on the XenServer side (for the upgrade) & I'll give the plan a go.
I'll report in afterwards, wish me luck!
Thanks,
David
David Merrill
Senior Systems Engineer,
Managed and Private/Hybrid Cloud Services
OTEL
Hi David,
with a bit of delay...
those steps need to be tested - I would skip the whole
"environment.properties" file and see how it behaves today - the reason
being that, though the article on shapeblue.com was old, it does mention
both "Unmanage" cluster and Maintenace mode - so I'm not quite
