Minimize agent state reports handling on server side
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Expired
|
Wishlist
|
Unassigned | ||
Bug Description
Agent state reports are mostly needed in order for neutron server to properly (re)schedule resources among agents.
New features may require more precise scheduling which in turn requires agents to report more and servers to handle more data.
However adding new logic to agent state reports handling has negative effect on scalability and overall neutron server performance. Here is one of examples: https:/
One of the things that could be done is to not include (or just to ignore on server side) the data which can't be changed during runtime (like config parameters) in each state report. Such data should only be processed on agent (re)start/revival.
So mainly it's about separating static and dynamic data in state reports handling to reduce the amount of db updates.
| Changed in neutron: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| summary: |
- Minimize agent state reports handling on server side + [rfe] Minimize agent state reports handling on server side |
| tags: | added: rfe |
| Armando Migliaccio (armando-migliaccio) wrote Re: [rfe] Minimize agent state reports handling on server side | #1 |
| Changed in neutron: | |
| status: | Confirmed → Triaged |
| Armando Migliaccio (armando-migliaccio) wrote | #2 |
| tags: | removed: rfe |
| summary: |
- [rfe] Minimize agent state reports handling on server side + Minimize agent state reports handling on server side |
| Armando Migliaccio (armando-migliaccio) wrote | #3 |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to neutron (master) | #4 |
| Changed in neutron: | |
| status: | Triaged → In Progress |
| OpenStack Infra (hudson-openstack) wrote Change abandoned on neutron (master) | #5 |
| OpenStack Infra (hudson-openstack) wrote | #6 |
| Changed in neutron: | |
| status: | In Progress → Incomplete |
| assignee: | Oleg Bondarev (obondarev) → nobody |
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in neutron: | |
| status: | Incomplete → Expired |
If the goal is simply to reduce the payload of the periodic status report, I would be interested in seeing how you intend to break this down and make sure that no further changes break that pattern. This raises the interesting question on bw compatibility, but maybe not. Having said, I wonder if this can be tackled in the context of [1]. Thoughts?
[1] https:/