[ https://issues.oasis-open.org/browse/TOSCA-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Derek Palma updated TOSCA-280:
------------------------------
Description: Deployment artifacts such as VM images, Docker images and archives with multiple nested deployment artifacts (e.g. J2EE archives), can contain 0 or more software components. In the situation where it is desirable to explicitly model all such software components to manage their life-cycles and control their configurations, there needs to be a way to specify the respective deployment artifact they are contained packaged in. (was: Deployment artifacts such as VM images, Docker images and archives with multiple nested deployment artifacts (e.g. J2EE archives), can contain 0 or more software components. In the situation where it is desirable to explicitly model all such software components to manage their life-cycles and control their configurations, there needs to be a way to specify the respective deployment they are contained packaged in.)
> Support for mapping a hierarchy of software components to deployment artifacts
> ------------------------------------------------------------------------------
>
> Key: TOSCA-280
> URL: https://issues.oasis-open.org/browse/TOSCA-280
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Improvement
> Components: Spec - Simple Profile
> Reporter: Derek Palma
>
> Deployment artifacts such as VM images, Docker images and archives with multiple nested deployment artifacts (e.g. J2EE archives), can contain 0 or more software components. In the situation where it is desirable to explicitly model all such software components to manage their life-cycles and control their configurations, there needs to be a way to specify the respective deployment artifact they are contained packaged in.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
