Update docs from commit 2ffffb396a203fd75d8864e7ca779a2e61997357
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/commit/0a296045 Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/tree/0a296045 Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/diff/0a296045 Branch: refs/heads/asf-site Commit: 0a296045f521b78b24e7115ff04011a0ee762337 Parents: 48a79c8 Author: jenkins <bui...@apache.org> Authored: Thu Mar 15 16:26:49 2018 +0000 Committer: jenkins <bui...@apache.org> Committed: Thu Mar 15 16:26:49 2018 +0000 ---------------------------------------------------------------------- docs/master/_sources/overview/traffic_ops.rst.txt | 2 +- docs/master/overview/traffic_ops.html | 2 +- docs/master/searchindex.js | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0a296045/docs/master/_sources/overview/traffic_ops.rst.txt ---------------------------------------------------------------------- diff --git a/docs/master/_sources/overview/traffic_ops.rst.txt b/docs/master/_sources/overview/traffic_ops.rst.txt index 7053c7b..ad026ce 100644 --- a/docs/master/_sources/overview/traffic_ops.rst.txt +++ b/docs/master/_sources/overview/traffic_ops.rst.txt @@ -19,7 +19,7 @@ Traffic Ops =========== Traffic Ops is the tool for administration (configuration and monitoring) of all components in a Traffic Control CDN. The CDN administrator uses Traffic Ops to manage servers, cache groups, delivery services, etc. In many cases, a configuration change requires propagation to several, or even all, caches and only explicitly after or before the same change propagates to Traffic Router. Traffic Ops takes care of this required consistency between the different components and their configuration. Traffic Ops exposes its data through a series of HTTP APIs and has a user interface that is interactive and viewable using a standard web browser. -Traffic Ops uses a MySQL or PostgreSQL database to store the configuration information, and the `Mojolicious framework <http://mojolicio.us/>`_ to generate the user interface and APIs. Not all configuration data is in this database however; for sensitive data, like SSL private keys or token based authentication shared secrets, a separate key-value store is used, allowing the operator to harden the server that runs this key-value store better from a security perspective (i.e only allow Traffic Ops access it with a cert). The Traffic Ops server, by design, needs to be accessible from all the other servers in the Traffic Control CDN. +Traffic Ops uses a PostgreSQL database to store the configuration information, and the `Mojolicious framework <http://mojolicio.us/>`_ and `Go https://golang.org/`_ to generate APIs used by the Traffic Portal. Not all configuration data is in this database however; for sensitive data like SSL private keys or token based authentication shared secrets, a separate key-value store is used, allowing the operator to harden the server that runs this key-value store better from a security perspective (i.e only allow Traffic Ops access it with a cert). The Traffic Ops server, by design, needs to be accessible from all the other servers in the Traffic Control CDN. Traffic Ops generates all the application specific configuration files for the caches and other servers. The caches and other servers check in with Traffic Ops at a regular interval (default 15 minutes) to see if updated configuration files require application. http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0a296045/docs/master/overview/traffic_ops.html ---------------------------------------------------------------------- diff --git a/docs/master/overview/traffic_ops.html b/docs/master/overview/traffic_ops.html index d6ec171..124da24 100644 --- a/docs/master/overview/traffic_ops.html +++ b/docs/master/overview/traffic_ops.html @@ -199,7 +199,7 @@ <div class="section" id="traffic-ops"> <h1>Traffic Ops<a class="headerlink" href="#traffic-ops" title="Permalink to this headline">¶</a></h1> <p>Traffic Ops is the tool for administration (configuration and monitoring) of all components in a Traffic Control CDN. The CDN administrator uses Traffic Ops to manage servers, cache groups, delivery services, etc. In many cases, a configuration change requires propagation to several, or even all, caches and only explicitly after or before the same change propagates to Traffic Router. Traffic Ops takes care of this required consistency between the different components and their configuration. Traffic Ops exposes its data through a series of HTTP APIs and has a user interface that is interactive and viewable using a standard web browser.</p> -<p>Traffic Ops uses a MySQL or PostgreSQL database to store the configuration information, and the <a class="reference external" href="http://mojolicio.us/";>Mojolicious framework</a> to generate the user interface and APIs. Not all configuration data is in this database however; for sensitive data, like SSL private keys or token based authentication shared secrets, a separate key-value store is used, allowing the operator to harden the server that runs this key-value store better from a security perspective (i.e only allow Traffic Ops access it with a cert). The Traffic Ops server, by design, needs to be accessible from all the other servers in the Traffic Control CDN.</p> +<p>Traffic Ops uses a PostgreSQL database to store the configuration information, and the <a class="reference external" href="http://mojolicio.us/";>Mojolicious framework</a> and <a href="#id1"><span class="problematic" id="id2">`Go https://golang.org/`_</span></a> to generate APIs used by the Traffic Portal. Not all configuration data is in this database however; for sensitive data like SSL private keys or token based authentication shared secrets, a separate key-value store is used, allowing the operator to harden the server that runs this key-value store better from a security perspective (i.e only allow Traffic Ops access it with a cert). The Traffic Ops server, by design, needs to be accessible from all the other servers in the Traffic Control CDN.</p> <p>Traffic Ops generates all the application specific configuration files for the caches and other servers. The caches and other servers check in with Traffic Ops at a regular interval (default 15 minutes) to see if updated configuration files require application.</p> <p>Traffic Ops also runs a collection of periodic checks to determine the operational readiness of the caches. These periodic checks are customizable by the Traffic Ops admin using extensions.</p> <p>Traffic Ops is in the process of migrating from Perl to Go, and currently runs as two applications. The Go application serves all endpoints which have been rewritten in the Go language, and transparently proxies all other requests to the old Perl application. Both applications are installed by the RPM, and both run as a single service. When the project has fully migrated to Go, the Perl application will be removed, and the RPM and service will consist solely of the Go application.</p>
