dhcp_agent.ini revision 2521
80833bb9a1bf25dcf19e814438a4b311d2e1f4cffuankg# Show debugging output in log (sets DEBUG log level output)
6736c640e65e06990ef33af71ee81fac4df4ff5fjim# debug = true
254eb3394b0e47e7e5d25e49bbea74ccc652f645trawick# The DHCP agent will resync its state with Quantum to recover from any
254eb3394b0e47e7e5d25e49bbea74ccc652f645trawick# transient notification or rpc errors. The interval is number of
254eb3394b0e47e7e5d25e49bbea74ccc652f645trawick# seconds between attempts.
70caa242e6b90e0d6f0fabb56b8c5c2fb51717b3jorton# resync_interval = 5
70caa242e6b90e0d6f0fabb56b8c5c2fb51717b3jorton# The DHCP requires that an inteface driver be set. Choose the one that best
70caa242e6b90e0d6f0fabb56b8c5c2fb51717b3jorton# matches you plugin.
109e2a09790de3fb315d36d6232a14ab66c8eb0ahumbedooh# Solaris Elastic Virtual Switch (EVS)
109e2a09790de3fb315d36d6232a14ab66c8eb0ahumbedoohinterface_driver = quantum.agent.solaris.interface.SolarisVNICDriver
4be250c774bdac977eef29a02183ca78de29fb41rjung# The agent can use other DHCP drivers. Dnsmasq is the simplest and requires
4be250c774bdac977eef29a02183ca78de29fb41rjung# no additional setup of the DHCP server.
12b5dc9afa1844df5ac8acab98fb538432a2fa1crjung# Allow overlapping IP (Must have kernel build with CONFIG_NET_NS=y and
12b5dc9afa1844df5ac8acab98fb538432a2fa1crjung# iproute2 package that supports namespaces).
74e7a30182af5e68f14ccb8d57918b22b982db8bhumbedoohuse_namespaces = False
74e7a30182af5e68f14ccb8d57918b22b982db8bhumbedooh# The DHCP server can assist with providing metadata support on isolated
10961a2f60207cb873d889bb28b1f0ef707a4311humbedooh# networks. Setting this value to True will cause the DHCP server to append
10961a2f60207cb873d889bb28b1f0ef707a4311humbedooh# specific host routes to the DHCP request. The metadata service will only
10961a2f60207cb873d889bb28b1f0ef707a4311humbedooh# be activated when the subnet gateway_ip is None. The guest instance must
0448378b899e8df0c060360f17c0af692adf17bchumbedooh# be configured to request host routes via DHCP (Option 121).
0448378b899e8df0c060360f17c0af692adf17bchumbedooh# enable_isolated_metadata = False
60a765cccbd3f3b5997b65b0034220c79f78369etrawick# Allows for serving metadata requests coming from a dedicated metadata
60a765cccbd3f3b5997b65b0034220c79f78369etrawick# access network whose cidr is 169.254.169.254/16 (or larger prefix), and
60a765cccbd3f3b5997b65b0034220c79f78369etrawick# is connected to a Quantum router from which the VMs send metadata
e7ca863b04ee2a7aea7738cadbf51ce5e6c5245dhumbedooh# request. In this case DHCP Option 121 will not be injected in VMs, as
e7ca863b04ee2a7aea7738cadbf51ce5e6c5245dhumbedooh# they will be able to reach 169.254.169.254 through a router.
e7ca863b04ee2a7aea7738cadbf51ce5e6c5245dhumbedooh# This option requires enable_isolated_metadata = True
e7ca863b04ee2a7aea7738cadbf51ce5e6c5245dhumbedooh# enable_metadata_network = False
91814c869ca39ce45dfe147307d2a831cac6ecbehumbedooh# DeviceManager provides methods to setup/destroy dhcp ports on the
91654e263480f0fdc2a03d782ff23f8dad07cf79humbedooh# host running DHCP agent
79c5787b92ac5f0e1cc82393816c77a006399316trawickdevicemanager = quantum.agent.solaris.device.DeviceManager
79c5787b92ac5f0e1cc82393816c77a006399316trawick# An URI that specifies an EVS controller. It is of the form
79c5787b92ac5f0e1cc82393816c77a006399316trawick# ssh://user@hostname, where user is the username to use to connect
79c5787b92ac5f0e1cc82393816c77a006399316trawick# to EVS controller specified by hostname. By default it's set to
79c5787b92ac5f0e1cc82393816c77a006399316trawick# ssh://evsuser@localhost.
79c5787b92ac5f0e1cc82393816c77a006399316trawick# evs_controller = ssh://evsuser@localhost