ANSI INCITS 530-2013 Information Technology - Architecture for Managed Computing Systems.pdf

《ANSI INCITS 530-2013 Information Technology - Architecture for Managed Computing Systems.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 530-2013 Information Technology - Architecture for Managed Computing Systems.pdf（663页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Architecture forManaged Computing SystemsINCITS 530-2013INCITS 530-2013INCITS 530-2013American National Standardfor Information Technology Architecture forManaged Computing SystemsSecretariatInformation Technology Industry CouncilAppro

2、ved December 30, 2013American National Standards Institute, Inc.Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement o

3、f the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted ef

4、fort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conformi

5、ng to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name o

6、f the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American Nation

7、al StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished

8、byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2014 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permis

9、sion of ITI, 1101 K Street NW, Suite 610, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither th

10、e developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply to this standard. As of the date of publication of this standardand following calls for the identification of patents that may be required for the implementation ofthe standard, no suc

11、h claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.i CONTENTS Foreword.ix Introduction . 1 Document

12、 conventions 1 Typographical conventions . 1 ABNF usage conventions . 1 Deprecated material 2 Experimental material . 2 Common Information Model (CIM) Infrastructure . 2 Core model . 3 Common model . 3 Extension schema . 3 CIM implementations 4 CIM implementation conformance 5 CIM Query Language Spe

13、cification 5 UML Profile for CIM . 5 Management Profile Specification Usage Guide 6 1 Scope 7 1.1 Common Information Model (CIM) Infrastructure . 7 1.2 CIM Query Language Specification 7 1.3 UML Profile for CIM 7 1.4 Generic Operations . 7 1.5 Management Profile Specification Usage Guide 8 1.6 Messa

14、ge Registry XML Schema Specification . 9 2 Normative references 9 3 Terms and definitions 12 3.1 Definitions related to CIM qualifier values 12 3.2 Other terms and definitions . 13 4 Symbols and abbreviated terms 35 5 Common Information Model (CIM) Infrastructure v2.7.0 . 38 5.1 Meta Schema 38 5.1.1

15、 Definition of the Meta Schema . 38 5.1.2 Data Types . 57 5.1.3 Backwards Compatibility 66 5.1.4 Supported Schema Modifications 66 5.1.5 Class Names 76 5.1.6 Qualifiers 76 5.2 Managed Object Format . 108 5.2.1 MOF Usage 109 5.2.2 Class Declarations . 109 5.2.3 Instance Declarations 109 5.3 MOF Compo

16、nents . 109 5.3.1 Keywords . 110 5.3.2 Comments 110 5.3.3 Validation Context 110 5.3.4 Naming of Schema Elements 110 5.3.5 Class Declarations . 111 5.3.6 Association Declarations . 113 5.3.7 Qualifiers 118 5.3.8 Instance Declarations 121 5.3.9 Method Declarations 126 5.3.10 Compiler Directives 128 5

17、.3.11 Value Constants . 128 5.4 Naming 130 ii 5.4.1 CIM Namespaces 130 5.4.2 Naming CIM Objects 131 5.4.3 Identity of CIM Objects 135 5.4.4 Requirements on Specifications Using Object Paths 135 5.4.5 Object Paths Used in CIM MOF 136 5.4.6 Mapping CIM Naming and Native Naming 137 5.5 Mapping Existing

18、 Models into CIM . 138 5.5.1 Technique Mapping . 138 5.5.2 Recast Mapping . 139 5.5.3 Domain Mapping 141 5.5.4 Mapping Scratch Pads . 142 5.6 Repository Perspective . 142 5.6.1 DMTF MIF Mapping Strategies 143 5.6.2 Recording Mapping Decisions . 144 6 CIM Query Language Specification 147 6.1 Requirem

19、ents and concepts . 147 6.2 CIM Query Language (CQL) . 148 6.2.1 Identifying the CIM Query Language . 148 6.2.2 Query language type lattice . 149 6.2.3 Query functional description 150 6.2.4 Query language grammar 150 6.3 CIM Query Language considerations . 160 6.3.1 Considerations of the constructs

20、 in the BNF . 160 6.3.2 Query language functions 165 6.3.3 Query considerations . 167 6.3.4 Query errors . 167 7 UML Profile for CIM . 168 7.1 Usage of ABNF . 168 7.2 General definition of a UML profile . 168 7.3 Definition of the UML profile for CIM . 168 7.3.1 UML elements used . 169 7.3.2 Mapping

21、 of CIM elements 170 7.3.3 Mapping to UML packages 171 7.3.4 Mapping of CIM classes 173 7.3.5 Mapping of CIM indications . 174 7.3.6 Mapping of CIM associations . 174 7.3.7 Mapping of CIM properties 175 7.3.8 Mapping of CIM references . 177 7.3.9 Mapping of CIM methods . 178 7.3.10 Mapping of CIM pa

22、rameters and CIM return values 179 7.3.11 Mapping of CIM datatypes . 180 7.3.12 Mapping of CIM instances . 181 7.3.13 Mapping of CIM qualifiers 183 7.3.14 Mapping MOF file information 207 7.3.15 Stereotypes for the CIM meta elements 214 7.3.16 Other UML metaclasses used in the mapping . 215 7.3.17 C

23、onstraints . 221 7.3.18 Extension points . 274 7.3.19 Compatibility considerations 275 7.3.20 Limitations 275 7.3.21 Definition of UML profiles and type libraries 276 8 Generic Operations . 278 8.1 Concepts . 278 8.1.1 Generic operations model 278 8.1.2 Generic operations mappings 279 8.1.3 Conforma

24、nce to generic operations . 280 iii 8.1.4 Generic types . 281 8.1.5 Success and failure . 285 8.1.6 Preconditions and postconditions 285 8.1.7 Generic error messages 285 8.1.8 Consistency model. 286 8.2 Generic operations 290 8.2.1 Description format 292 8.2.2 Common operation parameters for all ope

25、rations . 293 8.2.3 Instance operations . 294 8.2.4 Direct instance enumeration operations 303 8.2.5 Pulled instance enumeration operations . 321 8.2.6 Method invocation 367 8.2.7 Class operations 371 8.2.8 Class enumeration operations . 380 8.2.9 Qualifier type operations 398 9 Management Profile S

26、pecification Usage Guide 407 9.1 Conformance 407 9.1.1 Profile and profile specification conformance 407 9.1.2 Implementation conformance 407 9.1.3 Instance conformance . 409 9.1.4 DMTF conformance requirements . 409 9.2 Concepts . 409 9.2.1 Overview 409 9.2.2 Management domain . 411 9.2.3 Managed o

27、bject type . 411 9.2.4 Managed environment and managed objects . 411 9.2.5 Profile definition . 411 9.2.6 Relationships between profile definition and management domain 411 9.2.7 Events and indications . 414 9.3 Profile definitions . 414 9.3.1 General 414 9.3.2 Profile elements . 415 9.3.3 Usage of

28、requirement levels 416 9.3.4 Definition of conditions . 417 9.3.5 Discovery mechanisms 422 9.3.6 Definition of the profile identification 423 9.3.7 Definition of schema references 424 9.3.8 Definition of profile categories . 424 9.3.9 Definition of profile relationships 425 9.3.10 Definition of abst

29、ract and concrete profiles . 434 9.3.11 Definition of the management domain . 435 9.3.12 Definition of registry references . 436 9.3.13 Definition of class adaptations . 436 9.3.14 Requirements for profile registration 457 9.3.15 Requirements for the definition of features 458 9.3.16 Requirements fo

30、r the definition of use cases 462 9.3.17 Backward compatibility 464 9.3.18 Definition of experimental content . 465 9.3.19 Deprecation of profile content 465 9.4 Profile general conventions and guidelines 465 9.4.1 General 465 9.4.2 Linguistic and notational conventions 465 9.4.3 Conventions and gui

31、delines for diagrams . 467 9.5 Profile implementation requirements 478 9.5.1 General 478 9.5.2 Implementation requirements for a set of profiles . 478 iv 9.5.3 Implementation requirements for implementation adaptations 482 9.5.4 Merge algorithm . 485 9.5.5 Implementation of deprecated definitions 48

32、7 9.6 Profile specification requirements . 487 9.6.1 General 487 9.6.2 Profile specification conventions 487 9.6.3 Profile specification structures . 492 9.6.4 Requirements for profile specification clauses 494 ANNEX A (normative) MOF syntax grammar description 526 ANNEX B (informative) CIM meta sch

33、ema 532 ANNEX C (normative) Units . 553 C.1 Programmatic units . 553 C.2 Value for units qualifier . 557 ANNEX D (informative) UML notation 560 ANNEX E (informative) Guidelines for CIM modeling 562 E.1 SQL reserved words . 562 ANNEX F (normative) EmbeddedObject and EmbeddedInstance qualifiers . 565

34、F.1 Encoding for MOF . 565 F.2 Encoding for CIM protocols 566 ANNEX G (informative) Schema errata . 567 ANNEX H (informative) Ambiguous property and method names . 569 ANNEX I (informative) OCL considerations . 572 ANNEX J (informative) CQL query examples 574 J.1 Information gathering examples . 574

35、 J.2 Event detection examples . 579 J.3 Policy examples 580 ANNEX K (normative) CQL BNF . 583 ANNEX L (normative) Regular Expressions . 584 L.1 Basic Like Regular Expressions . 584 L.2 Full Like Extended Regular Expressions 585 ANNEX M (normative) Datetime Operations and BNF 586 M.1 Datetime operati

36、ons 586 M.2 Datetime BNF (normative) 589 ANNEX N (normative) Additional query language features . 592 N.1 Simple Join . 592 N.2 Complex Join 592 N.3 Subquery . 592 N.4 Result set operations 592 N.5 Extended Select list 593 N.6 Embedded properties 594 N.7 Aggregations . 594 N.8 Regular Expression Lik

37、e . 595 N.9 Array Range 595 N.10 Satisfies Array . 596 N.11 Foreign Namespace support 596 N.12 Arithmetic Expression . 597 N.13 Full Unicode 598 N.14 Conversion utilities 598 N.15 Property scope 598 ANNEX O (normative) CIM query template language . 600 O.1 CQLTexamples . 600 ANNEX P (informative) UM

38、L metamodel diagrams . 602 ANNEX Q (informative) Future operations . 607 Q.1 Test for property modifiability 607 v Q.2 Retrieval of associated instance graph . 607 ANNEX R (informative) Examples from a hypothetical profile . 608 R.1 General . 608 R.2 Example of a “Synopsis“ clause . 608 R.3 Example

39、of a “Description“ clause 611 R.4 Example of an “Implementation“ clause . 612 R.4.1 Example of the general layout of an “Implementation“ clause 612 R.4.2 Example of feature definitions . 612 R.4.3 Example of the “Conventions“ subclause 614 R.4.4 Examples of subclauses defining adaptations . 614 R.4.

40、5 Examples of subclauses defining indication adaptations 622 R.5 Example of the “Use cases“ clause 625 ANNEX S (informative) Regular expression syntax . 629 ANNEX T (normative) Message Registry XML Schema 632 ANNEX U (informative) Bibliography . 648 Figures Figure 1 Four Ways to Use CIM 4 Figure 2 C

41、IM MetaSchema 39 Figure 3 Example with Two Weak Associations and Propagated Keys 115 Figure 4 General Component Structure of Object Path . 132 Figure 5 Component Structure of Object Path for Namespaces . 132 Figure 6 Component Structure of Object Path for Qualifier Types 133 Figure 7 Component Struc

42、ture of Object Path for Classes 134 Figure 8 Component Structure of Object Path for Instances . 134 Figure 9 Technique Mapping Example 138 Figure 10 MIF Technique Mapping Example . 139 Figure 11 Recast Mapping . 139 Figure 12 Repository Partitions 143 Figure 13 Homogeneous and Heterogeneous Export .

43、 145 Figure 14 Scratch Pads and Mapping 145 Figure 15 Example for package mapping 172 Figure 16 Example for replacement of UML class during conversionof CIM MOF to UML . 173 Figure 17 Generic operations model . 278 Figure 18null Generic operations mappings . 279 Figure 19 Profile and management doma

44、in . 410 Figure 20 Existence of adaptation instances . 413 Figure 21 Complexity when an implementation decision depends on a runtime element . 420 Figure 22 Autonomous profile with optional component profiles . 433 Figure 23 Two variants of a component profile using another component profile . 434 F

45、igure 24 Class adaptation reference example . 438 Figure 25 DMTF collaboration structure diagram of an example Sensors profile . 439 Figure 26 Examples of DMTF collaboration structure diagrams 461 Figure 27 Example of a DMTF collaboration structure diagram 471 Figure 28 Examples of DMTF adaptation d

46、iagrams 474 Figure 29 Examples of DMTF class diagrams . 476 Figure 30 Example of profiles and resulting profile implementations 480 vi Figure 31 Example of merging of adaptations into implementation adaptations . 481 Figure 32 Traditional and condensed profile structures . 494 Figure P-1 33 related

47、stereotypes 603 Figure P-2 Contents of UML Profile “CIMQualifierType“ . 604 Figure P-3 UML metaclasses representing a CIM class (high level) . 605 Figure P-4 UML metaclass instances for a simple CIM class 606 Figure P-5 CIM MOF definition of a simple CIM class . 606 Tables Table 1 Component document

48、s 6 Table 2 Standards bodies 9 Table 3 Intrinsic Data Types 57 Table 4 Compatibility of Schema Modifications . 68 Table 5 Compatibility of Qualifier Type Modifications 73 Table 6 Changes that Increment the CIM Schema Major Version Number 75 Table 7 Defined Qualifier Scopes 77 Table 8 Defined Qualifi

49、er Flavors 78 Table 9 Example for Mapping a String Format Based on the General Mapping String Format 107 Table 10 UML Cardinality Notations 118 Table 11 Standard Compiler Directives . 128 Table 12 Domain Mapping Example 142 Table 13 NOT expression 157 Table 14 AND expression 157 Table 15 OR expression 158 Table 16 Overview of CIM element mapping . 170 Table 17 UML Class metaclass . 173 Table 18 UML AssociationClass metaclass . 175 Table 19 UML Property metaclass used to map CIM p