Upgrade from AL8.10

[anandmys]

I am running CWP on AL8.10

Should I upgrade to AL9?

What are the steps and precautions to be taken if I need to upgrade?

[overseer]

I too am running AL 8.10. My plan is to directly upgrade to AL 10 as soon as CWP support is a bit more mature, skipping AL 9 altogether.

[Wonder]

I too am running AL 8.10. My plan is to directly upgrade to AL 10 as soon as CWP support is a bit more mature, skipping AL 9 altogether.

The other day I did that migration, from AL 8.10 to AL10, and it went perfectly, 100% right.
For some reason, it was a test before doing the final migration. Now, with the new version of CWP, the option to migrate from CWP to CWP isn't working...

[stkontra]

I'm also wondering if it's possible to elevate from alma 8 to alma 10 without any compatibility issues in cwp pro?

[Wonder]

I'm also wondering if it's possible to elevate from alma 8 to alma 10 without any compatibility issues in cwp pro?

I can confirm, yesterday I migrated from AL 8.10 to AL10, without any problems, everything was perfect, fantastic, great job CWP.

[Wonder]

I'm also wondering if it's possible to elevate from alma 8 to alma 10 without any compatibility issues in cwp pro?

Just to add some more details to my previous post (now I can't edit my previous post):

My migration was performed from a server running AlmaLinux 8.10 with CWP Pro to a fresh installation of AlmaLinux 10 with CWP, using the built-in CWP-to-CWP migration tool. It was not an in-place OS upgrade.

The migration was successful, and I was particularly impressed by how much of the configuration was transferred automatically.

A few things I verified:

- DNS zones: The DNS zone was migrated automatically, including the existing records. CWP also replaced the old server's IPv4 addresses with the new server's IPv4, including the SPF record.
- IPv6: The original IPv6 addresses were preserved, so I updated them manually to match the new server.
- DKIM: The main domain's DKIM configuration and private key were migrated successfully. I verified that the private key was byte-for-byte identical on both servers using SHA256.
- DNS validation: After updating the IPv6 records and the SOA serial, the migrated zone passed `named-checkzone` validation and loaded successfully in BIND.

Overall, I'm very pleased with the improvements to the migration tool. The automatic DNS zone migration and IPv4 replacement were particularly nice surprises!

Of course, I'm still performing post-migration checks, so I wouldn't claim that every possible configuration has been fully verified yet.

Great work, CWP team!