Thanks for this! Alongside setting os-*-hostname to the public ip address,
I had to login to the aws console and manually open up port 35357, as juju
doesn't expose 35357 (for good measure I'm assuming).
Yeah, I had the same situation in Juju 2.0 ! (all is ok with Juju 1.25)
(with AWS provider)
I
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 keystone deployed to AWS using
