Re: [openstack-dev] [charms] Deploy Keystone To Public Cloud

2016-11-17 Thread Andrey Pavlov
Yeah, I had the same situation in Juju 2.0 ! (all is ok with Juju 1.25) (with AWS provider) It happens because OpenStack charms started to use 'network-get --primary-address public' instead of 'unit-get'. Then 'network-get public' returns private address and then charms register endpoint with

Re: [openstack-dev] [charms] Deploy Keystone To Public Cloud

2016-11-16 Thread Marco Ceppi
This should work, a charm school at ODS drove this exact thing. I'll give it a try tomorrow to see if I can help. Marco On Thu, Nov 17, 2016, 12:14 AM James Beedy wrote: > I'm having an issue getting a response back (mostly timeouts occur) when > trying to talk to

[openstack-dev] [charms] Deploy Keystone To Public Cloud

2016-11-16 Thread James Beedy
I'm having an issue getting a response back (mostly timeouts occur) when trying to talk to keystone deployed to AWS using private (on vpn) or public ip address. I've had luck with setting os-*-hostname configs, and ssh'ing in and running the keystone/openstack client locally from the keystone