Advertisement
Guest User

Untitled

a guest
Dec 22nd, 2015
69
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.57 KB | None | 0 0
  1. [DEFAULT]
  2. # Show debugging output in log (sets DEBUG log level output)
  3. # debug = False
  4. verbose = True
  5.  
  6. # The DHCP agent will resync its state with Neutron to recover from any
  7. # transient notification or rpc errors. The interval is number of
  8. # seconds between attempts.
  9. # resync_interval = 5
  10.  
  11. # The DHCP agent requires an interface driver be set. Choose the one that best
  12. # matches your plugin.
  13. interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver
  14.  
  15. # Example of interface_driver option for OVS based plugins(OVS, Ryu, NEC, NVP,
  16. # BigSwitch/Floodlight)
  17. # interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
  18.  
  19. # Name of Open vSwitch bridge to use
  20. # ovs_integration_bridge = br-int
  21.  
  22. # Use veth for an OVS interface or not.
  23. # Support kernels with limited namespace support
  24. # (e.g. RHEL 6.5) so long as ovs_use_veth is set to True.
  25. # ovs_use_veth = False
  26.  
  27. # Example of interface_driver option for LinuxBridge
  28. # interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver
  29.  
  30. # The agent can use other DHCP drivers. Dnsmasq is the simplest and requires
  31. # no additional setup of the DHCP server.
  32. dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq
  33.  
  34. # Allow overlapping IP (Must have kernel build with CONFIG_NET_NS=y and
  35. # iproute2 package that supports namespaces). This option is deprecated and
  36. # will be removed in a future release, at which point the old behavior of
  37. # use_namespaces = True will be enforced.
  38. # use_namespaces = True
  39.  
  40. # In some cases the neutron router is not present to provide the metadata
  41. # IP but the DHCP server can be used to provide this info. Setting this
  42. # value will force the DHCP server to append specific host routes to the
  43. # DHCP request. If this option is set, then the metadata service will be
  44. # activated for all the networks.
  45. # force_metadata = False
  46.  
  47. # The DHCP server can assist with providing metadata support on isolated
  48. # networks. Setting this value to True will cause the DHCP server to append
  49. # specific host routes to the DHCP request. The metadata service will only
  50. # be activated when the subnet does not contain any router port. The guest
  51. # instance must be configured to request host routes via DHCP (Option 121).
  52. # This option doesn't have any effect when force_metadata is set to True.
  53. enable_isolated_metadata = True
  54.  
  55. # Allows for serving metadata requests coming from a dedicated metadata
  56. # access network whose cidr is 169.254.169.254/16 (or larger prefix), and
  57. # is connected to a Neutron router from which the VMs send metadata
  58. # request. In this case DHCP Option 121 will not be injected in VMs, as
  59. # they will be able to reach 169.254.169.254 through a router.
  60. # This option requires enable_isolated_metadata = True
  61. # enable_metadata_network = False
  62.  
  63. # Number of threads to use during sync process. Should not exceed connection
  64. # pool size configured on server.
  65. # num_sync_threads = 4
  66.  
  67. # Location to store DHCP server config files
  68. # dhcp_confs = $state_path/dhcp
  69.  
  70. # Domain to use for building the hostnames. This option will be deprecated in
  71. # a future release. It is being replaced by dns_domain in neutron.conf
  72. # dhcp_domain = openstacklocal
  73.  
  74. # Override the default dnsmasq settings with this file
  75. dnsmasq_config_file = /etc/neutron/dnsmasq-neutron.conf
  76.  
  77. # Comma-separated list of DNS servers which will be used by dnsmasq
  78. # as forwarders.
  79. # dnsmasq_dns_servers =
  80.  
  81. # Base log dir for dnsmasq logging. The log contains DHCP and DNS log
  82. # information and is useful for debugging issues with either DHCP or DNS.
  83. # If this section is null, disable dnsmasq log.
  84. # dnsmasq_base_log_dir =
  85.  
  86. # Limit number of leases to prevent a denial-of-service.
  87. # dnsmasq_lease_max = 16777216
  88.  
  89. # Location to DHCP lease relay UNIX domain socket
  90. # dhcp_lease_relay_socket = $state_path/dhcp/lease_relay
  91.  
  92. # Use broadcast in DHCP replies
  93. # dhcp_broadcast_reply = False
  94.  
  95. # dhcp_delete_namespaces, which is True by default, can be set to False if
  96. # namespaces can't be deleted cleanly on the host running the DHCP agent.
  97. # Disable this if you hit the issue in
  98. # https://bugs.launchpad.net/neutron/+bug/1052535 or if
  99. # you are sure that your version of iproute suffers from the problem.
  100. # This should not be a problem any more. Refer to bug:
  101. # https://bugs.launchpad.net/neutron/+bug/1418079
  102. # This option is deprecated and will be removed in the M release
  103. # dhcp_delete_namespaces = True
  104.  
  105. # Timeout for ovs-vsctl commands.
  106. # If the timeout expires, ovs commands will fail with ALARMCLOCK error.
  107. # ovs_vsctl_timeout = 10
  108.  
  109. [AGENT]
  110. # Log agent heartbeats from this DHCP agent
  111. # log_agent_heartbeats = False
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement