> Op 13 september 2017 om 10:38 schreef Dan van der Ster :
>
>
> Hi Blair,
>
> You can add/remove mons on the fly -- connected clients will learn
> about all of the mons as the monmap changes and there won't be any
> downtime as long as the quorum is maintained.
>
> There is one catch when it
On Wed, Sep 13, 2017 at 11:04 AM, Dan van der Ster wrote:
> On Wed, Sep 13, 2017 at 10:54 AM, Wido den Hollander wrote:
>>
>>> Op 13 september 2017 om 10:38 schreef Dan van der Ster
>>> :
>>>
>>>
>>> Hi Blair,
>>>
>>> You can add/remove mons on the fly -- connected clients will learn
>>> about a
On Wed, Sep 13, 2017 at 10:54 AM, Wido den Hollander wrote:
>
>> Op 13 september 2017 om 10:38 schreef Dan van der Ster :
>>
>>
>> Hi Blair,
>>
>> You can add/remove mons on the fly -- connected clients will learn
>> about all of the mons as the monmap changes and there won't be any
>> downtime as
Hi Blair,
You can add/remove mons on the fly -- connected clients will learn
about all of the mons as the monmap changes and there won't be any
downtime as long as the quorum is maintained.
There is one catch when it comes to OpenStack, however.
Unfortunately, OpenStack persists the mon IP addres
Hi all,
We're looking at readdressing the mons (moving to a different subnet)
on one of our clusters. Most of the existing clients are OpenStack
guests on Libvirt+KVM and we have a major upgrade to do for those in
coming weeks that will mean they have to go down briefly, that will
give us an oppor
