Hi,
On 1/31/20 12:09 AM, Nigel Williams wrote:
Did you end up having all new IPs for your MONs? I've wondered how
should a large KVM deployment be handled when the instance-metadata
has a hard-coded list of MON IPs for the cluster? how are they changed
en-masse with running VMs? or do these
On 1/31/20 12:09 AM, Nigel Williams wrote:
> Did you end up having all new IPs for your MONs? I've wondered how
> should a large KVM deployment be handled when the instance-metadata
> has a hard-coded list of MON IPs for the cluster? how are they changed
> en-masse with running VMs? or do these
Did you end up having all new IPs for your MONs? I've wondered how
should a large KVM deployment be handled when the instance-metadata
has a hard-coded list of MON IPs for the cluster? how are they changed
en-masse with running VMs? or do these moves always result in at least
one MON with an
node, so there are
3 there.
- move an osd node to the new location
- wait for recovery
Etc.
Something like this? What is the idea about having 5 monitors in this
migration?
-Original Message-
To: ceph-users
Subject: Re: [ceph-users] moving small production cluster to different
On 1/28/20 6:58 PM, Anthony D'Atri wrote:
>
>
>> I did this ones. This cluster was running IPv6-only (still is) and thus
>> I had the flexibility of new IPs.
>
> Dumb question — how was IPv6 a factor in that flexibility? Was it just that
> you had unused addresses within an existing block?
I did this, but with the benefit of taking the network with me, just a forklift
from one datacenter to the next.
Shutdown the clients, then OSDs, then MDS/MON/MGRs, then switches.
Reverse order back up,
> On Jan 28, 2020, at 4:19 AM, Marc Roos wrote:
>
>
> Say one is forced to move a
And us too, exactly as below. One at a time then wait for things to
recover before moving the next host. We didn't have any issues with this
approach either.
Regards,
Simon.
On 28/01/2020 13:03, Tobias Urdin wrote:
We did this as well, pretty much the same as Wido.
We had a fiber connection
We did this as well, pretty much the same as Wido.
We had a fiber connection with good latency between the locations.
We installed a virtual monitor in the destination datacenter to always
keep quorum then we
simply moved one node at a time after setting noout.
When we took a node up on the
On 1/28/20 11:19 AM, Marc Roos wrote:
>
> Say one is forced to move a production cluster (4 nodes) to a different
> datacenter. What options do I have, other than just turning it off at
> the old location and on on the new location?
>
> Maybe buying some extra nodes, and move one node at a
