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=30737#action_30737 ] 

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

The agreement is as follows:

1. The underlying archive format is the zip format

2. There will be two pre-defined directories in that zip file, the TOSCA-Metadata directory (formerly called Meta-Inf) and the Service-Template directory

3. The Service-Template directory consists of one or more ServiceTemplate files. One of this service template is the "entry service template" (distinguished in the TOSCA.meta file - see next), describing the specific cloud application. The other service templates contain modularized TOSCA definitions like plans, node types etc if applicable (i.e. in case the cloud application has been defined in such a modular manner). 

4. The TOSCA-Metadata directory contains one TOSCA.meta file (formerly called MANIFEST.MF). This file contains the blocks of name/value-pairs decribed in the current CSAR spec draft. 

5. Signing artifacts is not supported in version 1 of the CSAR format, i.e. the TOSCA-Metadata directory will not contain any other files. Thus, future releases may define files in this directory that support extended features like signing. 

6. The other subdirectories of a CSAR zip file are not pre-defined, i.e. they are specific to the service template (the cloud application, respectively). 

7. Except Bock_0 of the TOSCA.meta file, all other metadata for artifacts of a CSAR will be defined separately. I.e. the corresponding name/value-pairs will be defined in conjunct with the artifact-types the TOSCA TC decides to be supported by a compliant application. For example, metadata for scripts (Python, PHP...), Java components (EAR...), images,... will be defined separately. This metadata may include authorization/authentication information in case the corresponding artifact type requires this (like scripts).

8. The current CSAR spec draft will be split and folded into a new TOSCA WD that Thomas, Tobias, and Frank will create.


> 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]