2.9 KiB

The title of your blueprint

Include the URL of your launchpad blueprint:

Introduction paragraph -- why are we doing anything?

Problem description

A detailed description of the problem.

Proposed change

Here is where you cover the change you propose to make in detail. How do you propose to solve this problem?

If this is one part of a larger effort make it clear where this piece ends. In other words, what's the scope of this effort?

Include where in the tempest tree hierarchy this will reside.

If the change is designed to test other OpenStack projects then list which ones it is targeted at.


This is an optional section which applies if the blueprint covers infrastructure changes to tempest. For example, blueprints which are just adding more API tests can leave this section empty.

Where it does apply we'd just like a demonstration that some thought has been put into why the proposed approach is the best one.


List the qa projects that this spec effects. For example:

  • openstack/tempest
  • openstack/tempest-lib
  • openstack-dev/devstack



Who is leading the writing of the code? Or is this a blueprint where you're throwing it out there to see who picks it up?

If more than one person is working on the implementation, please designate the primary author and contact.

Primary assignee:

<launchpad-id or None>

Can optionally can list additional ids if they intend on doing substantial implementation work on this blueprint.


Target Milestone for completion:


Work Items

Work items or tasks -- break the feature up into the things that need to be done to implement it. Those parts might end up being done by different people, but we're mostly trying to understand the timeline for implementation.


  • Include specific references to specs and/or blueprints in tempest, or in other projects, that this one either depends on or is related to.
  • Does this feature require any new library dependencies or code otherwise not included in OpenStack? Or does it depend on a specific version of library?