Hi David,
Thanks a lot for your comments!
I just want to utilize a different network than the public one (where dns
resolves the name) for ceph-deploy and client connections.
For example with 3 nics:
Nic1: Public (internet acces)
Nic2: Ceph-mon (clients and ceph-deploy)
Nic3: Ceph-osd
Thanks
The only thing that is supposed to use the cluster network are the OSDs.
Not even the MONs access the cluster network. I am sure that if you have a
need to make this work that you can find a way, but I don't know that one
exists in the standard tool set.
You might try temporarily setting the
Sorry! I'd like to add that I want to use the cluster network for both
purposes:
ceph-deploy --username vdicceph new vdicnode01 --cluster-network
192.168.100.0/24 --public-network 192.168.100.0/24
Thanks a lot
2017-07-28 0:29 GMT+02:00 Oscar Segarra :
> Hi,
>
> ¿Do you
I could be wrong, but I think you cannot achieve this objective. If you
declare a cluster network, OSDs will route heartbeat, object replication
and recovery traffic over the cluster network. We prefer that the cluster
network is NOT reachable from the public network or the Internet for added
Hi,
In my environment I have 3 hosts, every host has 2 network interfaces:
public: 192.168.2.0/24
cluster: 192.168.100.0/24
The hostname "vdicnode01", "vdicnode02" and "vdicnode03" are resolved by
public DNS through the public interface, that means the "ping vdicnode01"
will resolve