Advertisement
Guest User

network-l3_agent.ini

a guest
Mar 16th, 2015
319
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.10 KB | None | 0 0
  1. [DEFAULT]
  2. # Show debugging output in log (sets DEBUG log level output)
  3. debug = TRUE
  4.  
  5. # L3 requires that an interface driver be set. Choose the one that best
  6. # matches your plugin.
  7. # interface_driver =
  8.  
  9. # Example of interface_driver option for OVS based plugins (OVS, Ryu, NEC)
  10. # that supports L3 agent
  11. interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
  12.  
  13. # Use veth for an OVS interface or not.
  14. # Support kernels with limited namespace support
  15. # (e.g. RHEL 6.5) so long as ovs_use_veth is set to True.
  16. # ovs_use_veth = False
  17.  
  18. # Example of interface_driver option for LinuxBridge
  19. # interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver
  20.  
  21. # Allow overlapping IP (Must have kernel build with CONFIG_NET_NS=y and
  22. # iproute2 package that supports namespaces).
  23. use_namespaces = TRUE
  24.  
  25. # If use_namespaces is set as False then the agent can only configure one router.
  26.  
  27. # This is done by setting the specific router_id.
  28. # router_id =
  29.  
  30. # When external_network_bridge is set, each L3 agent can be associated
  31. # with no more than one external network. This value should be set to the UUID
  32. # of that external network. To allow L3 agent support multiple external
  33. # networks, both the external_network_bridge and gateway_external_network_id
  34. # must be left empty.
  35. # gateway_external_network_id =
  36.  
  37. # Indicates that this L3 agent should also handle routers that do not have
  38. # an external network gateway configured. This option should be True only
  39. # for a single agent in a Neutron deployment, and may be False for all agents
  40. # if all routers must have an external network gateway
  41. # handle_internal_only_routers = True
  42.  
  43. # Name of bridge used for external network traffic. This should be set to
  44. # empty value for the linux bridge. when this parameter is set, each L3 agent
  45. # can be associated with no more than one external network.
  46. external_network_bridge =
  47.  
  48. # TCP Port used by Neutron metadata server
  49. # metadata_port = 9697
  50.  
  51. # Send this many gratuitous ARPs for HA setup. Set it below or equal to 0
  52. # to disable this feature.
  53. # send_arp_for_ha = 0
  54.  
  55. # seconds between re-sync routers' data if needed
  56. # periodic_interval = 40
  57.  
  58. # seconds to start to sync routers' data after
  59. # starting agent
  60. # periodic_fuzzy_delay = 5
  61.  
  62. # enable_metadata_proxy, which is true by default, can be set to False
  63. # if the Nova metadata server is not available
  64. # enable_metadata_proxy = True
  65.  
  66. # Location of Metadata Proxy UNIX domain socket
  67. # metadata_proxy_socket = $state_path/metadata_proxy
  68.  
  69. # router_delete_namespaces, which is false by default, can be set to True if
  70. # namespaces can be deleted cleanly on the host running the L3 agent.
  71. # Do not enable this until you understand the problem with the Linux iproute
  72. # utility mentioned in https://bugs.launchpad.net/neutron/+bug/1052535 and
  73. # you are sure that your version of iproute does not suffer from the problem.
  74. # If True, namespaces will be deleted when a router is destroyed.
  75. # router_delete_namespaces = False
  76.  
  77. # Timeout for ovs-vsctl commands.
  78. # If the timeout expires, ovs commands will fail with ALARMCLOCK error.
  79. # ovs_vsctl_timeout = 10
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement