On Fri, Aug 9, 2013 at 1:06 PM, Alessio Ababilov <aababi...@griddynamics.com> wrote:
>> Well, first I wrote two separate plugins for v2 and v3, but I decided >> to join them just for command-line tool convenience: user can omit >> "--os-auth-system=keystone" option and the system will be chosen >> automatically based on available arguments (in >> auth.load_plugin_from_args function). >> And v3 and v2 are distinguished by --os-identity-api-version option of >> the plugin. I'd like to suggest that having the option to use different Identity API versions for auth and for the other client operations would be useful. I'm not sure if that is inherent in this design or not... >> > Another standalone change is that v2 and v3 both currently authenticate >> > to keystone immediately upon creation, under the apiclient they won't. >> > I've got no real opinion either way but it may cause some discussion. >> I have developed the first version of common API client library more >> than a year ago for our own Web dashboard in Grid Dynamics and I >> definitely vote for lazy authentication. It is more convenient for >> user; also, authentication can be perfectly called explicitly by >> HttpClient.authenticate() One of the challenges I've had with OpenStackClient is to only perform the auth once then stuff the proper credentials into the other (compute, image, etc) clients to prevent them from doing it again. Again, my apologies for not having kept up on this but a completely separate auth step that can either be called as-needed or performed up front and passed in to the clients would be extremely useful. dt -- Dean Troyer dtro...@gmail.com _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
