)]}'
{"doc/config-reference/source/tables/neutron-common.rst":[{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"c7ed4b8e1119eed6f8cd891d2655617b94800716","unresolved":false,"context_lines":[{"line_number":67,"context_line":"   * - ``external_dns_driver`` \u003d ``None``"},{"line_number":68,"context_line":"     - (String) Driver for external DNS integration."},{"line_number":69,"context_line":"   * - ``global_physnet_mtu`` \u003d ``1500``"},{"line_number":70,"context_line":"     - (Integer) MTU of the underlying physical network. Neutron uses this value to calculate MTU for all virtual network components. For flat and VLAN networks, neutron uses this value without modification. For overlay networks such as VXLAN, neutron automatically subtracts the overlay protocol overhead from this value. Defaults to 1500, the standard value for Ethernet. Also consider setting the path_mtu ml2 configuration value to the global_physnet_mtu value when using the ml2 plug-in. Otherwise the global_physnet_mtu value might get overridden by a smaller path_mtu value and hence have no effect on overlay/tunnel networks but only flat and VLAN networks."},{"line_number":71,"context_line":"   * - ``ip_lib_force_root`` \u003d ``False``"},{"line_number":72,"context_line":"     - (Boolean) Force ip_lib calls to use the root helper"},{"line_number":73,"context_line":"   * - ``ipam_driver`` \u003d ``None``"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_36b2e74c","line":70,"updated":"2016-06-07 22:01:37.000000000","message":"Suggestion:\n\nIf using the ML2 plug-in with overlay/tunnel networks, also configure the path_mtu option with the same value as the global_physnet_mtu option.","commit_id":"9667a24deb6c0831dd216f08d7355e6a8e5bb2c0"}],"doc/config-reference/source/tables/neutron-ml2.rst":[{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"c7ed4b8e1119eed6f8cd891d2655617b94800716","unresolved":false,"context_lines":[{"line_number":25,"context_line":"   * - ``mechanism_drivers`` \u003d"},{"line_number":26,"context_line":"     - (List) An ordered list of networking mechanism driver entrypoints to be loaded from the neutron.ml2.mechanism_drivers namespace."},{"line_number":27,"context_line":"   * - ``path_mtu`` \u003d ``1500``"},{"line_number":28,"context_line":"     - (Integer) Maximum size of an IP packet (MTU) that can traverse the underlying physical network infrastructure without fragmentation when using an overlay/tunnel protocol. Either set this to the same value as the global_physnet_mtu value or use it to explicitly specify a physical network MTU value that differs from the default global_physnet_mtu value."},{"line_number":29,"context_line":"   * - ``physical_network_mtus`` \u003d"},{"line_number":30,"context_line":"     - (List) A list of mappings of physical networks to MTU values. The format of the mapping is \u003cphysnet\u003e:\u003cmtu val\u003e. This mapping allows specifying a physical network MTU value that differs from the default global_physnet_mtu value."},{"line_number":31,"context_line":"   * - ``tenant_network_types`` \u003d ``local``"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_164b6b2b","line":28,"updated":"2016-06-07 22:01:37.000000000","message":"Suggestion:\n\n... fragmentation for overlay/tunnel networks. In most cases, use the same value as the global_physnet_mtu option.","commit_id":"9667a24deb6c0831dd216f08d7355e6a8e5bb2c0"}]}