| 1 |
--- |
| 2 |
prelude: > |
| 3 |
The ML2/OVS and ML2/OVN drivers had inconsistencies on how IGMP was |
| 4 |
configured. Prior to this patch Neutron only exposed a single IGMP |
| 5 |
configuration option (``igmp_snooping_enabled``) and other features |
| 6 |
such as flooding IGMP packets, flooding reports and flooding to |
| 7 |
unregistered ports were hard coded differently in each driver. |
| 8 |
This patch introduces Neutron configuration options for those listed |
| 9 |
IGMP features. |
| 10 |
As part of this work, default values in the IGMP snooping |
| 11 |
configuration had to be changed for the ML2/OVS backend. Please |
| 12 |
check in the following sections for more details. |
| 13 |
features: |
| 14 |
- | |
| 15 |
New configuration options for IGMP were added in the [OVS] section: |
| 16 |
``igmp_flood``, ``igmp_flood_reports`` and ``igmp_flood_unregistered``. |
| 17 |
This gives operators full control on how IGMP should be configured for |
| 18 |
their deployments. |
| 19 |
upgrade: |
| 20 |
- | |
| 21 |
In order to make IGMP configuration consistent across drivers |
| 22 |
some defaults had to be changed for ML2/OVS. This change did not |
| 23 |
affect the defaults in the ML2/OVN driver. |
| 24 |
|
| 25 |
If ML2/OVS is used and ``igmp_snooping_enable`` is enabled, in order |
| 26 |
to make the IGMP related traffic run as before please ensure that |
| 27 |
the following configuration options are enabled after the upgrade. |
| 28 |
|
| 29 |
``[OVS]/igmp_flood_unregistered`` = True |
| 30 |
``[OVS]/igmp_flood`` = True |
| 31 |
``[OVS]/igmp_flood_reports`` = True |