Re: [charms] Deploy Keystone To Public Cloud
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) 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 private address and then they do not work from outside. I could solve this only be setting 'os-public-hostname' to floating-ip of specific machine. On Thu, Nov 17, 2016 at 2: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 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 > instance after adding the private ip <-> fqdn mapping in > keystone:/etc/hosts, but can't seem to come up with any combination that > lets me talk to the keystone api remotely. Just to be clear, I'm only > deploying keystone and percona-cluster charms to AWS, not all of Openstack. > > If not possible using the ec2 provider, is this a possibility with any > public providers? > > Thanks > > _ -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: [charms] Deploy Keystone To Public Cloud
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 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 > instance after adding the private ip <-> fqdn mapping in > keystone:/etc/hosts, but can't seem to come up with any combination that > lets me talk to the keystone api remotely. Just to be clear, I'm only > deploying keystone and percona-cluster charms to AWS, not all of Openstack. > > If not possible using the ec2 provider, is this a possibility with any > public providers? > > Thanks > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[charms] Deploy Keystone To Public Cloud
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 instance after adding the private ip <-> fqdn mapping in keystone:/etc/hosts, but can't seem to come up with any combination that lets me talk to the keystone api remotely. Just to be clear, I'm only deploying keystone and percona-cluster charms to AWS, not all of Openstack. If not possible using the ec2 provider, is this a possibility with any public providers? Thanks -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
