SourceForge : View Wiki Page: GRIDGridComponentModelGCMGCMInteroperabilityDeploymentETSITR102827

Search Wiki Pages Project: scrm-wg Wiki > GRIDGridComponentModelGCMGCMInteroperabilityDeploymentETSITR102827 > View Wiki Page

wiki2080: GRIDGridComponentModelGCMGCMInteroperabilityDeploymentETSITR102827

Standard

1. The name of the specification

ETSI TR 102 827 GRID; Grid Component Model (GCM);GCM Interoperability Deployment

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

This Technical Report offers a standard, uniform way of describing grid resources, so as to make these resources available to grid-based applications. When building a grid, one is confronted to several problems, among which: choosing a grid framework, as many are available. when running a grid-enabled application, one must rewrite configuration directives when switching to a different grid framework. a grid can be built on widely different hardware infrastructures, from an heterogenous set of desktop machines to a dedicated cluster, or even any combination of those. grid infrastructures can also be very dynamic, it should be easy to add or remove machines, and such changes should be transparent to users. To simplify this, the GCM Interoperability Deployment standard offers a uniform way to describe grid resources, how they are connected to one another, how they can be activated, and how they can be accessed.

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

Version 1.1.1 (2008-8)

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

Grid Component Model (GCM)

5. URI for the normative text of the specification

http://pda.etsi.org/PDA/queryform.asp?profile=LMI-zx3i52qMKbiObiutMe

SOURCE

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

European Telecommunications Standards Institute (ETSI)

7. URI for the SDO

http://www.etsi.org/website/homepage.aspx

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

Published

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?

(http://en.wikipedia.org/wiki/FCAPS, http://www.futsoft.com/pdf/fcapswp.pdf) Fault Management: Fixing broken resources. Configuration Management: Controlling a resource's operational parameters. Accounting Management: Recording and analyzing resource use. Performance Management: Controlling speed and efficiency of resource use. Security Management: Controlling access to resources.

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 ) Application layer.

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

(http://www.dmtf.org/standards/cim/)

Policy Management Infrastructure Physical Networks Logical Networks Physical Systems Logical Systems Physical Devices Logical Devices Physical Storage Logical Storage Operating Systems Databases Application Servers Applications Users Security Support

OPTIONAL

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

Published

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

http://www.etsi.org/website/copyright.aspx

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.

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

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

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

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).

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.

Show Details