Project news

15-day Public Review for Cloud Application Management for Platforms (#CAMP) V1.1 – ends 17 March

The OASIS Cloud Application Management for Platforms (CAMP) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Cloud Application Management for Platforms Version 1.1
Committee Specification Draft 04 / Public Review Draft 02
12 February 2014

Specification Overview:

The specification defines the artifacts and APIs that need to be offered by a Platform as a Service (PaaS) cloud to manage the building, running, administration, monitoring and patching of applications in the cloud. Its purpose is to enable interoperability among self-service interfaces to PaaS clouds by defining artifacts and formats that can be used with any conforming cloud and enable independent vendors to create tools and services that interact with any conforming cloud using the defined interfaces. Cloud vendors can use
these interfaces to develop new PaaS offerings that will interact with independently developed tools and components.

TC Description:

The OASIS CAMP TC advances an interoperable protocol that cloud implementers can use to package and deploy their applications. CAMP defines interfaces for self-service provisioning, monitoring, and control. Based on REST, CAMP is expected to foster an ecosystem of common tools, plugins, libraries and frameworks, which will allow vendors to offer greater value-add.

Common CAMP use cases include:

– moving on-premise applications to the cloud (private or public)
– redeploying applications across cloud platforms from multiple vendors

Public Review Period:

The public review starts 03 March 2014 at 00:00 GMT and ends 17 March 2014 at 23:59 GMT. The specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous review. Changes are highlighted in the diff-marked PDF file [3].

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs:
The prose specification document and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/camp/camp-spec/v1.1/csprd02/camp-spec-v1.1-csprd02.pdf

HTML:
http://docs.oasis-open.org/camp/camp-spec/v1.1/csprd02/camp-spec-v1.1-csprd02.html

Editable source:
http://docs.oasis-open.org/camp/camp-spec/v1.1/csprd02/camp-spec-v1.1-csprd02.doc

CAMP Type Definitions:
http://docs.oasis-open.org/camp/camp-spec/v1.1/csprd02/type-definitions/

ZIP distribution files (complete):

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/camp/camp-spec/v1.1/csprd02/camp-spec-v1.1-csprd02.zip

Additional information about this specification and the CAMP TC may be found on the TC’s public home page located at:

http://www.oasis-open.org/committees/camp/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:

http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=camp

Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:

http://lists.oasis-open.org/archives/camp-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of ‘Cloud Application Management for Platforms Version 1.1,’ we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification. OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

========== Additional references:

[1] OASIS Cloud Application Management for Platforms (CAMP) TC
http://www.oasis-open.org/committees/camp/

[2] Previous public reviews:
– 30 day public review, 19 August 2013: https://lists.oasis-open.org/archives/tc-announce/201308/msg00011.html
– Comment resolution log: http://docs.oasis-open.org/camp/camp-spec/v1.1/csprd01/camp-spec-v1.1-csprd01-comment-log.ods, http://docs.oasis-open.org/camp/camp-spec/v1.1/csprd01/camp-spec-v1.1-csprd01-comment-log.xlsx

[3] Redlined DIFF file: http://docs.oasis-open.org/camp/camp-spec/v1.1/csprd02/camp-spec-v1.1-csprd02-DIFF.pdf

[4] http://www.oasis-open.org/policies-guidelines/ipr

[5] http://www.oasis-open.org/committees/camp/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.3
Non-Assertion Mode