Return to CIM_ParticipatingCS.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / System |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / System / CIM_ParticipatingCS.mof
(download)
Revision: 1.1, Tue Jan 24 13:50:33 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_ParticipatingCS // ================================================================== [Association, Version ( "2.6.0" ), UMLPackagePath ( "CIM::System::SystemElements" ), Description ( "A Cluster is composed of two or more ComputerSystems, " "operating together. A ComputerSystem may participate in " "multiple Clusters. \n" "\n" "When first establishing or bringing up a Cluster, only one " "ComputerSystem may be defined as participating in it. " "Therfore, the cardinality of the association for the " "ComputerSystem reference is Min (1)." )] class CIM_ParticipatingCS : CIM_Dependency { [Override ( "Antecedent" ), Min ( 1 ), Description ( "The ComputerSystem which participates in the Cluster." )] CIM_ComputerSystem REF Antecedent; [Override ( "Dependent" ), Description ( "The Cluster." )] CIM_Cluster REF Dependent; [Description ( "StateOfNode indicates the condition of the participating " "ComputerSystem in the Cluster. For example, one value is " "\"Joining\" (2)." ), ValueMap { "0", "1", "2", "3", "4", "5", "6" }, Values { "Unknown", "Other", "Joining", "Paused", "Available", "Unavailable", "Degraded" }] uint16 StateOfNode; [Description ( "RoleOfNode indicates whether the Cluster nodes are peers " "(value = 2), connected in a master-slave/primary- " "secondary relationship (values = 3 for primary, 4 for " "secondary), available in a standby configuration (5) or " "of some other (1) or unknown (0) relationship. In a " "System/390 environment, the nodes are identified as " "\"Base Plex\" (value=6) or \"Enhanced Plex\" (value=7)." ), ValueMap { "0", "1", "2", "3", "4", "5", "6", "7" }, Values { "Unknown", "Other", "Peer", "Primary", "Secondary", "Standby", "Base Plex", "Enhanced Plex" }] uint16 RoleOfNode; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |