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]?
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)?
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?
[1] https://review.openstack.org/469863
[2] https://review.openstack.org/359061
[3] https://review.openstack.org/512699
[4]
https://github.com/openstack/bifrost/blob/21ca45937a9cb36c6f04073182bf2edea8acbd5d/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:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
