From 6baecfa2ffb831c04fb9c94d09a9ccd8f9f2ade4 Mon Sep 17 00:00:00 2001 From: Michal Nasiadka Date: Wed, 16 Nov 2022 19:04:07 +0000 Subject: Run ML2/OVS agents processes in separate containers It's an experimental feature, disabled by default (but enabled by default in our CI). It's based on TripleO ,,version'' that was their fix for the linked bug. Closes-Bug: #1891469 Depends-On: https://review.opendev.org/c/openstack/kolla/+/946215 Change-Id: Iaa1e687152db8351bc0e9b10e66f412860ac13a5 --- doc/source/reference/networking/neutron.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'doc/source') diff --git a/doc/source/reference/networking/neutron.rst b/doc/source/reference/networking/neutron.rst index fab86ce73..2a772e5eb 100644 --- a/doc/source/reference/networking/neutron.rst +++ b/doc/source/reference/networking/neutron.rst @@ -335,3 +335,18 @@ In this example: - `neutron_modules_extra`: Allows users to specify additional modules and their associated parameters. The given configuration adjusts the `hashsize` parameter for the `nf_conntrack_tftp` module. + +Running Neutron agents subprocesses in separate containers +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +There is an experimental feature in Kolla-Ansible that allows to overcome +the issue of breaking data plane connectivity and dhcp services when +restarting neutron-l3-agent and neutron-dhcp-agent. + +To enable it, modify the configuration in ``/etc/kolla/globals.yml``: + +.. code-block:: yaml + + neutron_agents_wrappers: "yes" + +For additional details see `bug 1891469 `_ -- cgit v1.2.3