yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #34587
[Bug 1328991] Re: External network should not have provider:network_type as vxlan
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1328991
Title:
External network should not have provider:network_type as vxlan
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
Given this is the ml2_conf.ini file on a controller node that also runs neutron API server, DHCP and L3 agents.
[ml2]
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,l2population
tenant_network_types = vxlan
[ml2_type_flat]
[ml2_type_vlan]
[ml2_type_gre]
tunnel_id_ranges = 1:1000
[ml2_type_vxlan]
vni_ranges = 1001:65535
[database]
connection = mysql://...
[ovs]
local_ip = 192.0.2.24
enable_tunneling = True
[agent]
tunnel_types = vxlan
l2_population = True
polling_interval = 2
minimize_polling = True
[securitygroup]
firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
When the tripleo-incubator's setup-neutron.sh script creates the
external network on this node (devstack runs the same command):
neutron net-create ext-net --router:external=True
neutron net-show ext-net displays:
# neutron net-show ext-net
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | 94384f38-0cb0-4336-a7c3-293858dec2ba |
| name | ext-net |
| provider:network_type | vxlan |
| provider:physical_network | |
| provider:segmentation_id | 1002 |
| router:external | True |
| shared | False |
| status | ACTIVE |
| subnets | b0585eeb-ea5a-4741-a759-4497f6e6c21a |
| tenant_id | 8b0a6343ca3e471bbcf0a78e084a98c0 |
+---------------------------+--------------------------------------+
The provider:network_type of vxlan is not appropriate for an external network because the only ports possible on it are floatingips and router gateways. There are no VM ports. So vxlan tunnels for this network won't be created at all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1328991/+subscriptions
References