yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #55727
[Bug 1618433] Re: vxlan tunnel does not get created
Your tenant_network_types = vlan suggests that the network is VLAN. So
it's of no surprise you don't see any tunnels. They are not needed. The
fact that you enabled the type driver in ml2 and set tunnel_types =
vxlan on the agent does not mean that VXLAN will be used for all
networks. It only means that IF you have a VXLAN network, it will be
handled by the cluster.
I don't see an issue here, and the bug report does not even talk in
terms of user visible issues. I suggest we mark it as invalid.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1618433
Title:
vxlan tunnel does not get created
Status in neutron:
Invalid
Bug description:
in multinode scenario, vxlan tunnel between compute and network nodes
does not get created. Latest master is used for neutron components.
vlan is configured as tenants type and vxlan is configured as a tunnel
type. br-tun does not show vxlan interface.
[ml2]
type_drivers = flat,vlan,vxlan
tenant_network_types = vlan
mechanism_drivers = openvswitch,l2population
[ml2_type_vlan]
network_vlan_ranges = physnet2:1:3999
[ml2_type_flat]
flat_networks = physnet1
[ml2_type_vxlan]
vni_ranges = 1:1000
vxlan_group = 239.1.1.1
[securitygroup]
firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
[agent]
tunnel_types = vxlan
l2_population = true
arp_responder = true
[ovs]
bridge_mappings = physnet1:br-ex, physnet2:br-tnts
ovsdb_connection=tcp:10.57.120.13:6640
local_ip=10.57.120.13
Bridge br-tun
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port br-tun
Interface br-tun
type: internal
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1618433/+subscriptions
References