ࡱ> <>;U@ bjbj ("= J%   , < < < P 8P -00FFFF f r,,,,,,,$/RV10,< 1FF11,< < FF,CCC1< F< F,C1,C CO?(< < +F$ 0OM('*(,,0-O*1u1P+P P < < < < +41< ;,`zC zzz,,P x D'P x Common Manageability Model (CMM) Overview A fundamental requirement of grid management infrastructure is the ability to define the resources and resource management functions of the system in a standard and interoperable way. The capabilities of the grid management infrastructure rely on the ability to discover, compose, and interact with the resources and the resources managers responsible for them. The Common Manageability Model (CMM) specification defines the base behavioral model for all resources and resource managers in the grid management infrastructure. A mechanism is defined by which resource managers can make use of detailed manageability information for a resource which may come from existing resource models and instrumentation, such as those expressed in CIM, JMX, SNMP, etc, combined with a set of canonical operations introduced by base CMM interfaces. The result is a manageable resource abstraction that introduces OGSI compliant operations over an exposed underlying base content model. CMM does not define yet another manageability (resource information) model. The Common Manageability Model specification defines the base manageable resource interface that which a resource or resource manager must provide to be manageable canonical lifecycle states, the transitions between the states, and the operations necessary for the transitions that complements OGSI lifetime service data the ability to represent relationships among manageable resources (instances and types) including a canonical set of relationship types lifecycle metadata (XML attributes) common to all types of managed resources for monitoring and control of service data and operations based on lifecycle state canonical services factored out from across multiple resources or domain specific resource managers, such as an operational port type (start/stop/pause/resume/quiesce) Additional items that may become within the scope of the CMM specification (driven by its companion community practice document) are new data types or metadata to convey semantic meaning of manageability information, such as counter or gauge versioning information meta data to associate a metered usage (unit of measure) with manageability information classification of properties such as metric, configuration registries and locating fine-grained resources managed resource identifier To summarize, CMM represents the proposed industry standard for representing manageable resources and resource managers within the grid management infrastructure. The CMM interfaces are OGSI compliant and are used as the base abstract interfaces from which specific manageable resource types are derived. Standardization of the base management behavior is required in order to integrate the vast number and types of resources and more limited set of resource managers introduced by multiple vendors.  Organizations like as DMTF already define a comprehensive resource information model. Overtime, it is important that we provide input to DMTF as they move their information model rendering to XMI, XSD, and WSDL.  The intent is to work with the OASIS WSDM workgroup since comprehensive change control is part of their agenda. 20 July 2003  PAGE 1 *f ; }  ! * % D E F G y | }  ^ d Z\]սɽɫ蘉znhu1PJ^JnHtHhh2~PJ^Jh{dh`Qhu1PJ^JnHtHhu1hh`QPJ^JnHtH#jh?<0JPJU^JnHtHhPJ^JnHtHh8aPJ^JnHtHhh8aPJ^JnHtHhihh`Qh8ah2~h h\FK+*+ F G } []Og)F $ & Fa$gd $ ^a$gd $ & Fa$gd $^a$gd $^a$gd`Q $^a$gd ^gd\FK=NOef()EFGyz<=>Ҵ|pppaWWMjh00JUjh00JUh`Qh PJ^JnHtHh|PJ^JnHtHh^5PJ^JnHtHh2~PJ^JnHtHh2~B*PJ^JnHphtHh0PJ^JnHtHh0h0hiPJ^JnHtHhihiPJ^JnHtHhi#jh 0JPJU^JnHtHhu1PJ^JnHtHh PJ^JnHtHFG=^gd  $^a$gd  $^a$gd?< $^a$gd`Q ^gdlE h`Qh PJ^JnHtHh0h00JmHnHujh00JU h00J&1h:p2~/ =!"#$%N@N 2~Normal$^a$OJQJ_HmH sH tH @ 2~Heading 1,Heading 1 Char Char$ & F ~ <@&5CJ$KH \^JaJ V@V 2~ Heading 2$ & F<@&5CJ\^JaJ@ 2~<Heading 3,Heading 3 Char1,Heading 3 Char Char,Heading 3 Char*$$ & F T<@&^5CJ\^JaJ<@< 2~Heading 4,Heading 4 Char1,Heading 4 Char Char,Heading 4 Char2 Char Char,Heading 4 Char1 Char Char Char,Heading 4 Char Char Char Char Char,Heading 4 Char1 Char Char Char Char Char,Heading 4 Char Char Char Char Char Char CharU$ & F ,8Xx xHX (#0d7$8$@&H$^0 56CJ\b@b 2~ Heading 5$$ & F@&a$5B*CJOJQJ\aJph\@\ 2~ Heading 6$ & F@&5B*CJOJQJ\^JphF@F 2~ Heading 7$ & F@& 5\^JF@F 2~ Heading 8$ & F@& 5\^J\ @\ 2~ Heading 9) $$ & F#d7$8$@&H$]#5\DA@D Default Paragraph FontRi@R  Table Normal4 l4a (k@(No ListHH 2~ Balloon TextCJOJQJ^JaJ4U@4  Hyperlink >*phd^@d  Normal (Web)$dd[$\$^a$CJOJPJQJaJN>@"N  Title$<@&a$5CJ KH\^JaJ 4@24  Header  !4 @B4  Footer  !.)@Q.  Page Number6@b6 ?< Footnote Text@&@q@ ?<Footnote ReferenceH*De IL "[]G @0@0@0@00R*+FG}[]Og) F G =  0000000 0 0 0 0 000 0 0 0 0 0  0 00@0@00V2@0@00 ӝ*+FG}[]OgF G ;00;00000;00;000000 ;0 | ;0  ;0 0;0 000R$$$' F  !'! _Toc45077423 * 4  8*urn:schemas-microsoft-com:office:smarttagsdate 2020037DayMonthYear= ) F = E F F G G y z  ; ; < = ?   =  |+}t~\ >MZ2 :vl dĻcg@d}"/R)QdN]qAdNsE=H:jIdN6I-v,)(JdNd*j-v|mdN-vsEr~ &U"0u1^5\FK`Q8a2~ lE{d| F?<i@E E $)E E  @@UnknownGz Times New Roman5Symbol3& : Arial;SimSun[SOC PMingLiUe0}fԚ5& zaTahoma?5 z Courier New;Wingdings"hԥww& U  !4d8 8 3qH  F1  P            Oh+'0\   $ 0<DLT1ss sssNormal rm9rmMicrosoft Word 10.0@> @Y?O@4灊O ՜.+,0 hp|  IBM8 { 1 Title  !"#$%&'()*,-./012456789:=Root Entry FJ0O?1Table1WordDocument("SummaryInformation(+DocumentSummaryInformation83CompObjj  FMicrosoft Word Document MSWordDocWord.Document.89q