Standard

1. The name of the specification

Configuration Description, Deployment, and Lifecycle Management CDDLM Deployment API

2. A short statement (<100 words) of the purpose and function of the specification

The deployment API is the WSRF-based SOAP API for deploying applications to one or more target computers. Every set of computers to which systems can be deployed hosts one or more "Portal Endpoints", WSRF resources which provide a means to create new "System Endpoints". A System Endpoint represents a deployed system. The caller can upload files to it, then submit a deployment descriptor for deployment. A System Endpoint is effectively a component in terms of the Component Model specification it implements the properties and operations defined in that document. It also adds the ability to resolve references within the deployed system, enabling remote callers to examine the state of components with it.

3. The version number (or other distinct identifier) and date of the most recently approved version of the specification.

1.0

4. If the specification is part of a group of explicitly related specifications from the same source, the name of the group of specifications.

• CDDLM foundation document
• CDDLM SmartFrog based Language
• CDDLM XML Configuration Description Language
• CDDLM Component Model
• CDDLM Deployment API

5. URI for the normative text of the specification

http://www.ogf.org/Public_Comment_Docs/Documents/Oct-2005/draft-ggf-cddlm-deploy-api2.pdf

SOURCE

6. The name of the SDO that generated/authored/hosted the specification.

Open Grid Forum (OGF)

7. URI for the SDO

http://www.ogf.org

8. The level of approval that the SDO has conferred on the specification as described by the SDO's process.

Grid Working Draft Recommendation Proposal (GWD-R.P)

9. The language or languages in which the specification is available.

English

SUBJECT

10. Which of the ITU-T TMN FCAPS model layers does the specification's functionality address?

• Configuration Management: Controlling a resource's operational parameters.
• Performance Management: Controlling speed and efficiency of resource use.

12. Where does the specification directly operate, as among the layers defined in the ISO Open System Interconnect (OSI) model?

(http://www.looselycoupled.com/opinion/2003/saruk-osi-infr0905.html )

• Presentation Layer
• Application Layer

13. Which of the following (CIM based) functional areas does the model of the specification address?

• Logical Systems
• Applications

OPTIONAL

14. The level of approval of the specification in this generic lifecycle taxonomy:

• Final approval

15. URI for the applicable SDO's patent and copyright rules, if any, applicable to development and use of the specification.

http://www.ogf.org/ggf_abt_policies.htm

16. URI for the SDO's posting location, (if any) for notices from participants or individuals regarding claims under the rules stated under number 15.

http://www.ogf.org/ggf_abt_policies_ipr.htm

17. Interoperability, conformance, or certification test activity for the specification (by owner name or URI).

N/A

18. Known implementations of the specification (by owner name or URI).

N/A

19. A list (or URI pointer to same) of the other specifications* that are normatively referenced in the specification.

<TBD>

20. A list (or URI pointer to same) of the other specifications* that are referenced in the specification (except the ones listed under number 19).

<TBD>

21. A list (or URI pointer to same) of other specifications* with which the specification may (speculatively) interoperate or act in complementary, compatible fashion.

22. A list (or URI pointer to same) of other specifications* similar to this specification. (Whether or not substitutable.)

*: Please identify where reference specification is within SDO member organizations or not and current level of approval as the level of question.