You may need split horizon DNS. The internal machines' DNS should resolve to the internal IP, and the external machines' DNS should resolve to the external IP.
There are various ways to do that. The RadosGW config has an example of setting up Dnsmasq: http://ceph.com/docs/master/radosgw/config/#enabling-subdomain-s3-calls
On Tue, Dec 16, 2014 at 3:05 AM, Georgios Dimitrakakis <giorgis@xxxxxxxxxxxx> wrote:
Thanks Craig.
I will try that!
I thought it was more complicate than that because of the entries for the "public_network" and "rgw dns name" in the config file...
I will give it a try.
Best,
George
That shouldnt be a problem. Just have Apache bind to all interfaces
instead of the external IP.
In my case, I only have Apache bound to the internal interface. My
load balancer has an external and internal IP, and Im able to talk to
it on both interfaces.
On Mon, Dec 15, 2014 at 2:00 PM, Georgios Dimitrakakis wrote:
Hi all!
I have a single CEPH node which has two network interfaces.
One is configured to be accessed directly by the internet (153.*)
and the other one is configured on an internal LAN (192.*)
For the moment radosgw is listening on the external (internet)
interface.
Can I configure radosgw to be accessed by both interfaces? What I
would like to do is to save bandwidth and time for the machines on
the internal network and use the internal net for all rados
communications.
Any ideas?
Best regards,
George
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx [1]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com [2]
Links:
------
[1] mailto:ceph-users@xxxxxxxxxx.com
[2] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
[3] mailto:giorgis@xxxxxxxxxxxx
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
