Merge lp:~tr3buchet/nova/xs_multi_nic into lp:~hudson-openstack/nova/trunk
Status: | Merged |
---|---|
Approved by: | Matt Dietz |
Approved revision: | 808 |
Merged at revision: | 843 |
Proposed branch: | lp:~tr3buchet/nova/xs_multi_nic |
Merge into: | lp:~hudson-openstack/nova/trunk |
Diff against target: |
234 lines (+67/-72) 2 files modified
nova/virt/xenapi/vm_utils.py (+2/-2) nova/virt/xenapi/vmops.py (+65/-70) |
To merge this branch: | bzr merge lp:~tr3buchet/nova/xs_multi_nic |
Related bugs: | |
Related blueprints: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Rick Harris (community) | Approve | ||
Matt Dietz (community) | Approve | ||
Review via email: mp+53458@code.launchpad.net |
Commit message
xenapi support for multi_nic. This is a phase of multi_nic which allows xenapi to work as is and with multi_nic. The other virt driver(s) need to be updated with the same support.
Description of the change
xenapi now supports multi_nic. This has to be merged before or at the same time as multi_nic. Driver receive network information from the compute worker for spawn, inject networking info, and create vifs. Will continue to work if network information is not passed in (for example if multi_nic is not yet implemented). After multi_nic a few of these shims can be deleted.
network info format:
list of (network model object, {network info dict}) pairs. The network info dict is going to be created identically to how mappings are currently created in nova/virt/
Looks ok to me. I also understand your use case from offline discussions.