[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=33093#action_33093 ] Gilbert Pilz commented on CAMP-4: --------------------------------- Concrete changes to Alex's v2 proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/48892/camp-spec-v1.1-wd08-issue-4-v2-gp2.doc * Remove "Requirement Specification" as a top-level object. You can share requirements between Component Specifications (using "id") without having to promote Requirements to a top-level object. * Don't talk about Component Specifications types in terms of things that are defined in the resource model. From a developer perspective, this is putting the cart before the horse. PDPs exist before the creation of any resources in a platform so we should describe Component and Requirement Specification types on their own terms, without reference to specific resource instances which may or may not exist. * "Fulfillment" is a good/necessary concept, but we need to make it simpler. * Avoid references to any IaaS-level concepts like VMs etc. Obviously there will be CAMP implementations that involve these concepts, but the PDP material is complicated enough without introducing further, unspecified material. * Removed section on Extending Requirements. Unclear what the goal of this section was and the example didn't seem to illustrate what the text described. Suggest we work out the basics of DPs before we get into how to extend them. * Remove section on Transitive Requirements as it was confusing and the new material on Fulfillment References seems to solve the same problem. > 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]