Simple Tenant Usage Pagination Support
The simple tenant usage API can return extremely large amounts of data and provides no way to paginate the results. Because the API does not use the pagination code, it doesn't even respect the "max results" sanity limit. Because it can query a ton of data, it also causes the api workers to inflate their memory footprint to the size of the DB result set, which is large. Since horizon queries this by default, most users are affected unless their ops team is extremely diligent about purging deleted instances (which are returned by the API by design).
Blueprint information
- Status:
- Complete
- Approver:
- Dan Smith
- Priority:
- Medium
- Drafter:
- Dan Smith
- Direction:
- Approved
- Assignee:
- Diana Clarke
- Definition:
- Approved
- Series goal:
- Accepted for ocata
- Implementation:
- Implemented
- Milestone target:
- ocata-3
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Bug #1383469: InstanceList.get_active_by_window_joined only needs system_metadata for expected_attrs in simple-tenant-usage API | Fix Released |
Sprints
Whiteboard
Let's queue this up for Ocata since it's a performance issue once you have a lot of instances/tenants. -- mriedem 20160701
I'm working on this --diana 2016-Oct-3
Gerrit topic: https:/
Addressed by: https:/
Simple tenant usage pagination
Addressed by: https:/
Simple tenant usage pagination
Addressed by: https:/
api-ref: microversion 2.40 overview