The following Neutron agents:
- neutron-metadata
- neutron-dhcp-agent
- neutron-l3-agent
- neutron-lbaasv2-agent
- neutron-vpn-agent
doesn't require ml2_conf.ini file.
ml2_conf.ini file is used to managed L2 network configuration.
This config doesn't have to be in DHCP, L3, metadata agents...
We should remove it to avoid restarting these agents in case of
ml2_conf.ini file modification.
Only neutron-server, neutron-openvswitch-agent,
neutron-linuxbridge-agent must be restarted.
Closes-Bug: #1677163
Change-Id: I0876b8a3845d1c2bccd996426a65df1a3a6f7085
(cherry picked from commit 5fe11a8fcb302dfd3d52819136a8644921ee1ddc)
Reviewed: https:/ /review. openstack. org/477218 /git.openstack. org/cgit/ openstack/ kolla-ansible/ commit/ ?id=e82c5090c61 14297cd8ea722b1 57e17ad335f365
Committed: https:/
Submitter: Jenkins
Branch: stable/ocata
commit e82c5090c611429 7cd8ea722b157e1 7ad335f365
Author: Bertrand Lallau <email address hidden>
Date: Tue Mar 21 11:00:11 2017 +0100
Fix neutron agents restarted on ml2 config change
The following Neutron agents: lbaasv2- agent
- neutron-metadata
- neutron-dhcp-agent
- neutron-l3-agent
- neutron-
- neutron-vpn-agent
doesn't require ml2_conf.ini file.
ml2_conf.ini file is used to managed L2 network configuration.
This config doesn't have to be in DHCP, L3, metadata agents...
We should remove it to avoid restarting these agents in case of openvswitch- agent, linuxbridge- agent must be restarted.
ml2_conf.ini file modification.
Only neutron-server, neutron-
neutron-
Closes-Bug: #1677163 2bccd996426a65d f1a3a6f7085 d3d52819136a864 4921ee1ddc)
Change-Id: I0876b8a3845d1c
(cherry picked from commit 5fe11a8fcb302df