README
¶
cache-config
Traffic Control cache configuration is done via the t3c
app and its ecosystem of sub-apps.
These are provided in the RPM trafficcontrol-cache-config
.
To apply Traffic Control configuration and changes to caches, users will typically run t3c
periodically via cron
or some other system automation mechanism. See t3c.
The t3c
app is an ecosystem of apps that work together, similar to git
and other Linux tools. The t3c
app itself has commands to proxy the other apps, as well as a mode to generate and apply the entire configuration.
Documentation
Each sub-command provides a README.md file. If your system has Pandoc and GNU
make
and date
(UNIX date
untested, might work - UNIX make
definitely
won't), they can also be transformed into Linux/UNIX "manual pages" using
make
(or explicitly make man
) and reStructuredText documentation using
make rst
.
Directories
¶
Path | Synopsis |
---|---|
toreq
toreq implements a Traffic Ops client for features in the latest version.
|
toreq implements a Traffic Ops client for features in the latest version. |
toreq/toreqold
Package toreqold calls the previous Traffic Ops API major version.
|
Package toreqold calls the previous Traffic Ops API major version. |
toreq/torequtil
torequtil has utility functions used by toreq and toreqnew which don't require the Traffic Ops client, and thus can be shared.
|
torequtil has utility functions used by toreq and toreqnew which don't require the Traffic Ops client, and thus can be shared. |
testing
|
|
ort-tests/config
Package config provides tools to load and validate configuration data for the t3c tests.
|
Package config provides tools to load and validate configuration data for the t3c tests. |
ort-tests/tcdata
Package tcdata provides dynamic loading/unloading of ATC objects to/from a Traffic Ops instance.
|
Package tcdata provides dynamic loading/unloading of ATC objects to/from a Traffic Ops instance. |