Implement XenAPI support for the VLAN network manager
The XenAPI backed will provide support for the vlan network manager in the same way as this support is currently provided by the libvirt backend.
In a nutshell:
- network node configuration is not going to change
- compute node configuration will be performed using XenAPI calls
Blueprint information
- Status:
- Complete
- Approver:
- Rick Clark
- Priority:
- Medium
- Drafter:
- Salvatore Orlando
- Direction:
- Approved
- Assignee:
- Salvatore Orlando
- Definition:
- Approved
- Series goal:
- Accepted for cactus
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Salvatore Orlando
- Completed by
- Thierry Carrez
Whiteboard
In the current libvirt implementation both the network and the compute service use the same network driver (linux_net).
In order to provide XenAPI support we need a new network driver (which implements only ensure_
For this reason:
- the network service will continue using the linux_net driver
- the compute service will use the new 'xenapi_net' driver
This also means that the two services will use different flags for the network driver
the xenapi_net driver will simply redefine ensure_vlan_bridge in order to create a network with a VLAN ID on the vlan_interface using XenAPI.
