[openstack-dev] [keystoneauth] [osc] [ironic] Usage of none loader in the CLI
dtantsur at redhat.com
Wed Oct 25 12:07:09 UTC 2017
Thanks for raising this.
On 10/19/2017 01:11 PM, Vladyslav Drok wrote:
> I'd like to discuss the usage of the new noauth plugin to keystoneauth, which
> was introduced in . The docstring of the loader says it is intended to be
> used during adapter initialization along with endpoint_override. But what about
> the CLI usage in the OpenStack client? I was trying to make the none loader work
> with baremetal plugin, as part of testing , and encountered some problems,
> which are hacked around in .
> So, here are some questions:
> 1. Was it intended to be used in CLI at all, or should we still use the
> 2. If it was intended, should we:
> 2.1. do the hacks as in ?
I don't particularly like hardcoding an entrypoint name in the code here, to be
> 2.2. introduce endpoint as an option for the none loader, making it a bit
> similar to token_endpoint, with token hardcoded (and also get_endpoint method to
> the auth plugin I think)?
I think that's the way to go, we should fix the none loader in keystoneauth.
> 2.3. leave it as-is, allowing the usage of none loader only by specifying
> the parameters in the clouds.yaml, as in  for example?
That's not great. We're getting rid of the "ironic" command in favour of
"openstack baremetal", but inability to properly use a no-auth mode hurts quite
a few of our use cases (like Bifrost).
>  https://review.openstack.org/469863 <https://review.openstack.org/469863>
>  https://review.openstack.org/359061
>  https://review.openstack.org/512699
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev