> Le 11 mai 2018 à 08:36, Matt Riedemann <mriede...@gmail.com> a écrit : > > On 5/10/2018 6:30 PM, Jean-Philippe Méthot wrote: >> 1.I was talking about the region-name parameter underneath >> keystone_authtoken. That is in the pike doc you linked, but I am unaware if >> this is only used for token generation or not. Anyhow, it doesn’t seem to >> have any impact on the issue at hand. > > The [keystone]/region_name config option in nova is used to pike the identity > service endpoint so I think in that case region_one will matter if there are > multiple identity endpoints in the service catalog. The only thing is you're > on pike where [keystone]/region_name isn't in nova.conf and it's not used, it > was added in queens for this lookup: > > https://review.openstack.org/#/c/507693/ > > So that might be why it doesn't seem to make a difference if you set it in > nova.conf - because the nova code isn't actually using it. >
I was talking about the parameter under [keystone_authtoken] ([keystone_authtoken]/region_name) and not the new one under [keystone] ([keystone]/region_name). It seems that we were talking about different parameters though so this explains that. > You could try backporting that patch into your pike deployment, set > region_name to RegionOne and see if it makes a difference (although I thought > RegionOne was the default if not specified?). I will attempt this next week. Will update if I run into any issues. Also, from experience, most Openstack services seem to pick a random endpoint when region_name isn’t specified in a multi-region cloud. I’ve seen that several times ever since I've built and started maintaining this infrastructure.
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
