Allow upload of Provider templates
From http://
* Modify the resource instantiation to search among multiple named
definitions (either Custom or Plugin) for a resource type, according to
the "Provider" name.
* Add an API for posting multiple named implementations of a resource type.
Blueprint information
- Status:
- Complete
- Approver:
- Zane Bitter
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Angus Salkeld
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
- Implemented
- Milestone target:
- 2013.2
- Started by
- Angus Salkeld
- Completed by
- Angus Salkeld
Related branches
Related bugs
Sprints
Whiteboard
Allow the user to POST a provider template to:
/v1/
whose schema can then be accessed at:
/v1/
Then modify the creation of custom resources to allow the template to be read from a named, existing provider as well as from a URL.
*NOTE*
I've been rethinking the wisdom of having Heat act as a store for templates... it makes version control difficult. So we may scrap the details of this proposal in favour of uploading providers along with the template at stack create/update time. See this mailing list post (starting about mid-way down) for details:
http://
Gerrit topic: https:/
Addressed by: https:/
Initial template resources (aka provider resources)
Addressed by: https:/
Make template_
Addressed by: https:/
Remove unused parameter.
Addressed by: https:/
Use the Environment from within the engine
Addressed by: https:/
Initial Environment class and test
Addressed by: https:/
Cleanup the doc strings in heat/rpc/client.py
Addressed by: https:/
API support for Environments
Gerrit topic: https:/
Gerrit topic: https:/
Work Items
Work items:
I have committed a "lite" version that uploads the templates at stack create time: DONE
the uploading via a separate rest API is: TODO
Dependency tree
* Blueprints in grey have been implemented.