Actually I'm not sure that caching the mapping would be safe in all cases. The period would have to be so short to avoid the risk of the port and address being re-assigned that it probably doesn't by that much
** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1235351 Title: Metadata proxy queries the DB for each request Status in OpenStack Neutron (virtual network service): Invalid Bug description: The metadata agent has add add the Nova instance_id (i.e port device_id) to the query headers, which it does via a DB lookup. However its normal for a Nova VM to make a number of metadata queries in quick succession, esp during its start-up as cloud-init makes a separate request for each metadata item. The network->port->device_id mapping is very stable over a short period of time, so this data could be cached to improve performance To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1235351/+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