![]() ![]() |
![]() |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network / CIM_NextService.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_NextService // ================================================================== [Association, Version ( "2.7.0" ), UMLPackagePath ( "CIM::Network::QoS" ), Description ( "NextService establishes a predecessor-successor relationship " "between two ConditioningService objects. This association is " "used to indicate the sequence of ConditioningServices required " "to process a particular type of traffic. \n" "\n" "Instances describe the various relationships between different " "ConditioningServices (such as classifiers, meters, droppers, " "etc.) that are used collectively to condition traffic. Both " "one-to-one and more complicated fan-in and/or fan-out " "relationships can be described. The Conditioning Services may " "feed one another directly, or they may be mapped to multiple " "\'next\' Services based on the characteristics of the packet." )] class CIM_NextService { [Key, Description ( "The preceding ConditioningService, \'earlier\' in the " "processing sequence for a packet." )] CIM_ConditioningService REF PrecedingService; [Key, Description ( "The \'next\' or following ConditioningService." )] CIM_ConditioningService REF FollowingService; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |