From 964b9d80bb7b8c559f331d7ae66395845ec3f28c Mon Sep 17 00:00:00 2001 From: =?utf8?q?=C3=89douard=20Thuleau?= Date: Thu, 16 Jan 2014 10:15:07 +0100 Subject: [PATCH] Update help message of flag 'enable_isolated_metadata' Thanks to the commit c73b54e50b62c489f04432bdbc5bee678b18226e, the way of DHCP agent determines how a subnet is isolated evolves. But the flag help message wasn't updtated accordingly to this evolution. Change-Id: If07d8e0802524f9babdee0c8cc07d40cb0803afb Closes-bug: #1269722 --- etc/dhcp_agent.ini | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/etc/dhcp_agent.ini b/etc/dhcp_agent.ini index 583f136e6..9836d3500 100644 --- a/etc/dhcp_agent.ini +++ b/etc/dhcp_agent.ini @@ -36,9 +36,9 @@ # The DHCP server can assist with providing metadata support on isolated # networks. Setting this value to True will cause the DHCP server to append -# specific host routes to the DHCP request. The metadata service will only -# be activated when the subnet gateway_ip is None. The guest instance must -# be configured to request host routes via DHCP (Option 121). +# 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 # Allows for serving metadata requests coming from a dedicated metadata -- 2.45.2