Goals

The upstream gate for telemetry is hard to understand, running tests is quite opinionated, but differs a lot from what other OpenStack upstream projects do.

The other goal here is to add missing tests to  upstream (like including prometheus or sg-core coverage), or to remove dependencies to projects that are not really used anymore.

Requirements

A list of specific needs or objectives that a Epic must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the epic shifts.  If a non MVP requirement slips, it does not shift the epic.

(Optional) Use Cases

< How will the user interact with this epic? >

< Which users will use this and when will they use it? >

< Is this epic used as part of current user interface? >

Out of Scope

Updating gnocchi CI at the moment

Assumptions

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Interoperability Considerations

< Which other products and versions in our portfolio does this feature impact?>

< What interoperability test scenarios should be factored by the layered product(s)?>

• heat pulls f36
• test jobs pulls multiple projects, tests should be refactored and 
• make the test jobs simpler and easier to understand
• align the test runners with the rest of openstack projects