Keystoneclient session objects are well entrenched now. They provide a number of benefits as they essentially hand of the process of fetching authentication tokens and dealing with the service catalog that clients often make a mess of. They provide integration with auth_token middleware and loading from CONF files so there is now a standard way to define credentials for service to service communication.

Glanceclient should accept a session object and the other parameters that session aware clients support. This will allow much easier use for service -> service communication.

This pattern has already been adopted by at least: novaclient, cinderclient, keystoneclient, neutronclient, and most of the 'newer' project clients. The current notable absences are swiftclient and glanceclient.

Glanceclient is different to other clients, it has never accepted credentials and it has custom SSL handling. We will be able to support these options for clients initiated using the current option sets, however i don't think we will be able to support it when a keystoneclient session is passed to it.

Some examples:

https:/ /blueprints. launchpad. net/python- glanceclient/ +spec/session- objects