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

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

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


Subject: [OASIS Issue Tracker] Commented: (CAMP-4) Need a formal specification of the PDP format


    [ http://tools.oasis-open.org/issues/browse/CAMP-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32805#action_32805 ] 

Jacques Durand  commented on CAMP-4:
------------------------------------

The merging of  issue CAMP-21 actually raises questions beyond just the PDP:

- Should an assemblyTemplate have a unique signature in terms of its resource components (at least as far as its Application Component Templates is concerned), that does not vary across Providers?

The diagram from Gil in #21 suggests not.

But in section 5, def of AssemblyTemplates suggests yes:
"The platform shall instantiate the Application Components and their configurations  as specified in the definition of the Assembly Template."  Which is a fairly common expectation from a modeling viewpoint:  ADEs will generate AssemblyTemplates composed of ACTs and other Component Requirements. It will be expected that  different Providers respect this composition.

Re-reading the definition of #21: "One provider could choose to model this application as an Assembly Template with a single Application Component Template ..."
I think it would be cleaner if we decide that "templates" and their contents are precisely what Providers cannot modify , while "instances" are where Providers exercise their interpretation rights (e.g. when matching a component with requirements). Do we really need some interpretation flexibility "above" instances level? 

> Need a formal specification of the PDP format
> ---------------------------------------------
>
>                 Key: CAMP-4
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-4
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Anish Karmarkar
>            Assignee: Adrian Otto
>            Priority: Critical
>
> What is the packaging format (.jar, .zip) and structure defined for the PDP? How are artifacts organized in the PDP? How does the Cloud know where to look for the deployment plan?
> This is CAMP 1.0 drupal issue # 1008 & # 1085
> Specific comments from Tobias Kunze:
> - Use reserved filenames instead of extensions
> - Allow standard PKI
> - Be prescriptive about the archive format (zip, tar, cpio), specifically zip, also see TOSCA's CSAR discussion
> - Be prescriptive about what hash algorithms to use (md5, sha1, sha512, etc.) and how to declare them?

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