On Jun 12, 2014, at 11:16 PM, Pete Zaitcev wrote:
> On Thu, 12 Jun 2014 09:52:59 +0100
> Diogo Vieira wrote:
>
>> 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
On Thu, 12 Jun 2014 09:52:59 +0100
Diogo Vieira wrote:
> 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 interna
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 th
On Wed, 11 Jun 2014 18:52:43 +0100
Diogo Vieira 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 o
Hello,
I have an openstack setup that consists only in the Swift and Keystone (and its
dependencies) services, in 2 machines. 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.
The problem is that thi
