Return to CIM_LogicalDiskBasedOnPartition.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Device |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Device / CIM_LogicalDiskBasedOnPartition.mof
(download)
Revision: 1.1, Tue Jan 24 13:50:08 2012 UTC (12 years, 5 months ago) by marek Branch: MAIN CVS Tags: preBug9676, postBug9676, TASK-TASK_PEP362_RestfulService_branch-root, TASK-TASK_PEP362_RestfulService_branch-merged_out_from_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_to_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_from_branch, TASK-TASK_PEP362_RestfulService_branch-branch, TASK-PEP362_RestfulService-root, TASK-PEP362_RestfulService-merged_out_to_branch, TASK-PEP362_RestfulService-merged_out_from_trunk, TASK-PEP362_RestfulService-merged_in_to_trunk, TASK-PEP362_RestfulService-merged_in_from_branch, TASK-PEP362_RestfulService-branch, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, RELEASE_2_14_1, RELEASE_2_14_0-RC2, RELEASE_2_14_0-RC1, RELEASE_2_14_0, RELEASE_2_14-root, RELEASE_2_14-branch, RELEASE_2_13_0-RC2, RELEASE_2_13_0-RC1, RELEASE_2_13_0-FC, RELEASE_2_13_0, RELEASE_2_13-root, RELEASE_2_13-branch, RELEASE_2_12_1-RC1, RELEASE_2_12_1, RELEASE_2_12_0-RC1, RELEASE_2_12_0-FC, RELEASE_2_12_0, RELEASE_2_12-root, RELEASE_2_12-branch, HEAD, CIMRS_WORK_20130824 Branch point for: TASK-PEP317_pullop-branch BUG#:9155 TITLE: Upgrade Pegasus to Include the CIM 2.31 Schema in CVS DESCRIPTION: |
// 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; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |