E network, then define public/cluster networks
in the config and things still operate?
- Original Message -
From: "Jon Heese"
To: "Bill Campbell"
Cc: ceph-users@lists.ceph.com
Sent: Friday, October 23, 2015 10:03:46 AM
Subject: RE: [ceph-users] Proper Ceph network
se all copies of the message and its
attachments and notify the sender immediately via reply e-mail. **
From: Campbell, Bill [mailto:bcampb...@axcess-financial.com]
Sent: Friday, October 23, 2015 9:11 AM
To: Jon Heese
Cc: ceph-users@lists.ceph.com
Subject: Re: [ceph-users] Proper Ceph network configu
tegration and system administration.
- Original Message -
From: "Jon Heese"
To: ceph-users@lists.ceph.com
Sent: Friday, October 23, 2015 8:58:28 AM
Subject: [ceph-users] Proper Ceph network configuration
Hello,
We have two separate networks in our Ceph cluster design:
10.197.5
On 23-10-15 14:58, Jon Heese wrote:
> Hello,
>
>
>
> We have two separate networks in our Ceph cluster design:
>
>
>
> 10.197.5.0/24 - The "front end" network, "skinny pipe", all 1Gbe,
> intended to be a management or control plane network
>
> 10.174.1.0/24 - The "back end" network, "fat
Hello,
We have two separate networks in our Ceph cluster design:
10.197.5.0/24 - The "front end" network, "skinny pipe", all 1Gbe, intended to
be a management or control plane network
10.174.1.0/24 - The "back end" network, "fat pipe", all OSD nodes use 2x bonded
10Gbe, intended to be the