make congress compatible under keystone v3 context

Registered by Su Zhang on 2015-05-01

The current version of congress datasource drivers authenticate with openstack component client code under keystone v2. Therefore while communicating with keystone v3, congress will run into errors. I tested and encountered such errors on datasource drivers of nova, glance, keystone and neutron. I've already made the change accordingly to these datasource drivers to make them compatible with keystone v3. In short, instead of using authentication approach against client code with username and password, we need to use keystone session for authentication. Most of the components can be authenticated with keystone session directly but several other components cannot (for example glance will need to use token which can be extracted from keystone session). I've already fixed these aforementioned datasource drivers. However, congress developers may want to take keystone v3 into consideration before they release the code in the future.

Blueprint information

Status:
Complete
Approver:
Igor Bolotin
Priority:
Undefined
Drafter:
Su Zhang
Direction:
Needs approval
Assignee:
Su Zhang
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon liberty-2
Started by
Su Zhang on 2015-05-01
Completed by
Su Zhang on 2015-05-01

Related branches

Sprints

Whiteboard

(?)

Work Items

Work items:
Resolve issues between keystone v3 and congress nova datasource driver: DONE
Resolve issues between keystone v3 and congress neutron datasource driver: DONE
Resolve issues between keystone v3 and congress glance datasource driver: DONE
Resolve issues between keystone v3 and congress keystone datasource driver: DONE
Integrate and test all four datasource drivers: DONE

This blueprint contains Public information 
Everyone can see this information.