[reclass] Parameterize tenant VLAN ranges 99/55999/3
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Wed, 18 Apr 2018 16:40:33 +0000 (18:40 +0200)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Wed, 18 Apr 2018 20:20:57 +0000 (22:20 +0200)
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>
mcp/config/labs/local/idf-virtual1.yaml
mcp/reclass/classes/cluster/mcp-pike-ovs-dpdk-ha/openstack/init.yml
mcp/reclass/classes/cluster/mcp-pike-ovs-dpdk-noha/openstack/control.yml
mcp/scripts/pharos

index 35dab9b..79a5fa0 100644 (file)
@@ -36,7 +36,7 @@ idf:
       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:
index 55fc6ab..1f8ff4b 100644 (file)
@@ -11,4 +11,4 @@ classes:
 parameters:
   _param:
     neutron_tenant_network_types: "flat,vlan"
-    neutron_tenant_vlan_range: "1000:1030"
+    neutron_tenant_vlan_range: ${_param:opnfv_net_tenant_vlan}
index 61baf21..4be308d 100644 (file)
@@ -14,4 +14,4 @@ parameters:
   neutron:
     server:
       backend:
-        tenant_vlan_range: 1000:1999
+        tenant_vlan_range: ${_param:opnfv_net_tenant_vlan}
index a3c0456..c703450 160000 (submodule)
@@ -1 +1 @@
-Subproject commit a3c0456cc14a75e96808505e670d0cab37b30abc
+Subproject commit c7034503e2bb8da20f2b5c678719c7c7fbe6e61f