Glance must support keystone sessions

Bug #1588356 reported by Raildo Mascena de Sousa Filho
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Undecided
Raildo Mascena de Sousa Filho

Bug Description

Glance is one of the last OpenStack services left that does not support instantiating a client using an existing Keystone session object. This complicates handling glance-related code in other projects.

Moving to Keystone sessions would also enable easier integration with various auth methods supported by Keystone as well as different Keystone API versions.

Changed in glance:
assignee: nobody → Raildo Mascena de Sousa Filho (raildo)
Changed in glance:
status: New → In Progress
summary: - keystoneauth session support
+ Glance must support keystone sessions
Revision history for this message
Kairat Kushaev (kkushaev) wrote :

Hi,
could you please clarify the point about sessions?
From what I know, glanceclient supports sessions:
https://github.com/openstack/python-glanceclient/blob/6f2fae7a19dc98286cd44519b5a0d9ed566610cc/glanceclient/common/http.py#L341
Did you mean sessions in glanceclient or somethere else?
Also sessions are default method of auth in glanceclient since Mitaka.

Changed in glance:
status: In Progress → Incomplete
Revision history for this message
Raildo Mascena de Sousa Filho (raildo) wrote :

Nowadays, when glance calls Keystone to authenticate, they are doing a HTTP call direct for the keystone endpoint using deprecated identity API version (v1 and v2).
As you can see here: https://github.com/openstack/glance/blob/master/glance/common/auth.py#L209 for example.

So, glanceclient are correct, but we need to do similar work on glance too.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers