OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (TOSCA-280) Support for mapping a hierarchy of software components to deployment artifacts

    [ https://issues.oasis-open.org/browse/TOSCA-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61827#comment-61827 ] 

Paul Lipton edited comment on TOSCA-280 at 2/18/16 6:20 PM:


was (Author: lippa02):
Formally introduced to the TC on 2016-02-18. From the minutes:

[13:07] Damian A. Tamburri (PoliMi - SCRIBE): Sivan is reporting that the issue aims at tagging instances that exhibit certain characteristics and providing the ability to query using this additional information

[13:08] Damian A. Tamburri (PoliMi - SCRIBE): Simon remarks that it may be an issue for the Instance-Model but Matt may comment that it could be already addressed elsewhere

[13:09] Damian A. Tamburri (PoliMi - SCRIBE): Matt is reporting on the concept of meta-data, this can be used at instance-model or catalog to tag things... in open-stack this could be used to coalesce or aggregate type-meaning information and creating groups with it

[13:11] Damian A. Tamburri (PoliMi - SCRIBE): action item should be to capture the use-cases that are not covered by the meta-data concept and its usages - further details may be needed to close the issue. However, there are instance-model concerns on the issue and therefore there may be perspectives which are not covered by the meta-data concept

[13:13] Damian A. Tamburri (PoliMi - SCRIBE): Derek comments that the issues may be separated, perhaps additional details should be tweaked in the service template definition

[13:14] Damian A. Tamburri (PoliMi - SCRIBE): Sivan agrees that issue can be passed to Instance-model ad-hoc to proceed with its further exploration and resolution

> 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 packaged in.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]