2e7eb09271
This agent is required by the macvtap ml2 driver to support
macvtap attachments for libvirt qemu/kvm instances. It introduces
a new configuration option MACVTAP.physical_interface_mappings.
The review is submitted in three parts:
- Part 1
Common functions that are used by the ml2 driver and the agent
- Part 2
The Mechanism Driver to support port binding for macvtap attachments
- Part 3 (this part)
The Macvtap L2 Agent.
DocImpact
New ML2 mech driver + l2 agent
New config option "macvtap.physical_interface_mappings"
Change-Id: I219d80b4c704ac2f41edd3501f4b2198925778d6
Closes-Bug: #1480979
19 lines
1021 B
YAML
19 lines
1021 B
YAML
---
|
|
prelude: >
|
|
Adding MacVtap ML2 driver and L2 Agent as new vswitch choice
|
|
features:
|
|
- Libvirt qemu/kvm instances can now be attached via MacVtap in
|
|
bridge mode to a network. VLAN and FLAT attachments are
|
|
supported. Other attachmentes than compute are not supported.
|
|
issues:
|
|
- To ensure any kind of migration works between all compute nodes,
|
|
make sure that the same physical_interface_mappings is
|
|
configured on each MacVtap compute node. Having different
|
|
mappings could cause live migration to fail (if the configured
|
|
physical network interface does not exist on the target host), or
|
|
even worse, result in an instance placed on the wrong physical
|
|
network (if the physical network interface exists on the target
|
|
host, but is used by another physical network or not used at all
|
|
by OpenStack). Such an instance does not have access to its
|
|
configured networks anymore. It then has layer 2 connectivity to
|
|
either another OpenStack network, or one of the hosts networks. |