"--target" parameter in "network log object create" is only expected for ML2/OVS

Bug #2026264 reported by Elvira García Ruiz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
New
Medium
Elvira García Ruiz

Bug Description

According to command help [1], option "--target" when creating security group log should work to narrow down logging action for specific port.

However, this is something not expected in the ML2/OVN driver, where the minimal unit of logging is per security group, and is selected using --resource.

I raised this on the last Neutron meeting to see if it was possible to have a general solution for this that could be useful for any parameter and any driver (Like answering with an error through the API) but this would result on a driver-driven API which is something discouraged.

There was also the option of logging a Warning or an error when using non-supported parameters, but I don't know if this would give hints to the users about which driver they are using, something we also don't want non-admin users to know.

Finally, there is the option to fix this specific problem by changing the --help for network log create.

[1]
"""
$ openstack network log create --help
usage: openstack network log create ...

Create a new network log

positional arguments:
  <name> Name for the network log

optional arguments:
...
  --resource <resource>
                        Name or ID of resource (security group or firewall
                        group) that used for logging. You can control for
                        logging target combination with --target option.
  --target <target> Port (name or ID) for logging. You can control for
                        logging target combination with --resource option.
...
"""

Changed in neutron:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.