Hi,
there have been a couple of threads wrt network change, simply
restarting OSDs is not sufficient. I still haven't had to do it
myself, but did you 'ceph orch reconfig osd' after adding the second
public network, then restart them? I'm not sure if the orchestrator
works as expected here, last year there was a thread [1] with the same
intention. Can you check the local ceph.conf file
(/var/lib/ceph/<FSID>/<SERVICE>/config) of the OSDs (or start with
one) if it contains both public networks? I (still) expect the
orchestrator to update that config as well. Maybe it's worth a bug
report? If there's more to it than just updating the monmap I would
like to see that added to the docs since moving monitors to a
different network is already documented [2].
Regards,
Eugen
[1] https://www.spinics.net/lists/ceph-users/msg75162.html
[2]
https://docs.ceph.com/en/quincy/cephadm/services/mon/#moving-monitors-to-a-different-network
Zitat von Boris Behrens <bb@xxxxxxxxx>:
Hi,
I need to migrate a storage cluster to a new network.
I added the new network to the ceph config via:
ceph config set global public_network "old_network/64, new_network/64"
I've added a set of new mon daemons with IP addresses in the new network
and they are added to the quorum and seem to work as expected.
But when I restart the OSD daemons, the do not bind to the new addresses. I
would have expected that the OSDs try to bind to all networks but they are
only bound to the old_network.
The idea was to add the new set of network config to the current storage
hosts, bind everything to ip addresses in both networks, shift over
workload, and then remove the old network.
_______________________________________________
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
