![]() ![]() |
![]() |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Application / CIM_FRUIncludesSoftwareFeature.mof
(download)
Revision: 1.1, Tue Jan 24 13:49:56 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_FRUIncludesSoftwareFeature // ================================================================== [Association, Aggregation, Version ( "2.6.0" ), UMLPackagePath ( "CIM::Application::DeploymentModel" ), Description ( "The FRUIncludesSoftwareFeature association identifies the " "SoftwareFeature(s) packaged with a particular FRU. A common " "usage is to determine whether the FRU is compatible with a " "hardware/software platform. In order to determine this, the " "following conditions need to be verified: \n" "(1) Is the physical package of the FRU compatible with the " "slots or equivalent packaging of the hardware? \n" "(2) Are there any physical constraints (such as power " "consumption) that prevent the FRU from being installed? \n" "(3) Are the SoftwareFeatures packaged with the FRU compatiable " "with the underlying operating system and other software " "already installed/to be installed on the platform? \n" "This latter question can be answered by first checking if an " "instance of FRUIncludesSoftwareFeature exists. If it does, " "then the compatibility of each SoftwareFeature can be " "determined by evaluating the Check classes for the Software " "Elements that are part of the Feature (found by traversing the " "association, SoftwareFeatureSoftwareElements). For example, " "there might be a SoftwareElementVersionCheck that declares " "that a SoftwareElement (of the FRU\'s Software Feature) is not " "compatible with current software." )] class CIM_FRUIncludesSoftwareFeature { [Key, Aggregate, Max ( 1 ), Description ( "The field replaceable unit." )] CIM_FRU REF FRU; [Key, Description ( "The SoftwareFeature which is included in the FRU and " "whose SoftwareElements should be evaluated." )] CIM_SoftwareFeature REF Component; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |