I have a fairly run-of-the-mill cephadm managed/containerized 20.2.1 cluster. Not hyperconverged or anything like that. It's currently exporting RBD to a Proxmox VE 8.4 cluster (QEMU virtualization), and CephFS to a couple RHEL 8.x servers via kernel mounts. I need to migrate the whole thing, including the monitors, to new hardware. My question is, can I rely on the QEMU processes and kernel mounts to correctly update their internal monitor maps as I add new monitors and remove old monitors, or will I suddenly reach a point where the consumers can't find the monitors they started up with and lose their minds? (I know I'll also need to update the static configs.) I'm pretty sure it should Just Work so long as I don't do something dumb and lose quorum, but there's a big difference between "should" and "actually does", and I haven't been able to find any writeups of people actually doing it, so I'm asking here. Is this likely to work? Is this known to not work for some reason (e.g., the kernel mounts or QEMU processes never actually update their mon maps after startup)? TIA! ----- Edward Huyer Golisano College of Computing and Information Sciences Rochester Institute of Technology Golisano 70-2373 152 Lomb Memorial Drive Rochester, NY 14623 585-475-6651 erhvks@rit.edu<mailto:erhvks@rit.edu> Obligatory Legalese: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.