| 2023-07-05 07:52:12 |
Yusuf Güngör |
description |
Hi, according to documentation for using Neutron Packet Logging the firewall driver must be set as openvswitch in openvswitch_agent.ini. This is tested by us and it is correct.
[security_group]
firewall_driver = openvswitch
https://docs.openstack.org/kolla-ansible/2023.1/reference/networking/neutron-extensions.html#neutron-logging-framework
kolla-ansible enable_neutron_packet_logging does not consider this change and firewall_driver is hard coded as "neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewall" in ./roles/neutron/templates/openvswitch_agent.ini.j2 for kolla-ansible xena, yoga and zed releases.
[securitygroup]
firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver |
Hi, according to documentation for using Neutron Packet Logging the firewall driver must be set as openvswitch in openvswitch_agent.ini. This is tested by us and it is correct.
[security_group]
firewall_driver = openvswitch
https://docs.openstack.org/kolla-ansible/2023.1/reference/networking/neutron-extensions.html#neutron-logging-framework
kolla-ansible enable_neutron_packet_logging does not consider this change and firewall_driver is hard coded as "neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewall" in ./roles/neutron/templates/openvswitch_agent.ini.j2 for kolla-ansible xena, yoga and zed releases.
[securitygroup]
firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
Doc states the it should be overridden manually, why it is not overridden default by the value of enable_neutron_packet_logging variable? |
|
