init() method for benchmark scenario classes

Registered by Mikhail Dubov

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
Completed by
Boris Pavlovic

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/test-engine-init,n,z

Addressed by: https://review.openstack.org/55465
    Fix passing the context to multiprocessing pool

Gerrit topic: https://review.openstack.org/#q,topic:bp/flexible-benchmark-config,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bp/benchmark_scenarios,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bp/benchmark-scenarios,n,z

Addressed by: https://review.openstack.org/59782
    Perform init() for each temporary user

Addressed by: https://review.openstack.org/59781
    Make openstack clients for temp users lazy

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.