The strange part is that I do have os_auth_host configured in savanna.conf,
pointing to the IP address of the keystone server. That value appears to be
ignored. I guess I'll have to setup a debugging session.
Going Mobile
> On Nov 10, 2013, at 4:41 PM, Matthew Farrellee wrote:
>
> Jon,
>
>
Jon,
I ran into this issue and we discussed on IRC a couple weeks ago.
At least for the Vanilla plugin you have to supply a instance->infra
routable addr/ip for os_auth_host in your savanna.conf.
https://bugs.launchpad.net/savanna/+bug/1244309
Ultimately I'd like to add some code that uses t
I've got two guesses why it does not work properly:
1. Savanna does not consume config file at all and the defaults (by
coincidence) do not work for swift only.
2. you invoke swift_helper.get_swift_configs() at the top level of some
module like that:
SWIFT_CONFIG = swift_helper.get_swift_co
I'm not sure that would help - all my code changes are runtime changes
associated with EDP actions (i.e. the cluster and its configuration are already
set). I was looking for help in trying to ascertain why the swift_helper would
not return the savanna.conf value at provisioning time.
-- Jon
Hey Jon,
Can you post your code as a work in progress review? Maybe we can perceive
from the code what is wrong.
Thanks,
Dmitry
2013/11/10 Jon Maron
> Hi,
>
> I am debugging an issue with the swift integration - I see os_auth_url
> with a value of 127.0.0.1, indicating that at the time the
Hi,
I am debugging an issue with the swift integration - I see os_auth_url with a
value of 127.0.0.1, indicating that at the time the swift helper is invoked the
default value for auth host is being leveraged rather than the value in the
savanna.conf file. Any ideas how that may happen?
Mor
