Open gustavosr98 opened 1 month ago
See https://github.com/canonical/microceph/issues/197
Changing the public network after the bootstrap doesn't quite work so it was removed from the doc but the removal hasn't been backported it seems.
As @nobuto-m mentioned, changing the Public Network laterally is very complicated. To prevent this situation from coming in, we removed the ability to configure public network (from the CLI) as well as docs. This has been backported to quincy/edge but has not made it's way back to quincy/stable (unfortunately, taking a note here.). I would recommend using reef track since it has a better stability/velocity factor.
(From a parallel conversation) I figure Ceph allows for configuring multiple public networks (Microceph doesn't, but we can fix that), this can be used to migrate the public networks of a Ceph cluster. Now this will require some operator diligence but MicroCeph can be more helpful here.
Issue report
Trying to change network binds after bootstrap does not seem to work
What version of MicroCeph are you using ?
quincy/stable (0+git.4a608fc)
What happens (observed behaviour) ?
Now I followed this to change the network bind to another one https://canonical-microceph.readthedocs-hosted.com/en/quincy-stable/how-to/configure-network-keys/
But it still binds to the old network
What were you expecting to happen ?
I was expecting to be able to change the network configuration binding after having bootstrapped a ceph cluster to migrate from one network to another