Return to CIM_ConditioningService.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network / CIM_ConditioningService.mof
(download)
Revision: 1.1, Tue Jan 24 13:50:19 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_ConditioningService // ================================================================== [Version ( "2.7.0" ), UMLPackagePath ( "CIM::Network::QoS" ), Description ( "ConditioningService represents the ability to define how " "traffic is conditioned in the data-forwarding path of a " "device. The subclasses of ConditioningService define the " "particular types of conditioning that are done. These are the " "services performed by a classifier, a meter, a marker, a " "dropper, a queue, and a scheduler. Other, more sophisticated " "types of conditioning may be defined in the future. \n" "\n" "ConditioningService is a concrete class because its superclass " "(ForwardingService) is concrete. While this class can be " "instantiated, an instance of it does not accomplish anything, " "because the nature of the conditioning, and the parameters " "that control it, are specified only in the subclasses of " "ConditioningService. \n" "\n" "Two associations in which ConditioningService participates are " "critical to its usage in QoS - QoSConditioningSubService and " "NextService. QoSConditioningSubService aggregates " "ConditioningServices into a particular QoS service (such as " "AF), to describe the specific conditioning functionality that " "underlies that QoSService in a particular device. NextService " "indicates the subsequent conditioning service(s) for different " "traffic streams." )] class CIM_ConditioningService : CIM_Service { [Deprecated { "CIM_EnabledLogicalElement.EnabledState" }, Description ( "This property is a boolean that, if TRUE, signifies that " "one or more conditioning functions can be performed on " "traffic encountered by this ConditioningService. This " "allows one or more ConditioningServices to be enabled or " "disabled to provide different types of conditioning for " "traffic. Enabled is deprecated in lieu of a similar (but " "more generally and completely defined) property which is " "inherited." )] boolean Enabled; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |