This section describes the process for migrating from Syndeia Cloud (SC) 3.5 SP2 to Syndeia Cloud 3.6. In the remainder of this document, Syndeia 3.5 implies Syndeia 3.5 SP2.
...
Please read the following carefully before proceeding further.
(1) Starting Point: The starting point of the migration process is Syndeia Cloud 3.5 SP2. If you are currently running 3.5 / 3.5 SP1, please first upgrade to 3.5 SP2 then return here. The process is described in Upgrades and Migration
(2) Estimated Time: The estimated time to complete the migration procedure, including build upload (at 6Mbit/s+) but not including original server(s) cloning time, is ~2-3 hours.
(3) Approach: The overall approach for the migration upgrade process is as follows.
Stages 1-2 – The existing Syndeia 3.5 SP2 environment running in production is cloned to create a new environment that is the basis for Syndeia Cloud 3.6. Syndeia admins should make the Syndeia Cloud 3.5 SP2 production deployment unavailable to Syndeia users before cloning. Syndeia 3.5 SP2 production server can be brought back online after cloning but any data created in it after cloning will not be migrated. This approach is taken to ensure that the existing Syndeia Cloud 3.5 SP2 deployment is always available as a golden starting point for the migration process.
Stages 3-8 – Syndeia Cloud 3.6 installs are downloaded, services are started, and an upgrade is performed in the cloned environment. Data is verified. The cloned environment is now the new Syndeia Cloud 3.6-based production environment.
(4) Linux CentOS EoL: SC 3.5 was released against RHEL/CentOS 7.X. On Dec. 2020, the CentOS Enterprise Linux project (acquired by RH in 2014) was unilaterally redefined as “CentOS Stream” and is no longer based off the stable branch of RHEL but instead off of Fedora (which is deemed the upstream branch of RH OS-es) (see this for more information). As such, CentOS Enterprise Linux 7.9- the last maintenance release for v7, will reach EoL on 30-June-2024 (the same date as that of RHEL 7).
For those using RHEL8, no migration is required
For those using RHEL7, please follow RH’s documentation on how to upgrade to RHEL8
For those still using CentOS (7 or 8), it is recommended to migrate to Alma Linux. Alma Linux is a binary-compatible version of RHEL that was created by CloudLinux to fill this void along with by-laws to prevent such future corporate takeovers. A migration document is beyond the scope of this document but AlmaLinux has put together a tool and a guide to assist with this transition: See Migrate CentOS 7 to AlmaLinux 8
You do not need to upgrade / migrate CentOS to upgrade to SC 3.6, however it is recommended to do so before the EoL date to ensure you continue to have access to yum (now dnf) repository downloads & security updates (IF mandated).
...
The Syndeia Cloud 3.5 → 3.6 migration process has the following 6 stages.
...