Describe available test resources in a YAML file

Registered by Andrea Frittoli on 2015-04-14

Tempest configuration contains a mixture of flags that defined how tempest should behave, and ids and names pointing to test resources to be used.
This has several drawbacks: (1) configuring tempest requires a running cloud as we use IDs of test resources (2) using different resources in different tests requires a proliferation of configuration options (3) configuration file is huge and difficult to handle

We shall move all test resources to a dedicated YAML file, and thus allow for:
- tempest configuration to happen with the same amount of configuration a deployer system uses to configure the OpenStack services
- tests can select resources to be used by logical name or properties (e.g. use whatever image that would fit in "smallest" flavor), or run against all combinations of certain resources (via testscenarios).
Provide a tool to generate such YAML file

Blueprint information

Status:
Started
Approver:
Andrea Frittoli
Priority:
High
Drafter:
Andrea Frittoli
Direction:
Needs approval
Assignee:
Ken'ichi Ohmichi
Definition:
Approved
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Andrea Frittoli on 2016-02-24

Related branches

Sprints

Whiteboard

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

Addressed by: https://review.openstack.org/173334
    Add bp tempest-resources

Addressed by: https://review.openstack.org/283769
    Add Resources Configuration class

Addressed by: https://review.openstack.org/283775
    Create resources configuration group

Addressed by: https://review.openstack.org/284365
    Tie in resource configuration

Addressed by: https://review.openstack.org/286342
    Adds the ResourceProvider class

Addressed by: https://review.openstack.org/286359
    DO NOT MERGE: WIP - ResourceTracker

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.