what could go wrong with two clusters on the same network?

what could go wrong with two clusters on the same network?

[Xiaopong Tran]

Hi,

If I run two clusters on the same network, each with its own set of
monitors and config files (assuming that we didn't make any error
in the config files), would there be anything wrong with that?

Ceph seems to be quite chatty, so would they mess up their
messages?

Just want to make sure, and just want to know if anyone is
doing that.

Thanks

Xiaopong

Re: what could go wrong with two clusters on the same network?

[Wido den Hollander]

Hi,

On 12/31/2012 11:17 AM, Xiaopong Tran wrote:
> Hi,
>
> If I run two clusters on the same network, each with its own set of
> monitors and config files (assuming that we didn't make any error
> in the config files), would there be anything wrong with that?
>
> Ceph seems to be quite chatty, so would they mess up their
> messages?
>

Ceph is chatty, but it doesn't "pollute" your network.

OSDs only talk to other OSDs they learn from the monitors.

Ceph doesn't use broadcast or multicast in your local network, so it's 
safe to run multiple Ceph clusters in one subnet/VLAN.

Just make sure you use cephx (enabled by default in 0.55) so that you 
don't accidentally connect to the wrong cluster.

Wido

> Just want to make sure, and just want to know if anyone is
> doing that.
>
> Thanks
>
> Xiaopong
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: what could go wrong with two clusters on the same network?

[Gregory Farnum]

On Mon, Dec 31, 2012 at 10:27 AM, Wido den Hollander <wido@widodh.nl> wrote:
> Just make sure you use cephx (enabled by default in 0.55) so that you don't
> accidentally connect to the wrong cluster.

Use of cephx will provide an additional layer of protection for the
clients, but the OSDs and monitors (the only ones with disk state) do
record which cluster they belong to on first start-up, so if they end
up pointed to the wrong cluster they will refuse to connect. Just fyi!
:)
-Greg