Support TOSCA definitions for applications
TOSCA is a standard developed under OASIS foundation. It is aimed to cover definition of complex enterprise applications which might consist of different loosely coupled components. Components can be tied by using requirements and capabilities which are part of TOSCA standard. As TOSCA covers most of the Applications aspects (excluding app compilation and build) it should be straightforward to support TOSCA format in Murano.
TOSCA is adopted by enterprises so it will allow OpenStack ecosystem to integrate with enterprise IT applications.
Blueprint information
- Status:
- Complete
- Approver:
- Serg Melikyan
- Priority:
- Medium
- Drafter:
- Vahid Hashemian
- Direction:
- Approved
- Assignee:
- Vahid Hashemian
- Definition:
- Approved
- Series goal:
- Proposed for mitaka
- Implementation:
- Implemented
- Milestone target:
- mitaka-1
- Started by
- Vahid Hashemian
- Completed by
- Kirill Zaitsev
Related branches
Related bugs
Sprints
Whiteboard
https:/
(Vahid) My thoughts on this: https:/
The spec can be found here: https:/
Gerrit topic: https:/
Addressed by: https:/
Import TOSCA CSAR packages into Murano catalog
Work Items
Work items:
[vahidhashemian] Detect template format when creating a package (Item 1.1 in etherpad): TODO
[vahidhashemian] Populate other metadata fields based on detected format when creating a package (item 1.2 in etherpad): TODO
[vahidhashemian] Include all imported TOSCA templates when creating a package (item 1.3 in etherpad): TODO
[vahidhashemian] Detect format when importing a package and call Heat-Translator to validate if the format is TOSCA (item 1.4 in etherpad): TODO
[vahidhashemian] When importing a TOSCA package store its TOSCA template in the database (item 1.7 in etherpad): TODO
[vahidhashemian] When deploying a component if the format is TOSCA first call Heat-Translator to translate it into HOT (item 2.1 in etherpad): TODO