Can't we get a lot closer to making this automatic by having the monitors try and reach each other on the msgr2 port? We could have them test and enable it for public broadcast automatically if they succeed. That does still leave the possibility of something like the monitors having unrestricted access and the clients being blocked by a firewall. I'm not sure if that's worth worrying about, or if the more complicated test code is worth whatever improvement to the user experience we can get as a result. -Greg On Tue, Jan 8, 2019 at 7:55 PM Sage Weil <sweil@xxxxxxxxxx> wrote: > > On Tue, 8 Jan 2019, Patrick Donnelly wrote: > > On Tue, Jan 8, 2019 at 12:22 PM Sage Weil <sweil@xxxxxxxxxx> wrote: > > > 1) have a big warning in the upgrade notes to verify port 3300 is not > > > firewalled and automatically make the transition, or > > > > > > 2) have an explicit step that enables the new v2 protocol at port 3300, > > > something like > > > > > > ceph mon enable-v2-port > > > > > > The latter is an extra upgrade step admins have to do but is less likely > > > to make the mons appear to go dark during an upgrade. > > > > > > We should probably do #2, right? > > > > +1 on (2). > > https://github.com/ceph/ceph/pull/25849 > > Thanks! > sage
