Return to CIM_QoSService.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network / CIM_QoSService.mof
(download)
Revision: 1.1, Tue Jan 24 13:50:20 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_QoSService // ================================================================== [Version ( "2.7.0" ), UMLPackagePath ( "CIM::Network::QoS" ), Description ( "This is a concrete class that represents the ability to " "conceptualize a QoS service as a set of coordinated " "sub-services. This enables the network administrator to map " "business rules to the network, and the network designer to " "engineer the network such that it can provide different " "functions for different traffic streams. \n" "\n" "This class has two main purposes. First, it serves as a common " "base class for defining various sub-services that are needed " "to build higher-level QoS services. Second, it serves as a way " "to consolidate relationships between different types of QoS " "services and different types of ConditioningServices. \n" "\n" "For example, Gold Service may be defined as a QoSService which " "aggregates two other QoSServices together. Each of these " "\'other\' QoSServices could be DiffServServices - one " "representing the servicing of very high demand packets " "(instantiated as a DiffServService directly), and one " "representing the service given to most of the packets " "(instantiated as an AFService). The high demand " "DiffServService instance would use QoSConditioning SubService " "to aggregate together the necessary classifiers to indicate " "which traffic it applies to, the appropriate meters for " "contract limits, the marker to mark the EF PHB in the packets, " "and the queuing-related services. The AFService instance would " "similarly use QoSConditioning SubService to aggregate its " "classifiers, meters, the several markers used to mark the " "different AF PHBs in the packets, and the queuing-related " "services needed to deliver the packet treatment." )] class CIM_QoSService : CIM_Service { };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |