aboutsummaryrefslogtreecommitdiffstats
path: root/deploy
diff options
context:
space:
mode:
authorhuangxiangyu <huangxiangyu5@huawei.com>2017-04-01 17:06:54 +0800
committerhuangxiangyu <huangxiangyu5@huawei.com>2017-04-01 17:06:54 +0800
commit1ea10ede18b4bacc2aca04fccb26c34976962ed7 (patch)
tree6fbfed2bb31e8c8f8ca777a8a3d9038b707ead45 /deploy
parent0523f8c84d0dd1530c725b08d881653f8522287f (diff)
Fix vlan network can't deploy instance
JIRA: COMPASS-533 Bug: When a vlan network is created and bind to a physical network, the instances launched on this network will fail to get ip address from openstack dhcp server. Solution: Set enable_isolated_metadata to True in dhcp_agent.in Change-Id: I97cf8684d1ec9beeaa30e0ffa290150046ebcab1 Signed-off-by: huangxiangyu <huangxiangyu5@huawei.com>
Diffstat (limited to 'deploy')
-rw-r--r--deploy/adapters/ansible/roles/neutron-compute/templates/dhcp_agent.ini2
-rw-r--r--deploy/adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini2
-rw-r--r--deploy/adapters/ansible/roles/neutron-network/templates/dhcp_agent.ini2
-rw-r--r--deploy/adapters/ansible/roles/nova-controller/templates/dhcp_agent.ini2
4 files changed, 4 insertions, 4 deletions
diff --git a/deploy/adapters/ansible/roles/neutron-compute/templates/dhcp_agent.ini b/deploy/adapters/ansible/roles/neutron-compute/templates/dhcp_agent.ini
index 19eb62ec..4340c39c 100644
--- a/deploy/adapters/ansible/roles/neutron-compute/templates/dhcp_agent.ini
+++ b/deploy/adapters/ansible/roles/neutron-compute/templates/dhcp_agent.ini
@@ -40,7 +40,7 @@ use_namespaces = True
# specific host routes to the DHCP request. The metadata service will only
# be activated when the subnet does not contain any router port. The guest
# instance must be configured to request host routes via DHCP (Option 121).
-enable_isolated_metadata = False
+enable_isolated_metadata = True
# Allows for serving metadata requests coming from a dedicated metadata
# access network whose cidr is 169.254.169.254/16 (or larger prefix), and
diff --git a/deploy/adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini b/deploy/adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini
index 19eb62ec..4340c39c 100644
--- a/deploy/adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini
+++ b/deploy/adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini
@@ -40,7 +40,7 @@ use_namespaces = True
# specific host routes to the DHCP request. The metadata service will only
# be activated when the subnet does not contain any router port. The guest
# instance must be configured to request host routes via DHCP (Option 121).
-enable_isolated_metadata = False
+enable_isolated_metadata = True
# Allows for serving metadata requests coming from a dedicated metadata
# access network whose cidr is 169.254.169.254/16 (or larger prefix), and
diff --git a/deploy/adapters/ansible/roles/neutron-network/templates/dhcp_agent.ini b/deploy/adapters/ansible/roles/neutron-network/templates/dhcp_agent.ini
index 19eb62ec..4340c39c 100644
--- a/deploy/adapters/ansible/roles/neutron-network/templates/dhcp_agent.ini
+++ b/deploy/adapters/ansible/roles/neutron-network/templates/dhcp_agent.ini
@@ -40,7 +40,7 @@ use_namespaces = True
# specific host routes to the DHCP request. The metadata service will only
# be activated when the subnet does not contain any router port. The guest
# instance must be configured to request host routes via DHCP (Option 121).
-enable_isolated_metadata = False
+enable_isolated_metadata = True
# Allows for serving metadata requests coming from a dedicated metadata
# access network whose cidr is 169.254.169.254/16 (or larger prefix), and
diff --git a/deploy/adapters/ansible/roles/nova-controller/templates/dhcp_agent.ini b/deploy/adapters/ansible/roles/nova-controller/templates/dhcp_agent.ini
index 19eb62ec..4340c39c 100644
--- a/deploy/adapters/ansible/roles/nova-controller/templates/dhcp_agent.ini
+++ b/deploy/adapters/ansible/roles/nova-controller/templates/dhcp_agent.ini
@@ -40,7 +40,7 @@ use_namespaces = True
# specific host routes to the DHCP request. The metadata service will only
# be activated when the subnet does not contain any router port. The guest
# instance must be configured to request host routes via DHCP (Option 121).
-enable_isolated_metadata = False
+enable_isolated_metadata = True
# Allows for serving metadata requests coming from a dedicated metadata
# access network whose cidr is 169.254.169.254/16 (or larger prefix), and