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] Commented: (TOSCA-17) Packaging Format for TOSCA


    [ http://tools.oasis-open.org/issues/browse/TOSCA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30572#action_30572 ] 

Frank Leymann  commented on TOSCA-17:
-------------------------------------

I don't understand some of the discussion.

JAR is based on ZIP (here is a link to the JAR specification: http://docs.oracle.com/javase/1.4.2/docs/guide/jar/jar.html).  

JAR blocks are artifact-type specific and contain all metadata needed.  We (i.e. the TOSCA TC) need to agree on the artifact-types we want to support and define the name/value-pair representation of the metadata needed.

Together, I think the current CSAR proposal allows what Tobias' first proposal is about. If I am mistaken, I am happy to learn what I didn't get. 

I don't understand the Java-specifics in JAR and especially in CSAR. Of course, the renaming that Tobias proposes is fine with me, i.e. somebody should the actual CSAR document and change names that we then can debate (and agree on).  Although I would then make more radical name changes than that from MANIFEST.MF to manifest :-)  I.e. just call it "CSAR Metadata" or that like.

But my interpretation is that we agree on the content, overall structure, and mechanics of a packaging format.

I am not convinced that JSON is simpler than name/value pairs.

> Packaging Format for TOSCA
> --------------------------
>
>                 Key: TOSCA-17
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-17
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Spec
>    Affects Versions: CSD03
>            Reporter: Frank Leymann 
>
> Specifying a cloud application requires a number of different artifacts. In order to allow self-contained definitions of cloud applications a packaging format is needed that contains all the artifacts making up a manageable cloud application.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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