On Wed, Oct 25, 2017 at 3:07 PM, Dmitry Tantsur <dtant...@redhat.com> wrote:
> Hi! > > Thanks for raising this. > > On 10/19/2017 01:11 PM, Vladyslav Drok wrote: > >> Hi! >> >> I'd like to discuss the usage of the new noauth plugin to keystoneauth, >> which was introduced in [1]. 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 [2], and encountered some problems, which are hacked around in [3]. >> >> So, here are some questions: >> >> 1. Was it intended to be used in CLI at all, or should we still use the >> token_endpoint? >> 2. If it was intended, should we: >> 2.1. do the hacks as in [3]? >> > > I don't particularly like hardcoding an entrypoint name in the code here, > to be honest. > > 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. > I'll go with this option, Dean also suggested this in his review of [3] > > 2.3. leave it as-is, allowing the usage of none loader only by >> specifying the parameters in the clouds.yaml, as in [4] 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). > > >> [1] https://review.openstack.org/469863 <https://review.openstack.org/ >> 469863> >> [2] https://review.openstack.org/359061 >> [3] https://review.openstack.org/512699 >> [4] https://github.com/openstack/bifrost/blob/21ca45937a9cb36c6f >> 04073182bf2edea8acbd5d/playbooks/roles/bifrost-keystone-client-config/ >> templates/clouds.yaml.j2#L17-L19 >> >> Thanks, >> Vlad >> >> >> ____________________________________________________________ >> ______________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev