devstack support for v2 nova/quantum integration
Bug #1017760 reported by
dan wendlandt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Aaron Rosen |
Bug Description
https:/
adds a new version of quantum / Nova integration. This version require different flags than the older quantum-manager model.
we will need to update devstack to use these new flags (at least to start, this should be optional, and only enabled when quantum v2 is in use).
Changed in quantum: | |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → folsom-2 |
tags: | added: low-hanging-fruit |
Changed in quantum: | |
assignee: | nobody → Aaron Rosen (arosen) |
Changed in quantum: | |
status: | Confirmed → In Progress |
Changed in quantum: | |
milestone: | folsom-2 → folsom-3 |
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 reckon the change would basically consist of making sure the following flags are in place (from Yon's commit message on the gerrit review linked above): api_class= nova.network. quantumv2. api.API admin_username= admin admin_password= password admin_tenant_ name=admin admin_auth_ url=http:// localhost: 5000/v2. 0 auth_strategy= keystone localhost: 9696/
network_
quantum_
quantum_
quantum_
quantum_
quantum_
quantum_url=http://
We do not want to remove network manager flags now.