Administrator’s Guide¶
Traffic Control is distributed in source form for the developer, but also as a binary package. This guide details how to install and configure a Traffic Control CDN using the binary packages, as well as how to perform common operations running a CDN.
When installing a complete CDN from scratch, a sample recommended order is:
- Traffic Ops
- Traffic Vault (Riak)
- Traffic Monitor
- Apache Traffic Server Mid-Tier Caches
- Apache Traffic Server Edge Caches
- Traffic Router
- Traffic Stats
- Traffic Portal
Once everything is installed, you will need to configure the servers to talk to each other. You will also need Origin server(s), which the Mid-Tier Cache(s) get content from. An Origin server is simply an HTTP(S) server which serves the content you wish to cache on the CDN.
- Traffic Ops - Installing
- Traffic Ops - Default Profiles
- Traffic Ops - Migrating from 1.x to 2.x
- Traffic Ops - Migrating from 2.0 to 2.2
- Traffic Ops - Configuring
- Traffic Ops - Using
- The Traffic Ops Menu
- Health
- Server
- Delivery Service
- Delivery Service Types
- Federations
- Header Rewrite Options and DSCP
- Token Based Authentication
- Parent Selection
- Qstring Handling
- Multi Site Origin
- Traffic Router Profile
- Regex Remap Expression
- Delivery Service Regexp
- Static DNS Entries
- Server Assignments
- The Coverage Zone File and ASN Table
- The Deep Coverage Zone File
- Parameters and Profiles
- Tools
- Invalidate Content
- Manage DNSSEC Keys
- Managing Traffic Ops Extensions
- Traffic Portal Administration
- Traffic Portal - Using
- Traffic Monitor Administration (Legacy)
- Traffic Monitor Administration
- Traffic Router Administration
- Traffic Stats Administration
- Traffic Server Administration
- Traffic Vault Administration
- Quick How To Guides