group_binds for provider networks has no effect on neutron provider mappings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Undecided
|
James Denton |
Bug Description
When users define provider networks in /etc/openstack_
Example:
- network:
type: "vlan"
range: "101:200,301:400"
net_name: "vlan"
- neutron_
- network:
type: "vlan"
net_name: "physnet-pnet"
range: "2000:2100"
- neutron_l3_agent
In this example, both networks will be configured as Neutron provider networks in the respective agent and ml2_config files despite the group_binds values:
Compute:
# ML2 VLAN networks
[ml2_type_vlan]
network_vlan_ranges = vlan:101:
# Linux bridge agent physical interface mappings
[linux_bridge]
physical_
Network node:
# ML2 VLAN networks
[ml2_type_vlan]
network_vlan_ranges = vlan:101:
# Linux bridge agent physical interface mappings
[linux_bridge]
physical_
The desired state is as follows:
Compute:
# ML2 VLAN networks
[ml2_type_vlan]
network_vlan_ranges = vlan:101:
# Linux bridge agent physical interface mappings
[linux_bridge]
physical_
Network node:
# ML2 VLAN networks
[ml2_type_vlan]
network_vlan_ranges = vlan:101:
# Linux bridge agent physical interface mappings
[linux_bridge]
physical_
Changed in openstack-ansible: | |
assignee: | nobody → James Denton (james-denton) |
Changed in openstack-ansible: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. openstack. org/592659
Review: https:/