x
/
fuel-ccp-neutron
Code Issues Proposed changes

Allow configuring VxLAN VNI IDs 

VNI ID ranges for VxLAN are currently harcoded, it makes sense to
make them configurable, like VLAN ranges for physnets.

Change-Id: Ie3468f51eb606e95c5fdac5f7a1d677a08c9b510
This commit is contained in:
Elena Ezhova 2017-01-24 16:23:48 +04:00
parent e6f78fe6aa
commit 2d8e6b0b13
2 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
service/files/defaults.yaml
View File

@ -11,6 +11,8 @@ configs:
ml2:
tenant_network_types:
- "vxlan"
vni_ranges:
- "1:1000"
physnets:
- name: "physnet1"
bridge_name: "br-ex"

2
service/files/ml2_conf.ini.j2
View File

@ -34,7 +34,7 @@ flat_networks =
{%- endfor %}
[ml2_type_vxlan]
vni_ranges = 1:1000
vni_ranges = {{ neutron.ml2.vni_ranges|join(',') }}
vxlan_group = 239.1.1.1
[securitygroup]