Implement pluggable functionality to tempest

Registered by Valeriy Ponomaryov on 2013-12-16

Current realization of tempest hasn't pluggable functionality.

Proposal:
make tempest to look for extended files for:

1) config extension
2) exceptions extension
3) clients extensions

As result:
Much less merge conflicts.
For any purposes of new project can be cloned vanilla tempest and added new files to specific dirs,
tempest will read these files and dynamically add everything that is needed to new project.

Plug-ins for these purposes can be placed into 'contrib' dir of service-project files and then easy merge to tempest without any conflicts, only new files copied.

Blueprint information

Status:
Complete
Approver:
Sean Dague
Priority:
Undefined
Drafter:
Valeriy Ponomaryov
Direction:
Approved
Assignee:
Valeriy Ponomaryov
Definition:
Review
Series goal:
Proposed for icehouse
Implementation:
Implemented
Milestone target:
None
Started by
Valeriy Ponomaryov on 2013-12-16
Completed by
Valeriy Ponomaryov on 2016-03-18

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/make-tempest-pluggable,n,z

Addressed by: https://review.openstack.org/62429
    Implement pluggability for tempest (exceptions)

Addressed by: https://review.openstack.org/69983
    Implement pluggability for tempest (clients)

Addressed by: https://review.openstack.org/69985
    Implement pluggability for tempest (config)

Gerrit topic: https://review.openstack.org/#q,topic:bp/make-tempest-pluggable,n,z

Addressed by: https://review.openstack.org/89322
    Spec for making tempest pluggable

(?)

Work Items

Work items:
1) Make exceptions pluggable: DONE
2) Make config pluggable: DONE
3) Make clients pluggable: DONE

This blueprint contains Public information 
Everyone can see this information.