Cephadm-Managed Cluster to CES
Switching from another version of Ceph to Clyso Enterprise Storage is as simple as an upgrade! The CES container is also managed by cephadm, so the procedure is the same as upgrading to a new version of Ceph.
Start the upgrade by pulling the CES image from the registry. You can find the latest image name in our Getting Started guide.
For example, to upgrade to CES 25.03.2:
ceph orch upgrade start --image harbor.clyso.com/ces/ceph/ceph:ces-v25.03.2
Or to upgrade to CES 25.03.1:
ceph orch upgrade start --image harbor.clyso.com/ces/ceph/ceph:ces-v25.03.1
This will start the migration process and pull the latest CES image from the registry. To follow the progress of the migration, you can run the following command:
watch ceph -s
progress:
Upgrade to 18.2.4-21-g3462c366fdd (72s)
[========....................] (remaining: 3m)
Global Recovery Event (30s)
[=============...............] (remaining: 30s)
Below are useful commands to monitor the migration process:
ceph -W cephadm --watch-debug
watch ceph orch upgrade status
To verify the migration, you can run the following command:
ceph versions
Head over to the Ceph Copilot section to learn more about the new features and functionalities of the latest version of CES.
Migrate from CES to Ceph Upstream
When migrating back to upstream Ceph, ensure compatibility between your CES container version and the target upstream version. Some migration paths have known issues.
Compatibility Matrix
| From CES Version | To Upstream Ceph | Compatibility | Recommended Target |
|---|---|---|---|
| CES 25.03.2 (18.2.7) | Ceph 18.2.7+ | Fully Compatible | 18.2.7 or later |
| CES 25.03.1 (18.2.4) | Ceph 18.2.4 | ⚠️ Known Bug | Recommended - to use 18.2.7+ |
| CES 25.03.1 (18.2.4) | Ceph 18.2.7+ | Recommended | 18.2.7 or later |
upgrade bug from 25.03.1 to 18.2.4 is highlighted in this upstream tracker: https://tracker.ceph.com/issues/67660. There is a workaround fix to get around this issue which involes modifying the MGR keys.