Add support for APS-format packaging
The Aapplication Packaging Standard (APS, http://
The model behind APS is that an application is packaged in a standard format, and hosted by an APS controller that supports known API endpoints for retrieving packages, type information etc (quite similar to what Murano does now). Applications in turn must support an API that allows the controller to perform a set of operations (update being one, lifecycle operations etc).
While this is very similar to Murano right now, it would likely ease transition, especially since there is a huge existing catalog of APS-packaged applications at http://
HP has some interest in this (as well as TOSCA); it would be worth investigating what support there would be for this since it is likely a large development effort.
Blueprint information
- Status:
- Not started
- Approver:
- ruhe
- Priority:
- Undefined
- Drafter:
- Steve McLellan
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- Accepted for future
- Implementation:
- Unknown
- Milestone target:
- next
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
+1 to support multiple formats. We need to understand how to do this on architecture level. Probably we can reuse the approach which Heat has adopted - translators. Overall, APS and TOSCA support is a very huge step forward to have an advanced app catalog for openstack.