I'm going to close this for a couple of reasons. 1) It doesn't seem like this is specific to neutron, so it's not the correct place to make such a change.
2) The neutron code has no concept of a particular person, everything is just a project ID, which isn't an identifiable piece of information without another mapping, for example, from Keystone. 3) At the end of the day, an operation such as filtering IP addresses from logs seems like something for an operator, and something they would have to do for a lot more than just this. If there is a clearer document on what should be done here please update this bug with more information. ** Changed in: neutron Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1771493 Title: Add option to hide ipaddress in neutron logs Status in neutron: Won't Fix Bug description: As some might know, EU has released a new law, that gets in action on May25th 2018, that prohibits misuse of any personal data corresponding to a natural person. Any information that can directly or indirectly lead to tracking of a natural person can be captured, stored or processed only with the consent of the natural person. IP Address is categorized as one such data. It can be debated if ipaddress can be classified as personal data or not but that would be beyond the scope of this defect. The below log statements from neutron log displays the fixed ips associated with the VMs provisioned. The VMs provisioned from an Cloud platform like OpenStack could host someone's website and thus could be used to identify a natural person. Having said that, this information(logged ip) could be very useful from a serviceability perspective. So, the question is is it possible to add a mechanism such that we are able to configure whether this information should be logged or not? 2018-05-10 03:50:01.157 18683 INFO neutron.wsgi [req-b7b52f32-bbde-41b2-b882-707d63729256 a1e569eb16f0ec710b82314e31af4f8cfb1eedc3f0fb38554186e08717c21f0c 676da0962c9e48c687312f1a023af9ca - 96c9c4469e0b499e8c14043aa093b5bd 96c9c4469e0b499e8c14043aa093b5bd] 10.253.234.23,127.0.0.1 "GET /v2.0/floatingips?fixed_ip_address=162.42.34.10&port_id=41a1dff7-d5f5-43eb-a911-a594c4576f6a HTTP/1.1" status: 200 len: 217 time: 0.0247259 2018-05-10 03:50:02.049 18683 INFO neutron.wsgi [req-879d19ac-7b6f-4af0-b8b0-48d259f20ae7 a1e569eb16f0ec710b82314e31af4f8cfb1eedc3f0fb38554186e08717c21f0c 676da0962c9e48c687312f1a023af9ca - 96c9c4469e0b499e8c14043aa093b5bd 96c9c4469e0b499e8c14043aa093b5bd] 10.253.234.23,127.0.0.1 "GET /v2.0/floatingips?fixed_ip_address=162.42.34.10&port_id=41a1dff7-d5f5-43eb-a911-a594c4576f6a HTTP/1.1" status: 200 len: 217 time: 0.0201731 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1771493/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp