Class-based scenarios as alternative to existent method-based implementation

Registered by Alexander Maretskiy on 2016-03-22

Since current scenario implementation transforms method to class at runtime, it is reasonable to have class-based scenario implementation which will be much simpler to use behind the scenes.

This class should be based on Scenario and do not break compatibility.
The only required method is run() which is actually a body of scenario.

Blueprint information

Status:
Started
Approver:
Boris Pavlovic
Priority:
Undefined
Drafter:
Alexander Maretskiy
Direction:
Needs approval
Assignee:
Staroverov Anton
Definition:
New
Series goal:
None
Implementation:
Good progress
Milestone target:
None
Started by
Alexander Maretskiy

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/inroduce-class-based-scenario-implementation,n,z

Addressed by: https://review.openstack.org/295827
    [Spec] Introduce class-based scenario implementation

https://review.openstack.org/#/c/322825/

https://review.openstack.org/#/c/322829/

Gerrit topic: https://review.openstack.org/#q,topic:astarove-manila,n,z

Addressed by: https://review.openstack.org/359236
    Moving set of scenarios into separate classes

Gerrit topic: https://review.openstack.org/#q,topic:astarove-neutron,n,z

Addressed by: https://review.openstack.org/360295
    Moving of Neutrone scenarios into separate classes

Gerrit topic: https://review.openstack.org/#q,topic:astarove-sahara,n,z

Addressed by: https://review.openstack.org/364777
    Port all Sahara scenarios to new style

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

Addressed by: https://review.openstack.org/370195
    Update of docstrings to support common-style scenarios

Gerrit topic: https://review.openstack.org/#q,topic:astarove-volumes,n,z

Addressed by: https://review.openstack.org/357255
    Moving of Volumes scenarios into separate classes

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.