The title of your blueprint¶
Include the URL of your launchpad blueprint:
Introduction paragraph – why are we doing anything?
A detailed description of the problem.
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 heat tree hierarchy this will reside.
If your specification proposes any changes to the Heat REST API such as changing parameters which can be returned or accepted, or even the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query:
This is an optional section, 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.
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 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 heat, 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?