Ok, I guess that might work, but I have one problem with that approach. For a service I'm developing I have to know the public URL for an object in the store. For that I use Keystone to find the endpoint of Swift and I get the internal ip. Is there a way for me to set a public endpoint or get the correct ip (the one accessible publicly) of the service?
Diogo Vieira <[email protected]> Programador Eurotux Informática, S.A. | www.eurotux.com (t) +351 253 680 300 On Jun 11, 2014, at 8:09 PM, Pete Zaitcev <[email protected]> wrote: > On Wed, 11 Jun 2014 18:52:43 +0100 > Diogo Vieira <[email protected]> wrote: > >> I have one Proxy Node in the same machine as the Keystone service is as >> well as a Storage Node. On the other machine I have only a Storage Node. > >> What should be the approach used to make this publicly available? What >> ports should be opened in the firewall and what changes do I need to make >> in any of the services? > > You'll be fine with the 5000 for Keystone and whatever your Swift's > front end uses (80, 443, 8080, or 8443). Whatever is used in -A is > your Keystone port, use that. > > -- Pete
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
