We should make it possible for users to select amongst gre, vxlan or vlan for the tenant networks tunneling. Currently gre is used by default.
To use vxlan:
To use vlan:
- 'datacentre' must be the name of the neutron physical network where the vlans will be allocated (by default we have a single physical network defined in NeutronBridgeMappings)
- 1:1000 is the allocatable range
Gulio, please link your patch in here so we have the docs on how this works.
Following changes were pushed to make the three options working correctly in the templates:
as per report the relevant params are:
NeutronNetworkType: (can be gre, vxlan or vlan)
NeutronTunnelTypes: (can be gre or vxlan)
NeutronEnableTunnelling: (should be false when using vlan type)
NeutronNetworkVLANRanges: datacentre:1:1000 (the neutron phys network name plus the vlan range to use)
*** Bug 1223063 has been marked as a duplicate of this bug. ***
[stack@instack ~]$ rpm -qa |grep tripleo
[stack@instack ~]$ rpm -qa |grep rdo
]$ ssh firstname.lastname@example.org
The authenticity of host '192.0.2.16 (192.0.2.16)' can't be established.
ECDSA key fingerprint is 61:df:21:ce:de:b8:14:3d:b6:b0:80:37:f0:32:cc:ed.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.0.2.16' (ECDSA) to the list of known hosts.
Last login: Tue Jun 30 02:51:58 2015 from 192.0.2.1
# tunnel_types =
# Example: tunnel_types = gre
# Example: tunnel_types = vxlan
# Example: tunnel_types = vxlan, gre
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.