init() method for benchmark scenario classes
One of the core system parts which is still partly implemented is the support of the init() methods defined in benchmark scenario classes, which should be launched by the scenario runner before the actual benchmark scenarios. init()'s can be used to allocate some resources needed for benchmarking, e.g. prepared servers or floating IPs.
2 main problems to fix in scope of this blueprint are the following:
1) Passing the context (which stores the links to resources created in init()) to a benchmark scenario which is run in a multiprocessing pool;
2) Creating the resources in such a way that they can be further used from benchmark scenarios (the problem is that different temporary users are used in different benchmark scenario runs)
Blueprint information
- Status:
- Complete
- Approver:
- Boris Pavlovic
- Priority:
- Undefined
- Drafter:
- Mikhail Dubov
- Direction:
- Needs approval
- Assignee:
- Mikhail Dubov
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Boris Pavlovic
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Fix passing the context to multiprocessing pool
Gerrit topic: https:/
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Perform init() for each temporary user
Addressed by: https:/
Make openstack clients for temp users lazy