Instead of hardcoding the VLAN ranges in reclass, read them from IDF.
This is required when VLAN segmentation is used instead of VXLAN, as
lab switches should be configured appropiately (e.g. Armband PODs use
VLANs 2000+ instead of 1000-1030).
Change-Id: I009ccea9b328c40f055a745791eafe3393b96390
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
mask: 24
private:
interface: 2 # when used, will be third vnet interface, untagged
- vlan: native
+ vlan: 1000-1999
network: 10.1.0.0
mask: 24
public:
parameters:
_param:
neutron_tenant_network_types: "flat,vlan"
- neutron_tenant_vlan_range: "1000:1030"
+ neutron_tenant_vlan_range: ${_param:opnfv_net_tenant_vlan}
neutron:
server:
backend:
- tenant_vlan_range: 1000:1999
+ tenant_vlan_range: ${_param:opnfv_net_tenant_vlan}
-Subproject commit a3c0456cc14a75e96808505e670d0cab37b30abc
+Subproject commit c7034503e2bb8da20f2b5c678719c7c7fbe6e61f