Feature Freeze Exception: Xen support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Soren Hansen |
Bug Description
I'm embarrassed to say that while I finished Xen support quite a while ago, I never got around to filing the merge proposal. it was dependent on the orm_deux branch and I forgot all about it in the turmoil.
Xen support has been on our list of stuff we wanted to support in Austin since the beginning, so the desire to have it is certainly there. The Xen specific changes are pretty self-contained so shouldn't put anything else at risk. The only risky bit is the part that moves the code to get console output down into the virt drivers and the formatting of the response up into the api server. After much pain and suffering, I've gotten the unit tests for that bit of code running, so I'm fairly confident it works now.
Related branches
- Rick Clark (community): Approve
-
Diff: 223 lines (+94/-24)8 files modifiednova/api/ec2/cloud.py (+10/-5)
nova/compute/manager.py (+1/-17)
nova/fakerabbit.py (+1/-0)
nova/tests/cloud_unittest.py (+0/-1)
nova/virt/fake.py (+2/-0)
nova/virt/libvirt.xen.xml.template (+30/-0)
nova/virt/libvirt_conn.py (+47/-1)
nova/virt/xenapi.py (+3/-0)
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Soren Hansen (soren) |
milestone: | none → austin-feature-freeze |
Changed in nova: | |
status: | Triaged → Fix Committed |
Changed in nova: | |
status: | Fix Committed → Fix Released |
We could help on testing the Xen bits. Where is the code that we would need to pull in?