Description of problem: In ml2/OVN security group logging feature there is no option to specify a logfile. All the logs will be written to the /var/log/containers/stdouts/ovn_controller.log file (in containerized deployment). There is such an option in ml2/OVS. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This is not a feature for core OVN to implement. The log format is not standard anyway between networking drivers. I believe if we want to store the logs in a separate file, there should be a separate component (container?) that would process the ovn log file and filter out the messages that belong to SG logging. We discussed this matter with Daniel and we don't believe it's high priority. I'm lowering the priority here to reflect that.
This bug won't be solved in python-networking-ovn / neutron / OVN. The option to choose log file location is driver specific in neutron, and OVN logs hits with standard OS mechanisms (syslog). If we are interested in driver agnostic way to extract SG logging messages, we'll need to add a new component to do that (perhaps also normalizing the messages to some defined format). This bug should be reconsidered / moved to tripleo (?), if at all. Resetting the assignee / removing Triaged flag to repeat prioritization.
Note that the file logging is a config option specific for OVS driver and is not backend agnostic nor part of the API - https://github.com/openstack/neutron/blob/master/neutron/services/logapi/drivers/openvswitch/ovs_firewall_log.py#L49 imho this is not a parity bug
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days