x/vmware-nsx
Code Issues Proposed changes

Update help message of flag 'enable_isolated_metadata'

Browse Source 
Thanks to the commit c73b54e50b,
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
This commit is contained in:
Édouard Thuleau 2014-01-16 10:15:07 +01:00
parent 59329d90b7
commit a9a7f62df5
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
etc/dhcp_agent.ini
View File

@ -36,9 +36,9 @@
# The DHCP server can assist with providing metadata support on isolated # The DHCP server can assist with providing metadata support on isolated
# networks. Setting this value to True will cause the DHCP server to append # 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 # 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 activated when the subnet does not contain any router port. The guest
# be configured to request host routes via DHCP (Option 121). # instance must be configured to request host routes via DHCP (Option 121).
# enable_isolated_metadata = False # enable_isolated_metadata = False
# Allows for serving metadata requests coming from a dedicated metadata # Allows for serving metadata requests coming from a dedicated metadata