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=30521#action_30521 ] 

Koert Struijk  commented on TOSCA-17:
-------------------------------------

About dependencies for container/package:

In the metadata we may need 'major' dependencies to decide if the container can be used in the particular environment.

A powerful concept is allowing dependencies to other containers/packages that need to be deployed first (ensuring correct order, synchronized versions). We may also need to be able to describe a dependency to a product type (ie. something that may be satisfied by alternative implementations).

Also some metadata may need to describe the target environment in some way - 'Showstopper' dependencies to the environment so you can decide early if the container/package is suitable early on.

Also where non-sealed blocks are described this may open up the option to describe artifacts that need to be available but do not follow the container/package (if we want to allow that).

Some dependencies can already be figured out from the types of the artifacts in the individual blocks.

Having dependencies at the block level opens up the possibility to include alternative blocks where one or the other would be used according to the environment. 

I think the more detailed dependencies probably should be in the TOSCA descriptions and not in the packaging metadata.

Regards, Koert

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