Reviewed: https://review.opendev.org/679667 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=791dc24960f2b5e7b4ebd7d27ec8b8a1e3924e8a Submitter: Zuul Branch: master
commit 791dc24960f2b5e7b4ebd7d27ec8b8a1e3924e8a Author: Rodolfo Alonso Hernandez <ralon...@redhat.com> Date: Mon Sep 2 15:46:10 2019 +0000 Log when FIP is associated/disassociated Add a log entry when a floating IP is associated/disassociated from a port, reporting the external IP, the internal IP, the fixed port ID and the FIP ID. The log level is set to INFO; this security information will be registered regardless of the logging level. Change-Id: I9124399f680e4123c4dc14e8be666f9c4c5385a0 Closes-Bug: #1842327 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1842327 Title: Report in logs when FIP associate and disassociate Status in neutron: Fix Released Bug description: Related bug: https://bugs.launchpad.net/neutron/+bug/1593793 A floating IP (FIP) can be used to provide external access to a VM, associating a private IP with an external IP (the FIP). At this point, the VM user can access to Internet using the provider network. Could be very important for the deployment administrator to have log records of when a FIP has been associated/disassociated from a fixed IP (and it's port ID), for legal purposes. This RFE proposes to insert log INFO messages in the Neutron server log to track those events, recording the FIP, the fixed IP associated and the port ID. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1842327/+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