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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Alex Heneveld commented on CAMP-4:
----------------------------------

we had a meeting last week where we discussed this (as the single biggest hole!).
here are my notes:

- weak agreement that PDP should essentially be a batch operation, of individual things people can upload anyway
    (assembly templates, application component tempaltes, platform requirements)

- weak agreement that requirements/capabilities can be used for functional purposes
    (e.g. i want an appserver, or sql database) in additional to non-functional (i want 99.9% uptime);
    however CAMP will not provide namespace / conventions around this

- wiring / configuration
-- Auto-wiring (platform fulfills requirements) vs manual (user supplies); or even deep (transitive) requirement fulfillment
--- how do we support these, and how much?  (within assembly templates and application components, i guess?)

- identifiers - 3 types
--user-supplied identifiers --> local ones being uploaded in a PDP will get mangled by the CAMP server
    how does the user know the server's URI reference to thing(s) he supplies?
    - proposal:  exactly on AssemblyTemplate per PDP, and URI returned for that AssemblyTemplate       
-- platform-specific (PlatformComponentTemplate) identifiers
-- convention identifiers (eg requirements)
corollary:  for portability, use requirements, not platform component template references!

also, in general, we need some use cases and pseudocode / worked examples !


> 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