Thank you, Eugen, for suggesting the option of leaving the Mons and OSDs co-located if it's not an actual requirement to redeploy Mons. Your insight into the lightweight nature of MON daemons and the possibility of gradually adding new MONs without interrupting cluster services is well-received. We will carefully evaluate whether it's necessary to move the Mons and consider your approach. Anthony, your question about the Ceph release version and deployment method is important. We are currently using Ceph version 16.2.7, and the cluster was initially deployed with Ceph 15 but has been updated recently. Your experience with older releases and unexpected MON behavior is important for us. Tyler, thank you for bringing attention to the potential issues with relocated Mons having new IP addresses and the associated bugs in OpenStack Cinder. We appreciate your advice against redeploying Mons unless it's necessary. Your explanation of how to relocate OSDs without disrupting the cluster is also valuable, especially since we use containerization. We will carefully assess the options and thoroughly plan any changes to ensure minimal disruption and data integrity. Your contributions have been instrumental in helping us navigate this process. Once again, thank you for your support and guidance. Best Regards, Ramin On Sat, Sep 9, 2023 at 7:17 PM Anthony D'Atri <anthony.datri@xxxxxxxxx> wrote: > That may be the very one I was thinking of, though the OP seemed to be > preserving the IP addresses, so I suspect containerization is in play. > > > On Sep 9, 2023, at 11:36 AM, Tyler Stachecki <stachecki.tyler@xxxxxxxxx> > wrote: > > > > On Sat, Sep 9, 2023 at 10:48 AM Anthony D'Atri <anthony.datri@xxxxxxxxx> > wrote: > >> There was also at point an issue where clients wouldn’t get a runtime > update of new mons. > > > > There's also 8+ year old unresolved bugs like this in OpenStack Cinder > > that will bite you if the relocated mons have new IP addresses: > > https://bugs.launchpad.net/nova/+bug/1452641 > > > > Tripling down on what others have said: would advise against > > redeploying mons unless you need to... > > > > FYI: you can relocate the OSDs without having Ceph spew bits about by > > setting noout, stopping the OSDs to be moved, physically moving the > > underlying drive(s) to another host, running `ceph-volume lvm activate > > --all` on the new host, and unsetting noout. > > > > Regards, > > Tyler > > _______________________________________________ > > 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 > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |