Bug 1128913

Summary: Traffic Control Documentation.
Product: OpenShift Container Platform Reporter: Eric Rich <erich>
Component: DocumentationAssignee: Timothy <tpoitras>
Status: CLOSED DEFERRED QA Contact: brice <bfallonf>
Severity: low Docs Contact:
Priority: low    
Version: 2.1.0CC: bfallonf, bleanhar, erich, jhonce, jokerman, libra-onpremise-devel, mmccomas, mpatel, tpoitras, vbatts
Target Milestone: ---Flags: tpoitras: needinfo-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 22863, Administration Guide-2-1.0 Build Date: 08-08-2014 13:44:28 Topic IDs: 23616-632055 [Specified]
Last Closed: 2016-07-13 14:17:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Rich 2014-08-11 20:14:31 UTC
Title: Capacity Planning and Districts

Describe the issue:

Need documentation on Limiting / using Traffic Control. How to manage application using Traffic Control as well as how to set limitation in the node profile. 

Suggestions for improvement:

At a bare minimum explain how to enable / disable this feature of OpenShift on the nodes. 

# To enable bandwidth settings in resource_limits.conf this can be set to true.
# Changing this value requires restarting the MCollective service on the Node
# as well as starting the openshift-tc service.
TRAFFIC_CONTROL_ENABLED=false

Additional information: