CAMP-4 update, and CAMP-9 on the agenda?

    https://www.oasis-open.org/apps/org/workgroup/camp/download.php/49423/camp-spec-v1.1-wd10-issue-4-v4.pdf (changes not shown)
    https://www.oasis-open.org/apps/org/workgroup/camp/download.php/49422/camp-spec-v1.1-wd10-issue-4-v4.doc (with changes marked)

This is not ready for merging but it could be made into a mergeable version by next week if we have tentative agreement; and I propose we could then tackle the outstanding aspects (parameters+references+functions, and versions+metadata) as new issues.

I'd also like to suggest that as part of the agenda we discuss CAMP-9 (sensors and operations) which does have a proposal:

    https://tools.oasis-open.org/issues/browse/CAMP-9

Best
Alex

-------- Original Message --------

Subject:	[camp] [OASIS Issue Tracker] Commented: (CAMP-4) Need a formal specification of the PDP format
Date:	Wed, 5 Jun 2013 08:11:54 -0400 (EDT)
From:	OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To:	camp@lists.oasis-open.org

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

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

I have uploaded an updated proposal building on Gil's previous version and incorporating the discussion from the various meetings.  Specifically:

- replaces "targetType" with the concept of an explicit "type" for requirement specifications
- clarifies the expectation that a typical path is to provide component specs for ACT's with "content" and "requirements", while also permitting other scenarios where e.g. a PCT may be specified and constrained by "requirements" or even a "type", and where the correspondence between component specs and runtime components (ACT's / PCT's) is more subtle
- reinstates a single "fulfillment" attribute replacing "ref" and "fulfill"
- miscellaneous minor changes for consistency and clarity

This replaces the previous proposal:

    https://www.oasis-open.org/apps/org/workgroup/camp/download.php/49086/camp-spec-v1.1-wd10%20%282%29-issue-4-v3.doc

with:

    https://www.oasis-open.org/apps/org/workgroup/camp/download.php/49423/camp-spec-v1.1-wd10-issue-4-v4.pdf (changes not shown)
    https://www.oasis-open.org/apps/org/workgroup/camp/download.php/49422/camp-spec-v1.1-wd10-issue-4-v4.doc (with changes marked)


> 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

        

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

camp message