http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/5521f214/docs/latest/admin/traffic_ops_config.html ---------------------------------------------------------------------- diff --git a/docs/latest/admin/traffic_ops_config.html b/docs/latest/admin/traffic_ops_config.html index e20b968..9c86bbb 100644 --- a/docs/latest/admin/traffic_ops_config.html +++ b/docs/latest/admin/traffic_ops_config.html @@ -7,7 +7,7 @@ <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Configuring Traffic Ops — Traffic Control 1.8.1 documentation </title> + <title>Configuring Traffic Ops — Traffic Control 1.8-dev documentation </title> @@ -33,10 +33,7 @@ - <link rel="index" title="Index" - href="../genindex.html"/> - <link rel="search" title="Search" href="../search.html"/> - <link rel="top" title="Traffic Control 1.8.1 documentation" href="../index.html"/> + <link rel="top" title="Traffic Control 1.8-dev documentation" href="../index.html"/> <link rel="up" title="Administratorâs Guide" href="index.html"/> <link rel="next" title="Using Traffic Ops" href="traffic_ops_using.html"/> <link rel="prev" title="Installing Traffic Ops" href="traffic_ops_install.html"/> @@ -111,6 +108,7 @@ <li class="toctree-l2"><a class="reference internal" href="traffic_ops_extensions.html">Managing Traffic Ops Extensions</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_portal.html">Traffic Portal Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_monitor.html">Traffic Monitor Administration</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_monitor_golang.html">Traffic Monitor Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_router.html">Traffic Router Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_stats.html">Traffic Stats Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_server.html">Traffic Server Administration</a></li> @@ -125,6 +123,7 @@ <li class="toctree-l2"><a class="reference internal" href="../development/traffic_portal.html">Traffic Portal</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_router.html">Traffic Router</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_monitor.html">Traffic Monitor</a></li> +<li class="toctree-l2"><a class="reference internal" href="../development/traffic_monitor_golang.html">Traffic Monitor Golang</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_stats.html">Traffic Stats</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_server.html">Traffic Server</a></li> </ul> @@ -162,14 +161,14 @@ <div class="rst-content"> <div role="navigation" aria-label="breadcrumbs navigation"> <ul class="wy-breadcrumbs"> - <li><a href="../index.html">Traffic Control 1.8.1</a> »</li> + <li><a href="../index.html">Traffic Control 1.8-dev</a> »</li> <li><a href="index.html">Administrator’s Guide</a> »</li> <li>Configuring Traffic Ops</li> <li class="wy-breadcrumbs-aside"> - <a href="../_sources/admin/traffic_ops_config.rst.txt" rel="nofollow"> View page source</a> + <a href="../_sources/admin/traffic_ops_config.txt" rel="nofollow"> View page source</a> </li> </ul> @@ -199,7 +198,7 @@ </div> <div class="section" id="profile-parameters"> <span id="rl-param-prof"></span><h2>Profile Parameters<a class="headerlink" href="#profile-parameters" title="Permalink to this headline">¶</a></h2> -<p>Many of the settings for the different servers in a Traffic Control CDN are controlled by parameters in the parameter view of Traffic Ops. Parameters are grouped in profiles and profiles are assigned to a server. For a typical cache there are hundreds of configuration settings to apply. The Traffic Ops parameter view contains the defined settings. To make life easier, Traffic Ops allows for duplication, comparison, import and export of Profiles. Traffic Ops also has a “Global profile” - the parameters in this profile are going to be applied to all servers in the Traffic Ops instance, or apply to Traffic Ops themselves. These parameters are:</p> +<p>Many of the settings for the different servers in a Traffic Control CDN are controlled by parameters in the parameter view of Traffic Ops. Parameters are grouped in profiles and profiles are assigned to a server or a deliveryservice. For a typical cache there are hundreds of configuration settings to apply. The Traffic Ops parameter view contains the defined settings. To make life easier, Traffic Ops allows for duplication, comparison, import and export of Profiles. Traffic Ops also has a “Global profile” - the parameters in this profile are going to be applied to all servers in the Traffic Ops instance, or apply to Traffic Ops themselves. These parameters are:</p> <table border="1" class="docutils" id="index-0"> <colgroup> <col width="15%" /> @@ -217,34 +216,38 @@ <td>global</td> <td>The URL where this Traffic Ops instance is being served from.</td> </tr> -<tr class="row-odd"><td>tm.toolname</td> +<tr class="row-odd"><td>tm.cache.url</td> +<td>global</td> +<td>Not required. The URL where the Traffic Ops Config file cache instance is being served from. Requires Traffic Ops 2.1 and above.</td> +</tr> +<tr class="row-even"><td>tm.toolname</td> <td>global</td> <td>The name of the Traffic Ops tool. Usually “Traffic Ops”. Used in the About screen and in the comments headers of the files generated.</td> </tr> -<tr class="row-even"><td>tm.infourl</td> +<tr class="row-odd"><td>tm.infourl</td> <td>global</td> <td>This is the “for more information go here” URL, which is visible in the About page.</td> </tr> -<tr class="row-odd"><td>tm.logourl</td> +<tr class="row-even"><td>tm.logourl</td> <td>global</td> <td>This is the URL of the logo for Traffic Ops and can be relative if the logo is under traffic_ops/app/public.</td> </tr> -<tr class="row-even"><td>tm.instance_name</td> +<tr class="row-odd"><td>tm.instance_name</td> <td>global</td> <td>The name of the Traffic Ops instance. Can be used when multiple instances are active. Visible in the About page.</td> </tr> -<tr class="row-odd"><td>tm.traffic_mon_fwd_proxy</td> +<tr class="row-even"><td>tm.traffic_mon_fwd_proxy</td> <td>global</td> <td>When collecting stats from Traffic Monitor, Traffic Ops uses this forward proxy to pull the stats through. This can be any of the MID tier caches, or a forward cache specifically deployed for this purpose. Setting this variable can significantly lighten the load on the Traffic Monitor system and it is recommended to set this parameter on a production system.</td> </tr> -<tr class="row-even"><td>geolocation.polling.url</td> +<tr class="row-odd"><td>geolocation.polling.url</td> <td>CRConfig.json</td> <td>The location to get the GeoLiteCity database from.</td> </tr> -<tr class="row-odd"><td>geolocation6.polling.url</td> +<tr class="row-even"><td>geolocation6.polling.url</td> <td>CRConfig.json</td> <td>The location to get the IPv6 GeoLiteCity database from.</td> </tr> @@ -310,11 +313,11 @@ The Traffic Monitor IP addresses have to be included in this, if they are using </tr> <tr class="row-even"><td>Drive_Prefix</td> <td>storage.config</td> -<td>JvD/Jeff to supply blurb</td> +<td>The device path start of the disks. For example, if you have <code class="docutils literal"><span class="pre">/dev/sda</span></code> through <code class="docutils literal"><span class="pre">/dev/sdf</span></code> set this to <code class="docutils literal"><span class="pre">/dev/sd</span></code></td> </tr> <tr class="row-odd"><td>Drive_Letters</td> <td>storage.config</td> -<td>JvD/Jeff to supply blurb</td> +<td>The letter part of the disks, in the same example as above set this to <code class="docutils literal"><span class="pre">a,b,c,d,e,f</span></code></td> </tr> <tr class="row-even"><td>purge_allow_ip</td> <td>ip_allow.config</td> @@ -429,6 +432,14 @@ Value is left blank.</td> For example: –config regex_revalidate.config</td> <td><a class="reference external" href="https://docs.trafficserver.apache.org/en/5.3.x/reference/plugins/regex_remap.en.html";>regex_revalidate</a></td> </tr> +<tr class="row-odd"><td>use_reval_pending</td> +<td>global</td> +<td>Configures Traffic Ops to use separate +reval_pending flag for each cache.</td> +<td>When this flag is in use ORT will check for a new regex_revalidate.config every 60 seconds in syncds mode during the dispersal timer. This will +also allow ORT to be run in revalidate mode, which will check for and clear the reval_pending flag. This can be set to run via cron task. +This value is set to 0 by default. Enable with a value of 1. Use of this feature requires Traffic Ops 2.1 and above.</td> +</tr> </tbody> </table> <p>Note that the TTL the adminstrator enters in the purge request should be longer than the TTL of the content to ensure the bad content will not be used. If the CDN is serving content of unknown, or unlimited TTL, the administrator should consider using <a class="reference external" href="https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-config-http-cache-guaranteed-min-lifetime";>proxy-config-http-cache-guaranteed-min-lifetime</a> to limit the maximum time an object can be in the cache before it is considered stale, and set that to the same value as <cite>maxRevalDurationDays</cite> (Note that the former is in seconds and the latter is in days, so convert appropriately).</p> @@ -443,7 +454,7 @@ For example: –config regex_revalidate.config</td> <li>Start the kickstart installation.</li> </ol> <p>Create a ks.src file in the root of the selection location. See the example below:</p> -<div class="highlight-default"><div class="highlight"><pre><span class="n">mkdir</span> <span class="n">newdir</span> +<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">mkdir</span> <span class="n">newdir</span> <span class="n">cd</span> <span class="n">newdir</span><span class="o">/</span> <span class="n">cp</span> <span class="o">-</span><span class="n">r</span> <span class="o">../</span><span class="n">centos65</span><span class="o">/*</span> <span class="o">.</span> <span class="n">vim</span> <span class="n">ks</span><span class="o">.</span><span class="n">src</span> @@ -503,7 +514,7 @@ For example: –config regex_revalidate.config</td> <script type="text/javascript"> var DOCUMENTATION_OPTIONS = { URL_ROOT:'../', - VERSION:'1.8.1', + VERSION:'1.8-dev', COLLAPSE_INDEX:false, FILE_SUFFIX:'.html', HAS_SOURCE: true
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/5521f214/docs/latest/admin/traffic_ops_extensions.html ---------------------------------------------------------------------- diff --git a/docs/latest/admin/traffic_ops_extensions.html b/docs/latest/admin/traffic_ops_extensions.html index 6a38349..0ae22fc 100644 --- a/docs/latest/admin/traffic_ops_extensions.html +++ b/docs/latest/admin/traffic_ops_extensions.html @@ -7,7 +7,7 @@ <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Managing Traffic Ops Extensions — Traffic Control 1.8.1 documentation </title> + <title>Managing Traffic Ops Extensions — Traffic Control 1.8-dev documentation </title> @@ -33,10 +33,7 @@ - <link rel="index" title="Index" - href="../genindex.html"/> - <link rel="search" title="Search" href="../search.html"/> - <link rel="top" title="Traffic Control 1.8.1 documentation" href="../index.html"/> + <link rel="top" title="Traffic Control 1.8-dev documentation" href="../index.html"/> <link rel="up" title="Administratorâs Guide" href="index.html"/> <link rel="next" title="Traffic Portal Administration" href="traffic_portal.html"/> <link rel="prev" title="Using Traffic Ops" href="traffic_ops_using.html"/> @@ -162,14 +159,14 @@ <div class="rst-content"> <div role="navigation" aria-label="breadcrumbs navigation"> <ul class="wy-breadcrumbs"> - <li><a href="../index.html">Traffic Control 1.8.1</a> »</li> + <li><a href="../index.html">Traffic Control 1.8-dev</a> »</li> <li><a href="index.html">Administrator’s Guide</a> »</li> <li>Managing Traffic Ops Extensions</li> <li class="wy-breadcrumbs-aside"> - <a href="../_sources/admin/traffic_ops_extensions.rst.txt" rel="nofollow"> View page source</a> + <a href="../_sources/admin/traffic_ops_extensions.txt" rel="nofollow"> View page source</a> </li> </ul> @@ -193,7 +190,7 @@ <p>The extensions must be registered with Traffic Ops in order to display a column on the Server Check page. The list of currently registered extensions can be listed by running <code class="docutils literal"><span class="pre">/opt/traffic_ops/app/bin/extensions</span> <span class="pre">-a</span></code>.</p> <p>The below extensions are automatically registered with the Traffic Ops database (<code class="docutils literal"><span class="pre">to_extension</span></code> table) at install time (see <code class="docutils literal"><span class="pre">traffic_ops/app/db/seeds.sql</span></code>). However, cron must still be configured to run these checks periodically.</p> <p>The scripts are called as follows:</p> -<div class="highlight-default"><div class="highlight"><pre>$TO_HOME/bin/checks/To<name>Check.pl -c "{\"base_url\": \",https://\"<traffic_ops_ip>\", \"check_name\": \"<check_name>\"}" -l <log level> +<div class="highlight-default"><div class="highlight"><pre><span></span>$TO_HOME/bin/checks/To<name>Check.pl -c "{\"base_url\": \",https://\"<traffic_ops_ip>\", \"check_name\": \"<check_name>\"}" -l <log level> where: <name> is the type of check script @@ -205,7 +202,7 @@ where: <div class="section" id="example-cron-file"> <h2>Example Cron File<a class="headerlink" href="#example-cron-file" title="Permalink to this headline">¶</a></h2> <p>Edit with <code class="docutils literal"><span class="pre">crontab</span> <span class="pre">-e</span></code>. You may need to adjust the path to your $TO_HOME to match your system.</p> -<div class="highlight-default"><div class="highlight"><pre><span class="n">PERL5LIB</span><span class="o">=/</span><span class="n">opt</span><span class="o">/</span><span class="n">traffic_ops</span><span class="o">/</span><span class="n">app</span><span class="o">/</span><span class="n">local</span><span class="o">/</span><span class="n">lib</span><span class="o">/</span><span class="n">perl5</span><span class="p">:</span><span class="o">/</span><span class="n">opt</span><span class="o">/</span><span class="n">traffic_ops</span><span class="o">/</span><span class="n">app</span><span class="o">/</span><span class="n">lib</span> +<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">PERL5LIB</span><span class="o">=/</span><span class="n">opt</span><span class="o">/</span><span class="n">traffic_ops</span><span class="o">/</span><span class="n">app</span><span class="o">/</span><span class="n">local</span><span class="o">/</span><span class="n">lib</span><span class="o">/</span><span class="n">perl5</span><span class="p">:</span><span class="o">/</span><span class="n">opt</span><span class="o">/</span><span class="n">traffic_ops</span><span class="o">/</span><span class="n">app</span><span class="o">/</span><span class="n">lib</span> <span class="c1"># IPv4 ping examples - The 'select: ["hostName","domainName"]' works but, if you want to check DNS resolution use FQDN.</span> <span class="o">*/</span><span class="mi">15</span> <span class="o">*</span> <span class="o">*</span> <span class="o">*</span> <span class="o">*</span> <span class="n">root</span> <span class="o">/</span><span class="n">opt</span><span class="o">/</span><span class="n">traffic_ops</span><span class="o">/</span><span class="n">app</span><span class="o">/</span><span class="nb">bin</span><span class="o">/</span><span class="n">checks</span><span class="o">/</span><span class="n">ToPingCheck</span><span class="o">.</span><span class="n">pl</span> <span class="o">-</span><span class="n">c</span> <span class="s2">"{</span><span class="se">\"</span><span class="s2">base_url</span><span class="se">\"</span><span class="s2">: </span><span class="se">\"</span><span class="s2">https://localhost</span><span class="se">\"</span><span class="s2">, </span><span class="se">\"</span><span class="s2">check_name</span><span class="se">\"</span><span class="s2">: </s pan><span class="se">\"</span><span class="s2">10G</span><span class="se">\"</span><span class="s2">, </span><span class="se">\"</span><span class="s2">select</span><span class="se">\"</span><span class="s2">: [</span><span class="se">\"</span><span class="s2">hostName</span><span class="se">\"</span><span class="s2">,</span><span class="se">\"</span><span class="s2">domainName</span><span class="se">\"</span><span class="s2">]}"</span> <span class="o">>></span> <span class="o">/</span><span class="n">var</span><span class="o">/</span><span class="n">log</span><span class="o">/</span><span class="n">traffic_ops</span><span class="o">/</span><span class="n">extensionCheck</span><span class="o">.</span><span class="n">log</span> <span class="mi">2</span><span class="o">>&</span><span class="mi">1</span> @@ -290,7 +287,7 @@ where: <script type="text/javascript"> var DOCUMENTATION_OPTIONS = { URL_ROOT:'../', - VERSION:'1.8.1', + VERSION:'1.8-dev', COLLAPSE_INDEX:false, FILE_SUFFIX:'.html', HAS_SOURCE: true http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/5521f214/docs/latest/admin/traffic_ops_install.html ---------------------------------------------------------------------- diff --git a/docs/latest/admin/traffic_ops_install.html b/docs/latest/admin/traffic_ops_install.html index 8acce64..e68fe6b 100644 --- a/docs/latest/admin/traffic_ops_install.html +++ b/docs/latest/admin/traffic_ops_install.html @@ -7,7 +7,7 @@ <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Installing Traffic Ops — Traffic Control 1.8.1 documentation </title> + <title>Installing Traffic Ops — Traffic Control 1.8-dev documentation </title> @@ -33,10 +33,7 @@ - <link rel="index" title="Index" - href="../genindex.html"/> - <link rel="search" title="Search" href="../search.html"/> - <link rel="top" title="Traffic Control 1.8.1 documentation" href="../index.html"/> + <link rel="top" title="Traffic Control 1.8-dev documentation" href="../index.html"/> <link rel="up" title="Administratorâs Guide" href="index.html"/> <link rel="next" title="Configuring Traffic Ops" href="traffic_ops_config.html"/> <link rel="prev" title="Administratorâs Guide" href="index.html"/> @@ -111,6 +108,7 @@ <li class="toctree-l2"><a class="reference internal" href="traffic_ops_extensions.html">Managing Traffic Ops Extensions</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_portal.html">Traffic Portal Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_monitor.html">Traffic Monitor Administration</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_monitor_golang.html">Traffic Monitor Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_router.html">Traffic Router Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_stats.html">Traffic Stats Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_server.html">Traffic Server Administration</a></li> @@ -125,6 +123,7 @@ <li class="toctree-l2"><a class="reference internal" href="../development/traffic_portal.html">Traffic Portal</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_router.html">Traffic Router</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_monitor.html">Traffic Monitor</a></li> +<li class="toctree-l2"><a class="reference internal" href="../development/traffic_monitor_golang.html">Traffic Monitor Golang</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_stats.html">Traffic Stats</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_server.html">Traffic Server</a></li> </ul> @@ -162,14 +161,14 @@ <div class="rst-content"> <div role="navigation" aria-label="breadcrumbs navigation"> <ul class="wy-breadcrumbs"> - <li><a href="../index.html">Traffic Control 1.8.1</a> »</li> + <li><a href="../index.html">Traffic Control 1.8-dev</a> »</li> <li><a href="index.html">Administrator’s Guide</a> »</li> <li>Installing Traffic Ops</li> <li class="wy-breadcrumbs-aside"> - <a href="../_sources/admin/traffic_ops_install.rst.txt" rel="nofollow"> View page source</a> + <a href="../_sources/admin/traffic_ops_install.txt" rel="nofollow"> View page source</a> </li> </ul> @@ -257,7 +256,7 @@ </ol> <blockquote> <div><p>Example output:</p> -<div class="highlight-default"><div class="highlight"><pre><span class="n">trafficops</span><span class="o">-</span><span class="n">vm</span> <span class="c1"># /opt/traffic_ops/install/bin/postinstall</span> +<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">trafficops</span><span class="o">-</span><span class="n">vm</span> <span class="c1"># /opt/traffic_ops/install/bin/postinstall</span> <span class="n">This</span> <span class="n">script</span> <span class="n">will</span> <span class="n">build</span> <span class="ow">and</span> <span class="n">package</span> <span class="n">the</span> <span class="n">required</span> <span class="n">Traffic</span> <span class="n">Ops</span> <span class="n">perl</span> <span class="n">modules</span><span class="o">.</span> <span class="n">In</span> <span class="n">order</span> <span class="n">to</span> <span class="n">complete</span> <span class="n">this</span> <span class="n">operation</span><span class="p">,</span> <span class="n">Development</span> <span class="n">tools</span> <span class="n">such</span> <span class="k">as</span> <span class="n">the</span> <span class="n">gcc</span> @@ -274,7 +273,7 @@ </div> <p>If there are any prompts in this phase, please just answer with the defaults (some CPAN installs can prompt for install questions).</p> <p>When this phase is complete, you will see:</p> -<div class="highlight-default"><div class="highlight"><pre>... +<div class="highlight-default"><div class="highlight"><pre><span></span>... Successfully installed Test-Differences-0.63 Successfully installed DBIx-Class-Schema-Loader-0.07042 Successfully installed Time-HiRes-1.9726 (upgraded from 1.9719) @@ -303,7 +302,7 @@ Database type [mysql]: <p class="last">CentOS files note.</p> </div> <p>Example output:</p> -<div class="highlight-default"><div class="highlight"><pre>Database type [mysql]: +<div class="highlight-default"><div class="highlight"><pre><span></span>Database type [mysql]: Database name [traffic_ops_db]: Database server hostname IP or FQDN [localhost]: Database port number [3306]: @@ -444,7 +443,7 @@ use this user to login for the first time and create other users</td> <p>The postinstall script will now seed the database with some inital configuration settings for the CDN and the servers in the CDN.</p> <p>The next phase is the download of the geo location database and configuration of information needed for SSL certificates.</p> <p>Example output:</p> -<div class="highlight-default"><div class="highlight"><pre><span class="n">Downloading</span> <span class="n">MaxMind</span> <span class="n">data</span><span class="o">.</span> +<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">Downloading</span> <span class="n">MaxMind</span> <span class="n">data</span><span class="o">.</span> <span class="o">--</span><span class="mi">2015</span><span class="o">-</span><span class="mi">04</span><span class="o">-</span><span class="mi">14</span> <span class="mi">02</span><span class="p">:</span><span class="mi">14</span><span class="p">:</span><span class="mi">32</span><span class="o">--</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">geolite</span><span class="o">.</span><span class="n">maxmind</span><span class="o">.</span><span class="n">com</span><span class="o">/</span><span class="n">download</span><span class="o">/</span><span class="n">geoip</span><span class="o">/</span><span class="n">database</span><span class="o">/</span><span class="n">GeoLite2</span><span class="o">-</span><span class="n">City</span><span class="o">.</span><span class="n">mmdb</span><span class="o">.</span><span class="n">gz</span> <span class="n">Resolving</span> <span class="n">geolite</span><span class="o">.</span><span class="n">maxmind</span><span class="o">.</span><span class="n">com</span><span class="o">...</span> <span class="mf">141.101</span><span class="o">.</span><span class="mf">115.190</span><span class="p">,</span> <span class="mf">141.101</span><span class="o">.</span><span class="mf">114.190</span><span class="p">,</span> <span class="mi">2400</span><span class="p">:</span><span class="n">cb00</span><span class="p">:</span><span class="mi">2048</span><span class="p">:</span><span class="mi">1</span><span class="p">::</span><span class="mi">8</span><span class="n">d65</span><span class="p">:</span><span class="mi">73</span><span class="n">be</span><span class="p">,</span> <span class="o">...</span> <span class="n">Connecting</span> <span class="n">to</span> <span class="n">geolite</span><span class="o">.</span><span class="n">maxmind</span><span class="o">.</span><span class="n">com</span><span class="o">|</span><span class="mf">141.101</span><span class="o">.</span><span class="mf">115.190</span><span class="o">|</span><span class="p">:</span><span class="mf">80.</span><span class="o">..</span> <span class="n">connected</span><span class="o">.</span> @@ -573,6 +572,112 @@ use this user to login for the first time and create other users</td> </ol> </div> </div> +<div class="section" id="manually-generating-and-installing-the-ssl-certificate"> +<h2>Manually Generating and Installing the SSL Certificate<a class="headerlink" href="#manually-generating-and-installing-the-ssl-certificate" title="Permalink to this headline">¶</a></h2> +<div class="admonition note"> +<p class="first admonition-title">Note</p> +<p class="last">This section is valid for traffic-control 2.0.0 and later.</p> +</div> +<div class="section" id="self-signed-certificate-development"> +<h3>Self-signed Certificate (Development)<a class="headerlink" href="#self-signed-certificate-development" title="Permalink to this headline">¶</a></h3> +<blockquote> +<div><p>Example Procedure:</p> +<div class="highlight-default"><div class="highlight"><pre><span></span>$ openssl genrsa -des3 -passout pass:x -out localhost.pass.key 2048 +Generating RSA private key, 2048 bit long modulus +... +$ openssl rsa -passin pass:x -in localhost.pass.key -out localhost.key +writing RSA key +$ rm localhost.pass.key + +$ openssl req -new -key localhost.key -out localhost.csr +You are about to be asked to enter information that will be incorporated +into your certificate request. +What you are about to enter is what is called a Distinguished Name or a DN. +There are quite a few fields but you can leave some blank +For some fields there will be a default value, +If you enter '.', the field will be left blank. +----- +Country Name (2 letter code) [XX]:US<enter> +State or Province Name (full name) []:CO<enter> +Locality Name (eg, city) [Default City]:Denver<enter> +Organization Name (eg, company) [Default Company Ltd]: <enter> +Organizational Unit Name (eg, section) []: <enter> +Common Name (eg, your name or your server's hostname) []: <enter> +Email Address []: <enter> + +Please enter the following 'extra' attributes +to be sent with your certificate request +A challenge password []: pass<enter> +An optional company name []: <enter> +$ openssl x509 -req -sha256 -days 365 -in localhost.csr -signkey localhost.key -out localhost.crt +Signature ok +subject=/C=US/ST=CO/L=Denver/O=Default Company Ltd +Getting Private key +$ sudo cp localhost.crt /etc/pki/tls/certs +$ sudo cp localhost.key /etc/pki/tls/private +$ sudo chown trafops:trafops /etc/pki/tls/certs/localhost.crt +$ sudo chown trafops:trafops /etc/pki/tls/private/localhost.key +</pre></div> +</div> +</div></blockquote> +</div> +<div class="section" id="certificate-from-certificate-authority-production"> +<h3>Certificate from Certificate Authority (Production)<a class="headerlink" href="#certificate-from-certificate-authority-production" title="Permalink to this headline">¶</a></h3> +<div class="admonition note"> +<p class="first admonition-title">Note</p> +<p>You will need to know the appropriate answers when generating the certificate request file <cite>trafficopss.csr</cite> below.</p> +<p>Example Procedure:</p> +<div class="last highlight-default"><div class="highlight"><pre><span></span>$ openssl genrsa -des3 -passout pass:x -out trafficops.pass.key 2048 +Generating RSA private key, 2048 bit long modulus +... +$ openssl rsa -passin pass:x -in trafficops.pass.key -out trafficops.key +writing RSA key +$ rm localhost.pass.key + +Generate the Certificate Signing Request (CSR) file needed for Certificate Authority (CA) request. + +$ openssl req -new -key trafficops.key -out trafficops.csr +You are about to be asked to enter information that will be incorporated +into your certificate request. +What you are about to enter is what is called a Distinguished Name or a DN. +There are quite a few fields but you can leave some blank +For some fields there will be a default value, +If you enter '.', the field will be left blank. +----- +Country Name (2 letter code) [XX]: <enter country code> +State or Province Name (full name) []: <enter state or province> +Locality Name (eg, city) [Default City]: <enter locality name> +Organization Name (eg, company) [Default Company Ltd]: <enter organization name> +Organizational Unit Name (eg, section) []: <enter organizational unit name> +Common Name (eg, your name or your server's hostname) []: <enter server's hostname name> +Email Address []: <enter e-mail address> + +Please enter the following 'extra' attributes +to be sent with your certificate request +A challenge password []: <enter challenge password> +An optional company name []: <enter> +$ sudo cp trafficops.key /etc/pki/tls/private +$ sudo chown trafops:trafops /etc/pki/tls/private/trafficops.key + +You must then take the output file trafficops.csr and submit a request to your Certificate Authority (CA). +Once you get approved and receive your trafficops.crt file: + +$ sudo cp trafficops.crt /etc/pki/tls/certs +$ sudo chown trafops:trafops /etc/pki/tls/certs/trafficops.crt + +If necessary, install the CA certificates .pem and .crt in /etc/pki/tls/certs. + +You will need to update the file /opt/traffic_ops/app/conf/cdn.conf with the following changes: + ... + e.g. given trafficops.crt and trafficops.key + 'hypnotoad' => ... + 'listen' => 'https://[::]:443?cert=/etc/pki/tls/certs/trafficops.crt&key=/etc/pki/tls/private/trafficops.key&ca=/etc/pki/tls/certs/localhost.ca&verify=0x00&ciphers=AES128-GCM-SHA256:HIGH:!RC4:!MD5:!aNULL:!EDH:!ED' + ... +</pre></div> +</div> +</div> +</div> +</div> </div> @@ -613,7 +718,7 @@ use this user to login for the first time and create other users</td> <script type="text/javascript"> var DOCUMENTATION_OPTIONS = { URL_ROOT:'../', - VERSION:'1.8.1', + VERSION:'1.8-dev', COLLAPSE_INDEX:false, FILE_SUFFIX:'.html', HAS_SOURCE: true http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/5521f214/docs/latest/admin/traffic_ops_using.html ---------------------------------------------------------------------- diff --git a/docs/latest/admin/traffic_ops_using.html b/docs/latest/admin/traffic_ops_using.html index 4190ce2..d045c14 100644 --- a/docs/latest/admin/traffic_ops_using.html +++ b/docs/latest/admin/traffic_ops_using.html @@ -7,7 +7,7 @@ <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Using Traffic Ops — Traffic Control 1.8.1 documentation </title> + <title>Using Traffic Ops — Traffic Control 1.8-dev documentation </title> @@ -33,10 +33,7 @@ - <link rel="index" title="Index" - href="../genindex.html"/> - <link rel="search" title="Search" href="../search.html"/> - <link rel="top" title="Traffic Control 1.8.1 documentation" href="../index.html"/> + <link rel="top" title="Traffic Control 1.8-dev documentation" href="../index.html"/> <link rel="up" title="Administratorâs Guide" href="index.html"/> <link rel="next" title="Managing Traffic Ops Extensions" href="traffic_ops_extensions.html"/> <link rel="prev" title="Configuring Traffic Ops" href="traffic_ops_config.html"/> @@ -111,6 +108,7 @@ <li class="toctree-l2"><a class="reference internal" href="traffic_ops_extensions.html">Managing Traffic Ops Extensions</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_portal.html">Traffic Portal Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_monitor.html">Traffic Monitor Administration</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_monitor_golang.html">Traffic Monitor Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_router.html">Traffic Router Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_stats.html">Traffic Stats Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_server.html">Traffic Server Administration</a></li> @@ -125,6 +123,7 @@ <li class="toctree-l2"><a class="reference internal" href="../development/traffic_portal.html">Traffic Portal</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_router.html">Traffic Router</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_monitor.html">Traffic Monitor</a></li> +<li class="toctree-l2"><a class="reference internal" href="../development/traffic_monitor_golang.html">Traffic Monitor Golang</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_stats.html">Traffic Stats</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_server.html">Traffic Server</a></li> </ul> @@ -162,14 +161,14 @@ <div class="rst-content"> <div role="navigation" aria-label="breadcrumbs navigation"> <ul class="wy-breadcrumbs"> - <li><a href="../index.html">Traffic Control 1.8.1</a> »</li> + <li><a href="../index.html">Traffic Control 1.8-dev</a> »</li> <li><a href="index.html">Administrator’s Guide</a> »</li> <li>Using Traffic Ops</li> <li class="wy-breadcrumbs-aside"> - <a href="../_sources/admin/traffic_ops_using.rst.txt" rel="nofollow"> View page source</a> + <a href="../_sources/admin/traffic_ops_using.txt" rel="nofollow"> View page source</a> </li> </ul> @@ -345,31 +344,34 @@ per CDN.</td> </tr> </thead> <tbody valign="top"> -<tr class="row-even"><td>Cache Groups</td> +<tr class="row-even"><td>CDNs</td> +<td>Create/Read/Update/Delete CDNs</td> +</tr> +<tr class="row-odd"><td>Cache Groups</td> <td>Create/Read/Update/Delete cache groups</td> </tr> -<tr class="row-odd"><td>Users</td> +<tr class="row-even"><td>Users</td> <td>Create/Read/Update/Delete users</td> </tr> -<tr class="row-even"><td>Profiles</td> +<tr class="row-odd"><td>Profiles</td> <td>Create/Read/Update/Delete profiles. See <a class="reference internal" href="#rl-working-with-profiles"><span class="std std-ref">Parameters and Profiles</span></a></td> </tr> -<tr class="row-odd"><td>Networks(ASNs)</td> +<tr class="row-even"><td>Networks(ASNs)</td> <td>Create/Read/Update/Delete Autonomous System Numbers See <a class="reference internal" href="#rl-asn-czf"><span class="std std-ref">The Coverage Zone File and ASN Table</span></a></td> </tr> -<tr class="row-even"><td>Hardware</td> +<tr class="row-odd"><td>Hardware</td> <td>Get detailed hardware information (note: this should be moved to a Traffic Ops Extension)</td> </tr> -<tr class="row-odd"><td>Data Types</td> +<tr class="row-even"><td>Data Types</td> <td>Create/Read/Update/Delete data types</td> </tr> -<tr class="row-even"><td>Divisions</td> +<tr class="row-odd"><td>Divisions</td> <td>Create/Read/Update/Delete divisions</td> </tr> -<tr class="row-odd"><td>Regions</td> +<tr class="row-even"><td>Regions</td> <td>Create/Read/Update/Delete regions</td> </tr> -<tr class="row-even"><td>Physical Locations</td> +<tr class="row-odd"><td>Physical Locations</td> <td>Create/Read/Update/Delete locations</td> </tr> </tbody> @@ -512,7 +514,7 @@ must have an ssh key on the edge servers.</td> <td>Origin</td> </tr> <tr class="row-odd"><td>CCR</td> -<td>Comcast Content Router</td> +<td>Traffic Router</td> </tr> <tr class="row-even"><td>RASCAL</td> <td>Rascal health polling & reporting</td> @@ -537,6 +539,7 @@ must have an ssh key on the edge servers.</td> </div> <div class="section" id="bulk-upload-server"> <span id="rl-bulkserver"></span><span id="index-3"></span><h3>Bulk Upload Server<a class="headerlink" href="#bulk-upload-server" title="Permalink to this headline">¶</a></h3> +<p>TBD</p> </div> </div> <div class="section" id="delivery-service"> @@ -627,83 +630,74 @@ AAAA records of the edge name (<code class="docutils literal"><span class="pre"> <tr class="row-odd"><td>Use Multi Site Origin Feature</td> <td>Enable the Multi Site Origin feature for this delivery service. See <a class="reference internal" href="#rl-multi-site-origin"><span class="std std-ref">Multi Site Origin</span></a></td> </tr> -<tr class="row-even"><td>Multi Site Origin Algorithm</td> -<td><ul class="first last simple"> -<li>1 Consistent Hash spreads requests across multiple parents simultaneously based on hash of content URL.</li> -<li>2 Strict Round Robin spreads requests across multiple parents simultaneously based on order of requests.</li> -<li>3 IP Based Round Robin spreads requests across multiple parents simultaneously based on order of requests, but ensures that requests from the same IP always go to the same parent if available.</li> -<li>4 Latched uses only a single parent at any given time and switches to a new parent only if the current parent fails.</li> -</ul> -</td> -</tr> -<tr class="row-odd"><td>CCR profile</td> -<td>The Traffic Router profile for this delivery service. See <a class="reference internal" href="#rl-ccr-profile"><span class="std std-ref">CCR Profile or Traffic Router Profile</span></a>.</td> +<tr class="row-even"><td>Profile</td> +<td>The profile for this delivery service.</td> </tr> -<tr class="row-even"><td>Maximum Bits per Second allowed globally</td> +<tr class="row-odd"><td>Maximum Bits per Second allowed globally</td> <td>The maximum bits per second this delivery service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6 will be used (depending on whether this was a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used.</td> </tr> -<tr class="row-odd"><td>Maximum Transactions per Second allowed globally</td> +<tr class="row-even"><td>Maximum Transactions per Second allowed globally</td> <td>The maximum transactions per se this delivery service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6 will be used (depending on whether this was a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used.</td> </tr> -<tr class="row-even"><td>Geo Miss Default Latitude</td> +<tr class="row-odd"><td>Geo Miss Default Latitude</td> <td>Default Latitude for this delivery service. When client localization fails for both Coverage Zone and Geo Lookup, this the client will be routed as if it was at this lat.</td> </tr> -<tr class="row-odd"><td>Geo Miss Default Longitude</td> +<tr class="row-even"><td>Geo Miss Default Longitude</td> <td>Default Longitude for this delivery service. When client localization fails for bot Coverage Zone and Geo Lookup, this the client will be routed as if it was at this long.</td> </tr> -<tr class="row-even"><td>Edge Header Rewrite Rules</td> +<tr class="row-odd"><td>Edge Header Rewrite Rules</td> <td>Header Rewrite rules to apply for this delivery service at the EDGE tier. See <a class="reference internal" href="#rl-header-rewrite"><span class="std std-ref">Header Rewrite Options and DSCP</span></a>. <a class="footnote-reference" href="#id6" id="id1">[1]</a></td> </tr> -<tr class="row-odd"><td>Mid Header Rewrite Rules</td> +<tr class="row-even"><td>Mid Header Rewrite Rules</td> <td>Header Rewrite rules to apply for this delivery service at the MID tier. See <a class="reference internal" href="#rl-header-rewrite"><span class="std std-ref">Header Rewrite Options and DSCP</span></a>. <a class="footnote-reference" href="#id6" id="id2">[1]</a></td> </tr> -<tr class="row-even"><td>Regex Remap Expression</td> +<tr class="row-odd"><td>Regex Remap Expression</td> <td><p class="first">Regex Remap rule to apply to this delivery service at the Edge tier. See <a class="reference external" href="https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_remap.en.html";>ATS documentation on regex_remap</a>. <a class="footnote-reference" href="#id6" id="id3">[1]</a></p> <p class="last"><strong>Note:</strong> you will not be able to save a Regex Remap Expression if you have Query String Handling set to drop query strings at the edge. See <a class="reference internal" href="#rl-regex-remap"><span class="std std-ref">Regex Remap Expression</span></a>.</p> </td> </tr> -<tr class="row-odd"><td>Cache URL expression</td> +<tr class="row-even"><td>Cache URL expression</td> <td>Cache URL rule to apply to this delivery service. See <a class="reference external" href="https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cacheurl.en.html";>ATS documentation on cacheurl</a>. <a class="footnote-reference" href="#id6" id="id4">[1]</a></td> </tr> -<tr class="row-even"><td>Raw remap text</td> +<tr class="row-odd"><td>Raw remap text</td> <td>For HTTP and DNS deliveryservices, this will get added to the end of the remap line on the cache verbatim. For ANY_MAP deliveryservices this is the remap line. <a class="footnote-reference" href="#id6" id="id5">[1]</a></td> </tr> -<tr class="row-odd"><td>Long Description</td> +<tr class="row-even"><td>Long Description</td> <td>Long description for this delivery service. To be consumed from the APIs by downstream tools (Portal).</td> </tr> -<tr class="row-even"><td>Customer</td> +<tr class="row-odd"><td>Customer</td> <td>Customer description for this delivery service. To be consumed from the APIs by downstream tools (Portal).</td> </tr> -<tr class="row-odd"><td>Service</td> +<tr class="row-even"><td>Service</td> <td>Service description for this delivery service. To be consumed from the APIs by downstream tools (Portal).</td> </tr> -<tr class="row-even"><td>Info URL</td> +<tr class="row-odd"><td>Info URL</td> <td>Info URL for this delivery service. To be consumed from the APIs by downstream tools (Portal).</td> </tr> -<tr class="row-odd"><td>Check Path</td> +<tr class="row-even"><td>Check Path</td> <td>A path (ex: /crossdomain.xml) to verify the connection to the origin server with. This can be used by Check Extension scripts to do periodic health checks against the delivery service.</td> </tr> -<tr class="row-even"><td>Origin Shield (Pipe Delimited String)</td> +<tr class="row-odd"><td>Origin Shield (Pipe Delimited String)</td> <td>Experimental. Origin Shield string.</td> </tr> -<tr class="row-odd"><td>Active</td> +<tr class="row-even"><td>Active</td> <td>When this is set to no Traffic Router will not serve DNS or HTTP responses for this delivery service.</td> </tr> -<tr class="row-even"><td>Last Updated</td> +<tr class="row-odd"><td>Last Updated</td> <td>(Read Only) The last time this delivery service was updated.</td> </tr> -<tr class="row-odd"><td>Number of edges assigned</td> +<tr class="row-even"><td>Number of edges assigned</td> <td>(Read Only - change by clicking the <strong>Server Assignments</strong> button at the bottom) The number of EDGE caches assigned to this delivery service. See <a class="reference internal" href="#rl-assign-edges"><span class="std std-ref">Server Assignments</span></a>.</td> </tr> -<tr class="row-even"><td>Number of static DNS entries</td> +<tr class="row-odd"><td>Number of static DNS entries</td> <td>(Read Only - change by clicking the <strong>Static DNS</strong> button at the bottom) The number of static DNS entries for this delivery service. See <a class="reference internal" href="#rl-static-dns"><span class="std std-ref">Static DNS Entries</span></a>.</td> </tr> -<tr class="row-odd"><td>Example delivery URL</td> +<tr class="row-even"><td>Example delivery URL</td> <td>(Read Only) An example of how the delivery URL may start. This could be multiple rows if multiple HOST_REGEXP entries have been entered.</td> </tr> -<tr class="row-even"><td>Regular expressions for this delivery service</td> +<tr class="row-odd"><td>Regular expressions for this delivery service</td> <td>A subtable of the regular expressions to use when routing traffic for this delivery service. See <a class="reference internal" href="#rl-ds-regexp"><span class="std std-ref">Delivery Service Regexp</span></a>.</td> </tr> </tbody> @@ -893,68 +887,68 @@ http.no_dns_just_forward_to_parent</td> http.uncacheable_requests_bypass_parent</td> <td>records.config</td> <td>INT 1</td> -<td> </td> +<td> </td> </tr> <tr class="row-even"><td>CONFIG proxy.config. http.parent_proxy_routing_enable</td> <td>records.config</td> <td>INT 1</td> -<td> </td> +<td> </td> </tr> <tr class="row-odd"><td>CONFIG proxy.config. http.parent_proxy.retry_time</td> <td>records.config</td> <td>INT 300</td> -<td> </td> +<td> </td> </tr> <tr class="row-even"><td>CONFIG proxy.config. http.parent_proxy.fail_threshold</td> <td>records.config</td> <td>INT 10</td> -<td> </td> +<td> </td> </tr> <tr class="row-odd"><td>CONFIG proxy.config. http.parent_proxy.total_connect_attempts</td> <td>records.config</td> <td>INT 4</td> -<td> </td> +<td> </td> </tr> <tr class="row-even"><td>CONFIG proxy.config. http.parent_proxy.per_parent_connect_attempts</td> <td>records.config</td> <td>INT 2</td> -<td> </td> +<td> </td> </tr> <tr class="row-odd"><td>CONFIG proxy.config. http.parent_proxy.connect_attempts_timeout</td> <td>records.config</td> <td>INT 30</td> -<td> </td> +<td> </td> </tr> <tr class="row-even"><td>CONFIG proxy.config. http.forward.proxy_auth_to_parent</td> <td>records.config</td> <td>INT 0</td> -<td> </td> +<td> </td> </tr> <tr class="row-odd"><td>CONFIG proxy.config. http.parent_proxy_routing_enable</td> <td>records.config</td> <td>INT 0</td> -<td> </td> +<td> </td> </tr> <tr class="row-even"><td>CONFIG proxy.config. http.parent_proxy.file</td> <td>records.config</td> <td>STRING parent.config</td> -<td> </td> +<td> </td> </tr> <tr class="row-odd"><td>CONFIG proxy.config. http.parent_proxy.connect_attempts_timeout</td> <td>records.config</td> <td>INT 3</td> -<td> </td> +<td> </td> </tr> <tr class="row-even"><td>algorithm</td> <td>parent.config</td> @@ -1009,11 +1003,11 @@ http.parent_proxy.connect_attempts_timeout</td> <span id="rl-multi-site-origin"></span><h3>Multi Site Origin<a class="headerlink" href="#multi-site-origin" title="Permalink to this headline">¶</a></h3> <div class="admonition note"> <p class="first admonition-title">Note</p> -<p class="last">The Multi Site Origin feature is based upon a feature n ATS that has yet to be submitted to Traffic Server upstream, until it is, set this to 0, or use the ATS rpm supplied on the trafficcontrol.apache.org website.</p> +<p class="last">The configuration of this feature changed significantly between ATS version 5 and >= 6. Some configuration in Traffic Control is different as well. This documentation assumes ATS 6 or higher. See <a class="reference internal" href="quick_howto/multi_site_ats5.html#rl-multi-site-origin-qht-ats5"><span class="std std-ref">Configure Multi Site Origin (5.x)</span></a> for the ATS version 5.x configuration details.</p> </div> -<p>Normally, the mid servers are not aware of any redundancy at the origin layer. With Multi Site Origin enabled this changes - Traffic Server (and Traffic Ops) are now made aware of the fact there are multiple origins, and can be configured to do more advanced failover and loadbalancing actions.</p> -<p>With This feature enabled, origin servers (or origin server VIP names for a site) are going to be entered as servers in to the Traiffic Ops UI. Server type is “”</p> -<p>Parameters in the Origin profile that influence this feature:</p> +<p>Normally, the mid servers are not aware of any redundancy at the origin layer. With Multi Site Origin enabled this changes - Traffic Server (and Traffic Ops) are now made aware of the fact there are multiple origins, and can be configured to do more advanced failover and loadbalancing actions. A prerequisite for MSO to work is that the multiple origin sites serve identical content with identical paths, and both are configured to serve the same origin hostname as is configured in the deliveryservice <cite>Origin Server Base URL</cite> field. See the <a class="reference external" href="https://docs.trafficserver.apache.org/en/latest/admin-guide/files/parent.config.en.html";>Apache Traffic Server docs</a> for more information on that cache’s implementation.</p> +<p>With This feature enabled, origin servers (or origin server VIP names for a site) are going to be entered as servers in to the Traiffic Ops UI. Server type is “ORG”.</p> +<p>Parameters in the mid profile that influence this feature:</p> <table border="1" class="docutils"> <colgroup> <col width="37%" /> @@ -1039,47 +1033,68 @@ http.parent_proxy.connect_attempts_timeout</td> <td>INT 1</td> <td>required for parent selection.</td> </tr> -<tr class="row-even"><td>CONFIG proxy.config. http.parent_proxy.per_parent_connect_attempts</td> -<td>records.config</td> -<td>INT 5</td> -<td>maximum of 5 connection attempts per parent (parent.config list) within a transaction.</td> +</tbody> +</table> +<p>Parameters in the deliveryservice profile that influence this feature:</p> +<table border="1" class="docutils"> +<colgroup> +<col width="22%" /> +<col width="8%" /> +<col width="8%" /> +<col width="62%" /> +</colgroup> +<thead valign="bottom"> +<tr class="row-odd"><th class="head">Name</th> +<th class="head">Filename</th> +<th class="head">Default</th> +<th class="head">Description</th> </tr> -<tr class="row-odd"><td>CONFIG proxy.config. http.parent_proxy.total_connect_attempts</td> -<td>records.config</td> -<td>INT 10</td> -<td>maximum of 10 total connection attempts within a transaction.</td> +</thead> +<tbody valign="top"> +<tr class="row-even"><td>mso.parent_retry</td> +<td>parent.config</td> +<td>-</td> +<td>Either <code class="docutils literal"><span class="pre">simple_retry</span></code>, <code class="docutils literal"><span class="pre">dead_server_retry</span></code> or <code class="docutils literal"><span class="pre">both</span></code>.</td> </tr> -<tr class="row-even"><td>CONFIG proxy.config. http.parent_origin.simple_retry_enabled</td> -<td>records.config</td> -<td>INT 1</td> -<td>enables simple retry.</td> +<tr class="row-odd"><td>mso.algorithm</td> +<td>parent.config</td> +<td>consistent_hash</td> +<td><p class="first">The algorithm to use. <code class="docutils literal"><span class="pre">consisten_hash</span></code>, <code class="docutils literal"><span class="pre">strict</span></code>, <code class="docutils literal"><span class="pre">true</span></code>, <code class="docutils literal"><span class="pre">false</span></code>, or <code class="docutils literal"><span class="pre">latched</span></code>.</p> +<ul class="last simple"> +<li><code class="docutils literal"><span class="pre">consisten_hash</span></code> - spreads requests across multiple parents simultaneously based on hash of content URL.</li> +<li><code class="docutils literal"><span class="pre">strict</span></code> - strict Round Robin spreads requests across multiple parents simultaneously based on order of requests.</li> +<li><code class="docutils literal"><span class="pre">true</span></code> - same as strict, but ensures that requests from the same IP always go to the same parent if available.</li> +<li><code class="docutils literal"><span class="pre">false</span></code> - uses only a single parent at any given time and switches to a new parent only if the current parent fails.</li> +<li><code class="docutils literal"><span class="pre">latched</span></code> - same as false, but now, a failed parent will not be retried.</li> +</ul> +</td> </tr> -<tr class="row-odd"><td>CONFIG proxy.config. http.parent_origin.simple_retry_response_codes</td> -<td>records.config</td> -<td>STRING 404</td> -<td>the response code that invokes simple retry. May be a comman separated list of response codes.</td> +<tr class="row-even"><td>mso.unavailable_server_retry_response_codes</td> +<td>parent.config</td> +<td>“503”</td> +<td>Quoted, comma separated list of HTTP status codes that count as a unavailable_server_retry_response_code.</td> </tr> -<tr class="row-even"><td>CONFIG proxy.config. http.parent_origin.dead_server_retry_response_codes</td> -<td>records.config</td> -<td>STRING 503</td> -<td>the response code that invokes dead server retry. May be a comma separated list of response codes</td> +<tr class="row-odd"><td>mso.max_unavailable_server_retries</td> +<td>parent.config</td> +<td>1</td> +<td>How many times an unavailable server will be retried.</td> </tr> -<tr class="row-odd"><td>CONFIG proxy.config. http.parent_origin.dead_server_retry_enabled</td> -<td>records.config</td> -<td>INT 1</td> -<td>enables dead server retry.</td> +<tr class="row-even"><td>mso.simple_retry_response_codes</td> +<td>parent.config</td> +<td>“404”</td> +<td>Quoted, comma separated list of HTTP status codes that count as a simple retry response code.</td> </tr> -<tr class="row-even"><td>CONFIG proxy.config. diags.debug.enabled</td> -<td>records.config</td> -<td>INT 1</td> -<td>enable debugging for testing only</td> +<tr class="row-odd"><td>mso.max_simple_retries</td> +<td>parent.config</td> +<td>1</td> +<td>How many times a simple retry will be done.</td> </tr> </tbody> </table> <p>see <a class="reference internal" href="quick_howto/multi_site.html#rl-multi-site-origin-qht"><span class="std std-ref">Configure Multi Site Origin</span></a> for a <em>quick how to</em> on this feature.</p> </div> -<div class="section" id="ccr-profile-or-traffic-router-profile"> -<span id="rl-ccr-profile"></span><h3>CCR Profile or Traffic Router Profile<a class="headerlink" href="#ccr-profile-or-traffic-router-profile" title="Permalink to this headline">¶</a></h3> +<div class="section" id="traffic-router-profile"> +<span id="rl-ccr-profile"></span><h3>Traffic Router Profile<a class="headerlink" href="#traffic-router-profile" title="Permalink to this headline">¶</a></h3> <table border="1" class="docutils"> <colgroup> <col width="15%" /> @@ -1133,127 +1148,123 @@ http.parent_proxy.connect_attempts_timeout</td> <td>CRConfig.json</td> <td>The location (URL) to retrieve the coverage zone map file in XML format from.</td> </tr> -<tr class="row-even"><td>domain_name</td> -<td>CRConfig.json</td> -<td>The top level domain of this Traffic Router instance.</td> -</tr> -<tr class="row-odd"><td>tld.soa.expire</td> +<tr class="row-even"><td>tld.soa.expire</td> <td>CRConfig.json</td> <td>The value for the expire field the Traffic Router DNS Server will respond with on Start of Authority (SOA) records.</td> </tr> -<tr class="row-even"><td>tld.soa.minimum</td> +<tr class="row-odd"><td>tld.soa.minimum</td> <td>CRConfig.json</td> <td>The value for the minimum field the Traffic Router DNS Server will respond with on SOA records.</td> </tr> -<tr class="row-odd"><td>tld.soa.admin</td> +<tr class="row-even"><td>tld.soa.admin</td> <td>CRConfig.json</td> <td>The DNS Start of Authority admin. Should be a valid support email address for support if DNS is not working correctly.</td> </tr> -<tr class="row-even"><td>tld.soa.retry</td> +<tr class="row-odd"><td>tld.soa.retry</td> <td>CRConfig.json</td> <td>The value for the retry field the Traffic Router DNS Server will respond with on SOA records.</td> </tr> -<tr class="row-odd"><td>tld.soa.refresh</td> +<tr class="row-even"><td>tld.soa.refresh</td> <td>CRConfig.json</td> <td>The TTL the Traffic Router DNS Server will respond with on A records.</td> </tr> -<tr class="row-even"><td>tld.ttls.NS</td> +<tr class="row-odd"><td>tld.ttls.NS</td> <td>CRConfig.json</td> <td>The TTL the Traffic Router DNS Server will respond with on NS records.</td> </tr> -<tr class="row-odd"><td>tld.ttls.SOA</td> +<tr class="row-even"><td>tld.ttls.SOA</td> <td>CRConfig.json</td> <td>The TTL the Traffic Router DNS Server will respond with on SOA records.</td> </tr> -<tr class="row-even"><td>tld.ttls.AAAA</td> +<tr class="row-odd"><td>tld.ttls.AAAA</td> <td>CRConfig.json</td> <td>The Time To Live (TTL) the Traffic Router DNS Server will respond with on AAAA records.</td> </tr> -<tr class="row-odd"><td>tld.ttls.A</td> +<tr class="row-even"><td>tld.ttls.A</td> <td>CRConfig.json</td> <td>The TTL the Traffic Router DNS Server will respond with on A records.</td> </tr> -<tr class="row-even"><td>tld.ttls.DNSKEY</td> +<tr class="row-odd"><td>tld.ttls.DNSKEY</td> <td>CRConfig.json</td> <td>The TTL the Traffic Router DNS Server will respond with on DNSKEY records.</td> </tr> -<tr class="row-odd"><td>tld.ttls.DS</td> +<tr class="row-even"><td>tld.ttls.DS</td> <td>CRConfig.json</td> <td>The TTL the Traffic Router DNS Server will respond with on DS records.</td> </tr> -<tr class="row-even"><td>api.port</td> +<tr class="row-odd"><td>api.port</td> <td>server.xml</td> <td>The TCP port Traffic Router listens on for API (REST) access.</td> </tr> -<tr class="row-odd"><td>api.cache-control.max-age</td> +<tr class="row-even"><td>api.cache-control.max-age</td> <td>CRConfig.json</td> <td>The value of the <code class="docutils literal"><span class="pre">Cache-Control:</span> <span class="pre">max-age=</span></code> header in the API responses of Traffic Router.</td> </tr> -<tr class="row-even"><td>api.auth.url</td> +<tr class="row-odd"><td>api.auth.url</td> <td>CRConfig.json</td> <td>The API authentication URL (<a class="reference external" href="https:/">https:/</a>/${tmHostname}/api/1.1/user/login); ${tmHostname} is a search and replace token used by Traffic Router to construct the correct URL)</td> </tr> -<tr class="row-odd"><td>consistent.dns.routing</td> +<tr class="row-even"><td>consistent.dns.routing</td> <td>CRConfig.json</td> <td>Control whether DNS Delivery Services use consistent hashing on the edge FQDN to select caches for answers. May improve performance if set to true; defaults to false</td> </tr> -<tr class="row-even"><td>dnssec.enabled</td> +<tr class="row-odd"><td>dnssec.enabled</td> <td>CRConfig.json</td> <td>Whether DNSSEC is enabled; this parameter is updated via the DNSSEC administration user interface.</td> </tr> -<tr class="row-odd"><td>dnssec.allow.expired.keys</td> +<tr class="row-even"><td>dnssec.allow.expired.keys</td> <td>CRConfig.json</td> <td>Allow Traffic Router to use expired DNSSEC keys to sign zones; default is true. This helps prevent DNSSEC related outages due to failed Traffic Control components or connectivity issues.</td> </tr> -<tr class="row-even"><td>dynamic.cache.primer.enabled</td> +<tr class="row-odd"><td>dynamic.cache.primer.enabled</td> <td>CRConfig.json</td> <td>Allow Traffic Router to attempt to prime the dynamic zone cache; defaults to true</td> </tr> -<tr class="row-odd"><td>dynamic.cache.primer.limit</td> +<tr class="row-even"><td>dynamic.cache.primer.limit</td> <td>CRConfig.json</td> <td>Limit the number of permutations to prime when dynamic zone cache priming is enabled; defaults to 500</td> </tr> -<tr class="row-even"><td>keystore.maintenance.interval</td> +<tr class="row-odd"><td>keystore.maintenance.interval</td> <td>CRConfig.json</td> <td>The interval in seconds which Traffic Router will check the keystore API for new DNSSEC keys</td> </tr> -<tr class="row-odd"><td>keystore.api.url</td> +<tr class="row-even"><td>keystore.api.url</td> <td>CRConfig.json</td> <td>The keystore API URL (<a class="reference external" href="https:/">https:/</a>/${tmHostname}/api/1.1/cdns/name/${cdnName}/dnsseckeys.json; ${tmHostname} and ${cdnName} are search and replace tokens used by Traffic Router to construct the correct URL)</td> </tr> -<tr class="row-even"><td>keystore.fetch.timeout</td> +<tr class="row-odd"><td>keystore.fetch.timeout</td> <td>CRConfig.json</td> <td>The timeout in milliseconds for requests to the keystore API</td> </tr> -<tr class="row-odd"><td>keystore.fetch.retries</td> +<tr class="row-even"><td>keystore.fetch.retries</td> <td>CRConfig.json</td> <td>The number of times Traffic Router will attempt to load keys before giving up; defaults to 5</td> </tr> -<tr class="row-even"><td>keystore.fetch.wait</td> +<tr class="row-odd"><td>keystore.fetch.wait</td> <td>CRConfig.json</td> <td>The number of milliseconds Traffic Router will wait before a retry</td> </tr> -<tr class="row-odd"><td>signaturemanager.expiration.multiplier</td> +<tr class="row-even"><td>signaturemanager.expiration.multiplier</td> <td>CRConfig.json</td> <td>Multiplier used in conjunction with a zone’s maximum TTL to calculate DNSSEC signature durations; defaults to 5</td> </tr> -<tr class="row-even"><td>zonemanager.threadpool.scale</td> +<tr class="row-odd"><td>zonemanager.threadpool.scale</td> <td>CRConfig.json</td> <td>Multiplier used to determine the number of cores to use for zone signing operations; defaults to 0.75</td> </tr> -<tr class="row-odd"><td>zonemanager.cache.maintenance.interval</td> +<tr class="row-even"><td>zonemanager.cache.maintenance.interval</td> <td>CRConfig.json</td> <td>The interval in seconds which Traffic Router will check for zones that need to be resigned or if dynamic zones need to be expired from cache</td> </tr> -<tr class="row-even"><td>zonemanager.dynamic.response.expiration</td> +<tr class="row-odd"><td>zonemanager.dynamic.response.expiration</td> <td>CRConfig.json</td> <td>A string (e.g.: 300s) that defines how long a dynamic zone</td> </tr> -<tr class="row-odd"><td>DNSKEY.generation.multiplier</td> +<tr class="row-even"><td>DNSKEY.generation.multiplier</td> <td>CRConfig.json</td> <td>Used to deteremine when new keys need to be regenerated. Keys are regenerated if expiration is less than the generation multiplier * the TTL. If the parameter does not exist, the default is 10.</td> </tr> -<tr class="row-even"><td>DNSKEY.effective.multiplier</td> +<tr class="row-odd"><td>DNSKEY.effective.multiplier</td> <td>CRConfig.json</td> <td>Used when creating an effective date for a new key set. New keys are generated with an effective date of old key expiration - (effective multiplier * TTL). Default is 2.</td> </tr> @@ -1263,13 +1274,13 @@ http.parent_proxy.connect_attempts_timeout</td> <div class="section" id="regex-remap-expression"> <span id="rl-regex-remap"></span><span id="index-7"></span><h3>Regex Remap Expression<a class="headerlink" href="#regex-remap-expression" title="Permalink to this headline">¶</a></h3> <p>The regex remap expression allows to to use a regex and resulting match group(s) in order to modify the request URIs that are sent to origin. For example:</p> -<div class="highlight-default"><div class="highlight"><pre>^/original/(.*) http://origin.example.com/remapped/$1 +<div class="highlight-default"><div class="highlight"><pre><span></span>^/original/(.*) http://origin.example.com/remapped/$1 </pre></div> </div> <div class="admonition note"> <p class="first admonition-title">Note</p> <p>If <strong>Query String Handling</strong> is set to <code class="docutils literal"><span class="pre">2</span> <span class="pre">Drop</span> <span class="pre">at</span> <span class="pre">edge</span></code>, then you will not be allowed to save a regex remap expression, as dropping query strings actually relies on a regex remap of its own. However, if there is a need to both drop query strings <strong>and</strong> remap request URIs, this can be accomplished by setting <strong>Query String Handling</strong> to <code class="docutils literal"><span class="pre">1</span> <span class="pre">Do</span> <span class="pre">not</span> <span class="pre">use</span> <span class="pre">in</span> <span class="pre">cache</span> <span class="pre">key,</span> <span class="pre">but</span> <span class="pre">pass</span> <span class="pre">up</span> <span class="pre">to</span> <span class="pre">origin</span></code>, and then using a custom regex remap expression to do the necessary remapping, while simultan eously dropping query strings. The following example will capture the original request URI up to, but not including, the query string and then forward to a remapped URI:</p> -<div class="last highlight-default"><div class="highlight"><pre>^/([^?]*).* http://origin.example.com/remapped/$1 +<div class="last highlight-default"><div class="highlight"><pre><span></span>^/([^?]*).* http://origin.example.com/remapped/$1 </pre></div> </div> </div> @@ -1330,7 +1341,7 @@ http.parent_proxy.connect_attempts_timeout</td> <div class="section" id="the-coverage-zone-file-and-asn-table"> <span id="rl-asn-czf"></span><h3>The Coverage Zone File and ASN Table<a class="headerlink" href="#the-coverage-zone-file-and-asn-table" title="Permalink to this headline">¶</a></h3> <p>The Coverage Zone File (CZF) should contain a cachegroup name to network prefix mapping in the form:</p> -<div class="highlight-default"><div class="highlight"><pre><span class="p">{</span> +<div class="highlight-default"><div class="highlight"><pre><span></span><span class="p">{</span> <span class="s2">"coverageZones"</span><span class="p">:</span> <span class="p">{</span> <span class="s2">"cache-group-01"</span><span class="p">:</span> <span class="p">{</span> <span class="s2">"network6"</span><span class="p">:</span> <span class="p">[</span> @@ -1441,7 +1452,7 @@ http.parent_proxy.connect_attempts_timeout</td> <p>What we currently do is have 2 scripts, one to do hard drive configuration and one to do network configuration. Both are relatively specific to the environment they were created in, and both are <em>probably</em> wrong for other organizations, however they are currently living in the “misc” directory as examples of how to do things.</p> <p>We trigger those in a %pre section in ks.cfg and they will write config files to /tmp. We will then include those files in the appropriate places using %pre.</p> <p>For example this is a section of our ks.cfg file:</p> -<div class="highlight-default"><div class="highlight"><pre><span class="o">%</span><span class="n">include</span> <span class="o">/</span><span class="n">mnt</span><span class="o">/</span><span class="n">stage2</span><span class="o">/</span><span class="n">ks_scripts</span><span class="o">/</span><span class="n">packages</span><span class="o">.</span><span class="n">txt</span> +<div class="highlight-default"><div class="highlight"><pre><span></span><span class="o">%</span><span class="n">include</span> <span class="o">/</span><span class="n">mnt</span><span class="o">/</span><span class="n">stage2</span><span class="o">/</span><span class="n">ks_scripts</span><span class="o">/</span><span class="n">packages</span><span class="o">.</span><span class="n">txt</span> <span class="o">%</span><span class="n">pre</span> <span class="n">python</span> <span class="o">/</span><span class="n">mnt</span><span class="o">/</span><span class="n">stage2</span><span class="o">/</span><span class="n">ks_scripts</span><span class="o">/</span><span class="n">create_network_line</span><span class="o">.</span><span class="n">py</span> @@ -1450,7 +1461,7 @@ http.parent_proxy.connect_attempts_timeout</td> </pre></div> </div> <p>These two scripts will then run _before_ anaconda sets up it’s internal structures, then a bit further up in the ks.cfg file (outside of the %pre %end block) we do an</p> -<div class="highlight-default"><div class="highlight"><pre><span class="o">%</span><span class="n">include</span> <span class="o">/</span><span class="n">mnt</span><span class="o">/</span><span class="n">stage2</span><span class="o">/</span><span class="n">ks_scripts</span><span class="o">/</span><span class="n">password</span><span class="o">.</span><span class="n">cfg</span> +<div class="highlight-default"><div class="highlight"><pre><span></span><span class="o">%</span><span class="n">include</span> <span class="o">/</span><span class="n">mnt</span><span class="o">/</span><span class="n">stage2</span><span class="o">/</span><span class="n">ks_scripts</span><span class="o">/</span><span class="n">password</span><span class="o">.</span><span class="n">cfg</span> <span class="o">...</span> <span class="o">%</span><span class="n">include</span> <span class="o">/</span><span class="n">tmp</span><span class="o">/</span><span class="n">network_line</span> @@ -1461,7 +1472,7 @@ http.parent_proxy.connect_attempts_timeout</td> <p>This snarfs up the contents and inlines them.</p> <p>If you only have one kind of hardware on your CDN it is probably best to just put the drive config right in the ks.cfg.</p> <p>If you have simple networking needs (we use bonded interfaces in most, but not all locations and we have several types of hardware meaning different ethernet interface names at the OS level etc.) then something like this:</p> -<div class="highlight-default"><div class="highlight"><pre><span class="ch">#!/bin/bash</span> +<div class="highlight-default"><div class="highlight"><pre><span></span><span class="ch">#!/bin/bash</span> <span class="n">source</span> <span class="o">/</span><span class="n">mnt</span><span class="o">/</span><span class="n">stage2</span><span class="o">/</span><span class="n">ks_scripts</span><span class="o">/</span><span class="n">network</span><span class="o">.</span><span class="n">cfg</span> <span class="n">echo</span> <span class="s2">"network --bootproto=static --activate --ipv6=$IPV6ADDR --ip=$IPADDR --netmask=$NETMASK --gateway=$GATEWAY --ipv6gateway=$GATEWAY --nameserver=$NAMESERVER --mtu=$MTU --hostname=$HOSTNAME"</span> <span class="o">>></span> <span class="o">/</span><span class="n">tmp</span><span class="o">/</span><span class="n">network</span><span class="o">.</span><span class="n">cfg</span> <span class="c1"># Note that this is an example and may not work at all.</span> @@ -1506,7 +1517,7 @@ http.parent_proxy.connect_attempts_timeout</td> </div> <div class="section" id="snapshot-crconfig"> <span id="rl-snapshot-crconfig"></span><span id="index-13"></span><h4>Snapshot CRConfig<a class="headerlink" href="#snapshot-crconfig" title="Permalink to this headline">¶</a></h4> -<p>Every 60 seconds Traffic Monitor will check with Traffic Ops to see if a new CRConfig snapshot exists; Traffic Monitor polls Traffic Ops for a new CRConfig, and Traffic Router polls Traffic Monitor for the same file. This is necessary to ensure that Traffic Monitor sees configuration changes first, which helps to ensure that the health and state of caches and delivery services propagates properly to Traffic Router. See <a class="reference internal" href="#rl-ccr-profile"><span class="std std-ref">CCR Profile or Traffic Router Profile</span></a> for more information on the CRConfig file.</p> +<p>Every 60 seconds Traffic Monitor will check with Traffic Ops to see if a new CRConfig snapshot exists; Traffic Monitor polls Traffic Ops for a new CRConfig, and Traffic Router polls Traffic Monitor for the same file. This is necessary to ensure that Traffic Monitor sees configuration changes first, which helps to ensure that the health and state of caches and delivery services propagates properly to Traffic Router. See <a class="reference internal" href="#rl-ccr-profile"><span class="std std-ref">Traffic Router Profile</span></a> for more information on the CRConfig file.</p> <p>To create a new snapshot, use the <em>Tools > Snapshot CRConfig</em> menu:</p> <blockquote> <div><ol class="arabic"> @@ -1644,7 +1655,7 @@ between the active CRConfig and the CRConfig about to be written.</p> <script type="text/javascript"> var DOCUMENTATION_OPTIONS = { URL_ROOT:'../', - VERSION:'1.8.1', + VERSION:'1.8-dev', COLLAPSE_INDEX:false, FILE_SUFFIX:'.html', HAS_SOURCE: true http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/5521f214/docs/latest/admin/traffic_portal.html ---------------------------------------------------------------------- diff --git a/docs/latest/admin/traffic_portal.html b/docs/latest/admin/traffic_portal.html index 3335e5f..056f29a 100644 --- a/docs/latest/admin/traffic_portal.html +++ b/docs/latest/admin/traffic_portal.html @@ -7,7 +7,7 @@ <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Traffic Portal Administration — Traffic Control 1.8.1 documentation </title> + <title>Traffic Portal Administration — Traffic Control 2.1-dev documentation </title> @@ -33,13 +33,10 @@ - <link rel="index" title="Index" - href="../genindex.html"/> - <link rel="search" title="Search" href="../search.html"/> - <link rel="top" title="Traffic Control 1.8.1 documentation" href="../index.html"/> + <link rel="top" title="Traffic Control 2.1-dev documentation" href="../index.html"/> <link rel="up" title="Administratorâs Guide" href="index.html"/> <link rel="next" title="Traffic Monitor Administration" href="traffic_monitor.html"/> - <link rel="prev" title="Managing Traffic Ops Extensions" href="traffic_ops_extensions.html"/> + <link rel="prev" title="Managing Traffic Ops Extensions" href="traffic_ops/extensions.html"/> <script src="_static/js/modernizr.min.js"></script> @@ -105,12 +102,15 @@ </ul> <ul class="current"> <li class="toctree-l1 current"><a class="reference internal" href="index.html">Administrator’s Guide</a><ul class="current"> -<li class="toctree-l2"><a class="reference internal" href="traffic_ops_install.html">Installing Traffic Ops</a></li> -<li class="toctree-l2"><a class="reference internal" href="traffic_ops_config.html">Configuring Traffic Ops</a></li> -<li class="toctree-l2"><a class="reference internal" href="traffic_ops_using.html">Using Traffic Ops</a></li> -<li class="toctree-l2"><a class="reference internal" href="traffic_ops_extensions.html">Managing Traffic Ops Extensions</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_ops/installation.html">Traffic Ops - Installing</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_ops/default_profiles.html">Traffic Ops - Default Profiles</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_ops/migration_from_10_to_20.html">Traffic Ops - Migrating from 1.x to 2.x</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_ops/configuration.html">Traffic Ops - Configuring</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_ops/using.html">Traffic Ops - Using</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_ops/extensions.html">Managing Traffic Ops Extensions</a></li> <li class="toctree-l2 current"><a class="current reference internal" href="#">Traffic Portal Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_monitor.html">Traffic Monitor Administration</a></li> +<li class="toctree-l2"><a class="reference internal" href="traffic_monitor_golang.html">Traffic Monitor Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_router.html">Traffic Router Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_stats.html">Traffic Stats Administration</a></li> <li class="toctree-l2"><a class="reference internal" href="traffic_server.html">Traffic Server Administration</a></li> @@ -121,10 +121,12 @@ </ul> <ul> <li class="toctree-l1"><a class="reference internal" href="../development/index.html">Developer’s Guide</a><ul> +<li class="toctree-l2"><a class="reference internal" href="../development/building.html">Building Traffic Control</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_ops.html">Traffic Ops</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_portal.html">Traffic Portal</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_router.html">Traffic Router</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_monitor.html">Traffic Monitor</a></li> +<li class="toctree-l2"><a class="reference internal" href="../development/traffic_monitor_golang.html">Traffic Monitor Golang</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_stats.html">Traffic Stats</a></li> <li class="toctree-l2"><a class="reference internal" href="../development/traffic_server.html">Traffic Server</a></li> </ul> @@ -162,14 +164,14 @@ <div class="rst-content"> <div role="navigation" aria-label="breadcrumbs navigation"> <ul class="wy-breadcrumbs"> - <li><a href="../index.html">Traffic Control 1.8.1</a> »</li> + <li><a href="../index.html">Traffic Control 2.1-dev</a> »</li> <li><a href="index.html">Administrator’s Guide</a> »</li> <li>Traffic Portal Administration</li> <li class="wy-breadcrumbs-aside"> - <a href="../_sources/admin/traffic_portal.rst.txt" rel="nofollow"> View page source</a> + <a href="../_sources/admin/traffic_portal.txt" rel="nofollow"> View page source</a> </li> </ul> @@ -181,7 +183,7 @@ <a href="traffic_monitor.html" class="btn btn-neutral float-right" title="Traffic Monitor Administration">Next <span class="fa fa-arrow-circle-right"></span></a> - <a href="traffic_ops_extensions.html" class="btn btn-neutral" title="Managing Traffic Ops Extensions"><span class="fa fa-arrow-circle-left"></span> Previous</a> + <a href="traffic_ops/extensions.html" class="btn btn-neutral" title="Managing Traffic Ops Extensions"><span class="fa fa-arrow-circle-left"></span> Previous</a> </div> @@ -237,7 +239,7 @@ <a href="traffic_monitor.html" class="btn btn-neutral float-right" title="Traffic Monitor Administration">Next <span class="fa fa-arrow-circle-right"></span></a> - <a href="traffic_ops_extensions.html" class="btn btn-neutral" title="Managing Traffic Ops Extensions"><span class="fa fa-arrow-circle-left"></span> Previous</a> + <a href="traffic_ops/extensions.html" class="btn btn-neutral" title="Managing Traffic Ops Extensions"><span class="fa fa-arrow-circle-left"></span> Previous</a> </div> @@ -266,10 +268,11 @@ <script type="text/javascript"> var DOCUMENTATION_OPTIONS = { URL_ROOT:'../', - VERSION:'1.8.1', + VERSION:'2.1-dev', COLLAPSE_INDEX:false, FILE_SUFFIX:'.html', - HAS_SOURCE: true + HAS_SOURCE: true, + SOURCELINK_SUFFIX: '' }; </script> <script type="text/javascript" src="../_static/jquery.js"></script>
