It's simple. Just delete the existing one, keystone endpoint-delete
and then re-create it. However you should follow James's advice and make
sure you understand the security implications first.
On Tue, Oct 20, 2015 at 7:21 PM, Sesso wrote:
> how difficult is it to change the admin endpoint to a
how difficult is it to change the admin endpoint to a public url?
> On Oct 20, 2015, at 5:28 PM, Matt Fischer wrote:
>
> One simple workaround for this if you ssh directly to your Keystone node and
> run the admin commands from there. Once you bootstrap your project with the
> proper tenants a
One simple workaround for this if you ssh directly to your Keystone node
and run the admin commands from there. Once you bootstrap your project with
the proper tenants and users it's not an operation that most people do all
that often. We expose an admin endpoint on an internal load balancer URL
bu
Hi Jason,
Certain commands can only be executed via admin url, which in your case may not
be routable from external networks. You would need to consider changing the
admin endpoint to an ip/FQDN that can be accessed externally (like public url)
or limit the ability to execute those particular c
I have this below.
publicurl |
internalurl| adminurl
https://public.domain.com:5000/v2.0 | http://192.168.0.2:5000/v2.0
| http://192.168.0.2:35357/v2
You should have your public endpoints be externally reachable.
> On Oct 20, 2015, at 2:38 PM, Sesso wrote:
>
> Hello,
>
> I am trying to use a module to automate VM deployments. I can't connect to
> keystone externally so it will make new tenants. What is the best route to
> allow access?
> I
Hello,
I am trying to use a module to automate VM deployments. I can't connect to
keystone externally so it will make new tenants. What is the best route to
allow access?
I am using kilo.
Sent from my iPhone
___
OpenStack-operators mailing list
Ope
