[RFE] Caching instance id in the metadata agent to have less RPC messages sent to server

Bug #2024581 reported by Slawek Kaplonski
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Committed
Wishlist
Unassigned

Bug Description

Problem like that was mentioned in Vancouvers's "Challenges & lessons from operating OpenStack at Scale" forum session (https://etherpad.opendev.org/p/challenges-largescale)
In some cases, neutron metadata agent may put a lot of load on the RPC bus and neutron server as every time VM is asking for some of the metadata, this agent needs to find out what the id of the instance is. Because of that it sends RPC message to get port details every time.
It could be potentially avoided by some simple caching of the instance id in the agent's side.

Revision history for this message
Sahid Orentino (sahid-ferdjaoui) wrote :

I may missing something but don't we want to just enable the cache using memcache for the metadata agent?

This should be added in metadata_agent.ini

[cache]
backend = oslo_cache.memcache_pool
enabled = True
memcache_servers = ...
expiration_time = 300
memcache_pool_maxsize = 20

We ran into such issue and this clearly fixed/improved the issue.

tags: added: rfe-approved
removed: rfe
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

This RFE was approved during the drivers meeting celebrated today [1]. No spec is required.

The developer will check first the proposal in c#1, using the oslo_cache library. Once tested, it will be documented in the Neutron repository.

Thanks for this proposal.

[1]https://meetings.opendev.org/meetings/neutron_drivers/2023/neutron_drivers.2023-06-30-14.00.log.html

Revision history for this message
Lajos Katona (lajos-katona) wrote :
Changed in neutron:
status: New → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 23.0.0.0b3

This issue was fixed in the openstack/neutron 23.0.0.0b3 development milestone.

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.