Re: Upgrading OS [and ceph release] nondestructively for oldish Ceph cluster

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

the upgrade question pops up quite regularly, the latest I recall was discussed in this thread [1].

We've had a Nautilus [latest releases] cluster for some years now, and are planning the upgrade process - both moving off Centos7 [ideally to a RHEL9 compatible spin like Alma 9 or Rocky 9] and also moving to a newer Ceph release [ideally Pacific or higher to avoid too many later upgrades needed].

It's not supported to upgrade from N to a later release than P(acific).

For Ceph bluestore OSDs, I assume all the relevant metadata is on the OSD disk [or on the separate disk configured for RocksDB etc if you have nvme], and none is on the OS itself? For Mons and Mgrs, what stuff do I need to retain across the OS upgrade to have things "just work" [since they're relatively stateless, I assume mostly the /etc/ceph/ stuff and ceph cluster keys?]

Basically yes, backing up the /etc/ceph directory with some important keyrings (e. g. admin keyring) and maybe the auth keys can't hurt. It's not really necessary since you usually upgrade nodes one by one, in case the upgrade fails on one node all the information is still available. But it can be comforting having the backup.

Regards,
Eugen

[1] https://lists.ceph.io/hyperkitty/list/ceph-users@xxxxxxx/thread/N2RPRULADF3MAYBD7PGHSBGHXBFPHAHM/#7D67BUT4VQRVZMCKCUD4AEC64T4KBR5U

Zitat von Sam Skipsey <aoanla@xxxxxxxxx>:

Hello all,

We've had a Nautilus [latest releases] cluster for some years now, and are planning the upgrade process - both moving off Centos7 [ideally to a RHEL9 compatible spin like Alma 9 or Rocky 9] and also moving to a newer Ceph release [ideally Pacific or higher to avoid too many later upgrades needed].

As far as ceph release upgrades go, I understand the process in general.

What I'm less certain about (and more nervous about from a potential data loss perspective) is the OS upgrade. For Ceph bluestore OSDs, I assume all the relevant metadata is on the OSD disk [or on the separate disk configured for RocksDB etc if you have nvme], and none is on the OS itself? For Mons and Mgrs, what stuff do I need to retain across the OS upgrade to have things "just work" [since they're relatively stateless, I assume mostly the /etc/ceph/ stuff and ceph cluster keys?] For the MDS, I assume it's similar to MGRS? The MDS, IIRC, mainly works as a caching layer so I assume there's not much state that can be lost permanently?

Has anyone gone through this process who would be happy to share their experience? (There's not a lot on this on the wider internet - lots on upgrading ceph, much less on the OS)

Sam
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx


_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux