I found no options about source IP for ceph. Probably you may try to use
network namespaces to isolate ceph services with desired interfaces.
This would require a bit more setup though. You would need to create
namespace, add some kind of patch (veth?) interface between namespace
and host, but after that all traffic will definitively pass the lo
interface at least once.
On 07/07/2016 01:25 PM, Matyas Koszik wrote:
Hi,
My setup uses a layer3 network, where each node has two connections
(/31s), equipped with a loopback address and redundancy is provided via
OSPF. In this setup it is important to use the loopback address as source
for outgoing connections, since the interface addresses are not protected
from failure, but the loopback address is.
So I set the public addr and the cluster addr to the desired ip, but it
seems that the outgoing connections do not use this as the source address.
I'm using jewel; is this the expected behavior?
Matyas
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
