1 a.dunfey 1.1 // ===================================================================
2 // Title: Physical Replacement Sets and Capacity
3 // $State: Preliminary $
4 // $Date: 2005/01/05 00:54:01 $
5 // $Source:
6 // /home/dmtf2/var/cvs/repositories/dev/Schema/MOF/Physical_Misc.mof,v $
7 // $Revision: 1.6 $
8 // ===================================================================
9 //#pragma inLine ("Includes/copyright.inc")
10 // Copyright 1998-2005 Distributed Management Task Force, Inc. (DMTF).
11 // All rights reserved.
12 // DMTF is a not-for-profit association of industry members dedicated
13 // to promoting enterprise and systems management and interoperability.
14 // DMTF specifications and documents may be reproduced for uses
15 // consistent with this purpose by members and non-members,
16 // provided that correct attribution is given.
17 // As DMTF specifications may be revised from time to time,
18 // the particular version and release date should always be noted.
19 //
20 // Implementation of certain elements of this standard or proposed
21 // standard may be subject to third party patent rights, including
22 a.dunfey 1.1 // provisional patent rights (herein "patent rights"). DMTF makes
23 // no representations to users of the standard as to the existence
24 // of such rights, and is not responsible to recognize, disclose, or
25 // identify any or all such third party patent right, owners or
26 // claimants, nor for any incomplete or inaccurate identification or
27 // disclosure of such rights, owners or claimants. DMTF shall have no
28 // liability to any party, in any manner or circumstance, under any
29 // legal theory whatsoever, for failure to recognize, disclose, or
30 // identify any such third party patent rights, or for such party's
31 // reliance on the standard or incorporation thereof in its product,
32 // protocols or testing procedures. DMTF shall have no liability to
33 // any party implementing such standard, whether such implementation
34 // is foreseeable or not, nor to any patent owner or claimant, and shall
35 // have no liability or responsibility for costs or losses incurred if
36 // a standard is withdrawn or modified after publication, and shall be
37 // indemnified and held harmless by any party implementing the
38 // standard from any and all claims of infringement by a patent owner
39 // for such implementations.
40 //
41 // For information about patents held by third-parties which have
42 // notified the DMTF that, in their opinion, such patent may relate to
43 a.dunfey 1.1 // or impact implementations of DMTF standards, visit
44 // http://www.dmtf.org/about/policies/disclosures.php.
45 //#pragma inLine
46 // ===================================================================
47 // Description: The Physical Model defines modeling concepts related
48 // to actual boxes and packaging. This file defines the
49 // concepts related to sets of physical entities that are
50 // replaced at the same time/together, and capacity.
51 //
52 // The object classes below are listed in an order that
53 // avoids forward references. Required objects, defined
54 // by other working groups, are omitted.
55 // ==================================================================
56 // Change Log for v2.9 Preliminary
57 // CR1263 - Add DDR-2 to MemoryCapacity.MemoryType
58 // CR1387 - Deprecate ParticipatesInSet
59 //
60 // Change Log for v2.8
61 // CR1094 - Update subclassing of replacementset
62 //
63 // Change Log for v2.7
64 a.dunfey 1.1 // CR901 - Clarify the description for PhysicalCapacity
65 // ==================================================================
66
67 #pragma locale ("en_US")
68
69
70 // ==================================================================
71 // ReplacementSet
72 // ==================================================================
73 [Version ( "2.8.0" ), Description (
74 "The ReplacementSet class aggregates PhysicalElements that must "
75 "be 'replaced' or 'FRUed' together. For example, when replacing "
76 "a memory card, the component memory chips could be removed and "
77 "replaced as well. Or, a set of memory chips may be specified "
78 "to be replaced or upgraded together using this association.")]
79 class CIM_ReplacementSet : CIM_Collection {
80
81 [Key, Description (
82 "Name is a free-form string defining a label for the "
83 "ReplacementSet. It is the key for the object."),
84 MaxLen ( 256 )]
85 a.dunfey 1.1 string Name;
86 };
87
88
89 // ==================================================================
90 // ParticipatesInSet
91 // ==================================================================
92 [Association, Deprecated { "CIM_MemberOfCollection" }, Aggregation,
93 Version ( "2.8.1000" ), Description (
94 "ParticipatesInSet indicates which PhysicalElements are "
95 "replaced together. Since ReplacementSet was updated to "
96 "subclass from CIM_Collection, this separate association of "
97 "members into the set is no longer needed. It is deprecated in "
98 "lieu of MemberOfCollection.")]
99 class CIM_ParticipatesInSet {
100
101 [Deprecated { "CIM_MemberOfCollection.Collection" }, Key,
102 Aggregate, Description (
103 "The ReplacementSet.")]
104 CIM_ReplacementSet REF Set;
105
106 a.dunfey 1.1 [Deprecated { "CIM_MemberOfCollection.Member" }, Key,
107 Description (
108 "The PhysicalElement which should be replaced with other "
109 "Elements, as a Set.")]
110 CIM_PhysicalElement REF Element;
111 };
112
113 // ==================================================================
114 // PhysicalCapacity
115 // ==================================================================
116 [Abstract, Version ( "2.7.0" ), Description (
117 "PhysicalCapacity is an abstract class describing a "
118 "PhysicalElement's minimum/maximum requirements and ability to "
119 "support different types of hardware. For example, minimum and "
120 "maximum memory requirements can be modeled as a subclass of "
121 "CIM_PhysicalCapacity. \n"
122 "\n"
123 "Note that the items described in subclasses of "
124 "PhysicalCapacity, for example the class ConfigurationCapacity, "
125 "are either directly PhysicalElements (such as I/O slots or "
126 "storage library magazines) or closely associated to "
127 a.dunfey 1.1 "PhysicalElements via the Realizes relationship (i.e., "
128 "LogicalDevices such as batteries or processors).")]
129 class CIM_PhysicalCapacity : CIM_ManagedElement {
130
131 [Description (
132 "The Name property defines the label by which the Physical "
133 "Capacity object is known. When subclassed, the Name "
134 "property can be overridden to be a Key property."),
135 MaxLen ( 256 )]
136 string Name;
137 };
138
139
140 // =================================================================
141 // ElementCapacity
142 // =================================================================
143 [Association, Version ( "2.6.0" ), Description (
144 "ElementCapacity associates a PhysicalCapacity object with one "
145 "or more PhysicalElements. It serves to associate a description "
146 "of min/max hardware requirements or capabilities (stored as a "
147 "kind of PhysicalCapacity), with the PhysicalElements being "
148 a.dunfey 1.1 "described.")]
149 class CIM_ElementCapacity {
150
151 [Key, Description (
152 "PhysicalCapacity describes the minimum and maximum "
153 "requirements, and ability to support different types of "
154 "hardware for a PhysicalElement.")]
155 CIM_PhysicalCapacity REF Capacity;
156
157 [Key, Min ( 1 ), Description (
158 "The PhysicalElement being described.")]
159 CIM_PhysicalElement REF Element;
160 };
161
162
163 // ==================================================================
164 // MemoryCapacity
165 // ==================================================================
166 [Version ( "2.9.0" ), Description (
167 "MemoryCapacity describes the type of Memory that can be "
168 "installed on a PhysicalElement and its minimum/maximum "
169 a.dunfey 1.1 "configurations. Information on what memory is currently "
170 "'installed', versus an Element's min/max requirements, is "
171 "located in instances of the PhysicalMemory class.")]
172 class CIM_MemoryCapacity : CIM_PhysicalCapacity {
173
174 [Key, Override ( "Name" ), Description (
175 "The inherited Name serves as a part of the MemoryCapacity "
176 "object key.")]
177 string Name;
178
179 [Key, Description (
180 "The type of memory. This is a part of the object key. "
181 "Values correspond to the list of possible memory types in "
182 "the PhysicalMemory class."),
183 //#pragma inLine ("Includes\MemoryType.inc")
184 ValueMap { "0", "1", "2", "3", "4", "5", "6", "7", "8", "9",
185 "10", "11", "12", "13", "14", "15", "16", "17", "18", "19",
186 "20", "21", "22", "23..32567", "32568..65535" },
187 Values { "Unknown", "Other", "DRAM", "Synchronous DRAM",
188 "Cache DRAM", "EDO", "EDRAM", "VRAM", "SRAM", "RAM",
189 //10
190 a.dunfey 1.1 "ROM", "Flash", "EEPROM", "FEPROM", "EPROM", "CDRAM",
191 "3DRAM", "SDRAM", "SGRAM", "RDRAM",
192 // 20
193 "DDR", "DDR-2", "BRAM", "DMTF Reserved", "Vendor Reserved" },
194 //#pragma inLine
195 ModelCorrespondence { "CIM_PhysicalMemory.MemoryType" }]
196 uint16 MemoryType;
197
198 [Description (
199 "Minimum amount of memory, in Kbytes, that is needed for the "
200 "associated PhysicalElement to operate correctly."),
201 Units ( "KiloBytes" )]
202 uint64 MinimumMemoryCapacity;
203
204 [Description (
205 "Maximum amount of memory, in Kbytes, that can be supported "
206 "by the associated PhysicalElement."),
207 Units ( "KiloBytes" )]
208 uint64 MaximumMemoryCapacity;
209 };
210
211 a.dunfey 1.1
212 // ===================================================================
213 // ConfigurationCapacity
214 // ===================================================================
215 [Version ( "2.6.0" ), Description (
216 "ConfigurationCapacity provides information on the minimum and "
217 "maximum numbers of power supplies, fans, disk drives, etc. "
218 "that can be connected to or placed on/into a PhysicalElement "
219 "(and the number that must be connected/added/removed at a "
220 "time). The PhysicalElement whose configuration is described is "
221 "identified using the ElementCapacity association, inherited "
222 "from PhysicalCapacity. The object whose capacities are "
223 "indicated (ie, the power supply or fan) is identified in the "
224 "ObjectType property of this class. Since the same min/max "
225 "configurations can apply to multiple instances, this class is "
226 "not defined as 'weak'. \n"
227 "Examples of the use of the ConfigurationCapacity class are to "
228 "describe that a 'control unit' Chassis may be connected to (at "
229 "most) 4 other I/O chassis, or to describe what a "
230 "StorageLibrary's cabinet may contain. Continuing the latter "
231 "example, a particular StorageLibrary's cabinet might hold a "
232 a.dunfey 1.1 "minimum of 3 and a maximum of 9 TapeDrives, and a minimum of "
233 "88 and a maximum of 264 StorageMediaLocations (\"Slots\"). "
234 "This information would be described in two instances of "
235 "ConfigurationCapacity, both associated to the StorageLibrary's "
236 "PhysicalPackage. \n"
237 "This class does NOT represent the tradeoffs that are likely to "
238 "be required of one resource for another. It simply represents "
239 "capacities. In the case of the StorageLibrary, there may be "
240 "only 2 valid configurations - 9 TapeDrives with 88 Slots, or 3 "
241 "TapeDrives with 264 Slots. This class only conveys that 'up "
242 "to' 9 Drives and 'up to' 264 slots may be available and are "
243 "supported.")]
244 class CIM_ConfigurationCapacity : CIM_PhysicalCapacity {
245
246 [Key, Override ( "Name" ), Description (
247 "The inherited Name serves as a part of the Configuration "
248 "Capacity object key.")]
249 string Name;
250
251 [Key, Description (
252 "The type of object (power supply, fan, disk drive, ...) "
253 a.dunfey 1.1 "whose capacities are indicated. This information is part of "
254 "the class' key."),
255 ValueMap { "0", "1", "2", "3", "4", "5", "6", "7", "8", "9",
256 "10", "11", "12", "13", "14", "15", "16", "17", "18", "19",
257 "20", "21", "22", "23", "24" },
258 Values { "Other", "Processors", "Power Supplies", "Fans",
259 "Batteries", "I/O Slots", "Memory Slots",
260 "MediaAccessDevices (Drives)", "StorageMediaLocation Slots",
261 "StorageMediaLocation Magazines",
262 // 10
263 "StorageMediaLocation Panels",
264 "StorageMediaLocation InterLibrary Ports",
265 "StorageMediaLocation Limited Access Ports", "Doors",
266 "MediaTransferDevice Pickers",
267 "MediaTransferDevice Changers", "LabelReaders",
268 "Contained Chassis", "Connected Chassis", "Connected Frames",
269 // 20
270 "Front Side I/O Slots", "Back Side I/O Slots",
271 "Cache Memory", "NVS Memory", "Volatile Memory" },
272 ModelCorrespondence {
273 "CIM_ConfigurationCapacity.OtherTypeDescription" }]
274 a.dunfey 1.1 uint16 ObjectType;
275
276 [Description (
277 "A string describing the object type - used when the "
278 "ObjectType property is set to 0 (\"Other\"). OtherType "
279 "Description should be set to NULL when ObjectType is any "
280 "value other than 0."),
281 MaxLen ( 64 ),
282 ModelCorrespondence { "CIM_ConfigurationCapacity.ObjectType" }]
283 string OtherTypeDescription;
284
285 [Description (
286 "Minimum number of Elements of type, ObjectType, that must "
287 "be installed.")]
288 uint64 MinimumCapacity;
289
290 [Description (
291 "Maximum number of Elements of type, ObjectType, that may be "
292 "installed.")]
293 uint64 MaximumCapacity;
294
295 a.dunfey 1.1 [Description (
296 "Increment in which Elements must be added or removed.")]
297 uint32 Increment;
298 };
299
300
301 // ===================================================================
302 // end of file
303 // ===================================================================
|
Return to
Physical_Misc.mof
CVS log
Up to [Pegasus] / pegasus / Schemas / CIMPrelim291