summaryrefslogtreecommitdiffstats
path: root/Schemas/CIM228/DMTF/Device/CIM_LogicalDiskBasedOnPartition.mof
diff options
context:
space:
mode:
authorvenkat.puvvada <venkat.puvvada>2011-02-17 14:16:11 +0000
committervenkat.puvvada <venkat.puvvada>2011-02-17 14:16:11 +0000
commit4681c0f594d929037d507ca37befaf25088dc309 (patch)
treece98396f47a4aea22651ca5d83722e0eb7b2163b /Schemas/CIM228/DMTF/Device/CIM_LogicalDiskBasedOnPartition.mof
parent366071f7bcb2b998f9b940b0913c6438c1064ddc (diff)
downloadtog-pegasus-4681c0f594d929037d507ca37befaf25088dc309.zip
tog-pegasus-4681c0f594d929037d507ca37befaf25088dc309.tar.gz
tog-pegasus-4681c0f594d929037d507ca37befaf25088dc309.tar.xz
BUG#: 8931
TITLE: Add Schema 2.28 to the cvs DESCRIPTION:
Diffstat (limited to 'Schemas/CIM228/DMTF/Device/CIM_LogicalDiskBasedOnPartition.mof')
-rw-r--r--Schemas/CIM228/DMTF/Device/CIM_LogicalDiskBasedOnPartition.mof36
1 files changed, 36 insertions, 0 deletions
diff --git a/Schemas/CIM228/DMTF/Device/CIM_LogicalDiskBasedOnPartition.mof b/Schemas/CIM228/DMTF/Device/CIM_LogicalDiskBasedOnPartition.mof
new file mode 100644
index 0000000..115cd2c
--- /dev/null
+++ b/Schemas/CIM228/DMTF/Device/CIM_LogicalDiskBasedOnPartition.mof
@@ -0,0 +1,36 @@
+// Copyright (c) 2005 DMTF. All rights reserved.
+// <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
+// qualifier values to CIM Schema.</change>
+// ==================================================================
+// CIM_LogicalDiskBasedOnPartition
+// ==================================================================
+ [Association, Version ( "2.6.0" ),
+ UMLPackagePath ( "CIM::Device::StorageExtents" ),
+ Description (
+ "LogicalDisks can be BasedOn a DiskPartition. For example, a "
+ "personal computer\'s C: drive may be located on a Partition on "
+ "local PhysicalMedia. In this association of LogicalDisks to "
+ "Partitions, note that the cardinality of the Antecedent, Disk "
+ "Partition, is Max (1). This dictates that a LogicalDisk can "
+ "not span more than one Partition. However, there are cases "
+ "where this is true. When it occurs, the LogicalDisk is really "
+ "based on some kind of RAID configuration (for example, a "
+ "mirror or stripe set). In these scenarios, the LogicalDisk is "
+ "more correctly BasedOn a StorageVolume. To prevent incorrectly "
+ "using the LogicalDiskBasedOnPartition association, the Max (1) "
+ "qualifier was put on the Antecedent reference to the "
+ "DiskPartition." )]
+class CIM_LogicalDiskBasedOnPartition : CIM_LogicalDiskBasedOnExtent {
+
+ [Override ( "Antecedent" ),
+ Max ( 1 ),
+ Description ( "The DiskPartition." )]
+ CIM_DiskPartition REF Antecedent;
+
+ [Override ( "Dependent" ),
+ Description (
+ "The LogicalDisk which is built on the StorageExtent." )]
+ CIM_LogicalDisk REF Dependent;
+
+
+};