Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Status: New
--
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:
[RFE] Report in logs when FIP associate and disassociate
Status in neutron:
New
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
