If you want to follow the recommended method and separate public and cluster traffic than they need to be two separate subnets as that is how they are defined in the config file.
For example:
public_network = 192.168.1.0/24
cluster_network = 10.1.9.0/24
I do recommend separating your public and cluster networks but there's not a whole lot of benefit to it unless they are using physically separate links with dedicated bandwidth.
If you only have a single 10G link then don't define a cluster_network in your config and all traffic will route over the public network by default.
___
John Petrini
NOC Systems Administrator // CoreDial, LLC // coredial.com //
Hillcrest I, 751 Arbor Way, Suite 150, Blue Bell PA, 19422
P: 215.297.4400 x232 // F: 215.297.4401 // E: jpetrini@xxxxxxxxxxxx
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
On Thu, Jan 12, 2017 at 7:00 AM, Sivaram Kannan <sivaramsk@xxxxxxxxx> wrote:
Hi,
CEPH first time user here. I am trying to setup a ceph cluster. The
documentation (http://ceph.com/planet/bootstrap-your-ceph-cluster- )in-docker/
recommends a seperate network for control and data plane
1. Can i configure both control plane in the same network?
2. Is it so bad to configure that way even if I have a 10G pipe??
Thanks,
./Siva.
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph. com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
