OASIS Cloud Application Management for Platforms (CAMP) TC

Join TC     TC Page     Send a comment to this TC

Standardizing cloud PaaS management API

Anish Karmarkar, Anish.Karmarkar@oracle.com, Chair
Gilbert Pilz, gilbert.pilz@oracle.com, Secretary

Table of Contents

Announcements

Participation in the OASIS CAMP TC is open to all interested parties. Contact join@oasis-open.org for more information.


Overview

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

For more information on CAMP, see the TC Charter.


Subcommittees

No subcommittees have been formed for this TC.


TC Liaisons

No TC Liaisons have been announced for this TC.


TC Tools and Approved Publications


Technical Work Produced by the Committee

The latest Committee approved version of the CAMP V1.1 specification can be found here: PDF, word and html.


Expository Work Produced by the Committee

There are no approved expository work products for this TC yet.


External Resources

Although not produced by the OASIS CAMP TC, the following information offers useful insights into its work:


Mailing Lists and Comments

camp: the list used by TC members to conduct Committee work. TC membership is required to post. TC members are automatically subscribed; the public may view archives.

camp-comment: a public mail list for providing input to the OASIS CAMP TC members. Send a comment or view archives.


Press Coverage and Commentary


Standing Rules

  • Rule 1 (adopted nov 2012) :the TC will follow the issues lifecycle defined in CAMP TC Proposed Issues Process v6.ppt
  • Rule 2 (adopted nov 2012): Chair is responsible for applying all JIRA state transitions except resolved->applied, which will be handled by the editors
  • Rule 3 (adopted nov 2012):All JIRA transitions except resolved->applied and reopen require majority approval.
  • Rule 4 (adopted nov 2012):Reopening a closed or deferred issue requires 2/3rd majority.

Additional Information


Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.