From 71e6d415218ba10930752a0e241d670c6d5a8127 Mon Sep 17 00:00:00 2001 From: Dan Radez Date: Thu, 20 Oct 2016 20:28:57 +0000 Subject: Revert "Add ability to configure allowed vlan ranges in deploy configuration" This reverts commit 3228f00248cda32671fb0e6a02059bea6ae66c99. There is more settings that will need to added for the functionality this patch it intending to add. The JIRA will be updated and the feature will be worked on for Danube. Change-Id: I258ba552cbb49e6fa188a8dffe860e8dac2e3f5f Signed-off-by: Dan Radez --- config/network/network_settings.yaml | 1 - 1 file changed, 1 deletion(-) (limited to 'config') diff --git a/config/network/network_settings.yaml b/config/network/network_settings.yaml index ee5537d9..ab9ed962 100644 --- a/config/network/network_settings.yaml +++ b/config/network/network_settings.yaml @@ -89,7 +89,6 @@ networks: # Network configurations mtu: 64000 # Tenant network MTU overlay_id_range: 2,65535 # Tenant network Overlay segmentation ID range: # VNI, VLAN-ID, etc. - vlan_id_range: 1,1000 # Tenant physical network VLAN-ID range segmentation_type: vxlan # Tenant network segmentation type: # vlan, vxlan, gre nic_mapping: # Mapping of network configuration for Overcloud Nodes -- cgit 1.2.3-korg