Enable Keystone authN for Quantum in devstack
Bug #1028075 reported by
Salvatore Orlando
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Akihiro Motoki |
Bug Description
We want to allow devstack to deploy Quantum with keystone enabled.
To this aim, we need to perform changes in Quantum to have a 'pipeline factory' method for selecting between a noauth and a keystone pipeline, according to the authentication strategy specified in devstack.
We also want devstack to populate admin credentials in quantum's api-paste.ini
Changed in quantum: | |
importance: | Undecided → Medium |
assignee: | nobody → Salvatore Orlando (salvatore-orlando) |
milestone: | none → folsom-3 |
status: | New → Confirmed |
Changed in quantum: | |
status: | Confirmed → In Progress |
Changed in quantum: | |
status: | In Progress → Fix Committed |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | folsom-3 → 2012.2 |
To post a comment you must log in.
I have already devstack with keystone-enabled Quantum.
In my env, devstack selects auth_mode between a noauth and a keystone pipeline according to Q_AUTH_STRATEGY.
If it is ok, I can push the patch to the review.