You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficcontrol.apache.org by gi...@apache.org on 2018/02/10 01:42:43 UTC
[2/4] incubator-trafficcontrol-website git commit: Update docs from
commit 0acf4cb1ff86da3665588150b8817780acf45a11
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/064f20d7/docs/master/admin/traffic_ops/using.html
----------------------------------------------------------------------
diff --git a/docs/master/admin/traffic_ops/using.html b/docs/master/admin/traffic_ops/using.html
index 81cd8da..f4cbfd9 100644
--- a/docs/master/admin/traffic_ops/using.html
+++ b/docs/master/admin/traffic_ops/using.html
@@ -499,7 +499,7 @@ must have an ssh key on the edge servers.</td>
</div>
<div class="section" id="daily-summary">
<h3>Daily Summary<a class="headerlink" href="#daily-summary" title="Permalink to this headline">ΒΆ</a></h3>
-<p>Displays daily max gbps and bytes served for all CDNs. In order for the graphs to appear, the ‘daily_bw_url’ and ‘daily_served_url’ parameters need to be be created, assigned to the global profile, and have a value of a grafana graph. For more information on configuring grafana, see the <a class="reference external" href="traffic_stats.html">Traffic Stats</a> section.</p>
+<p>Displays daily max gbps and bytes served for all CDNs. In order for the graphs to appear, the ‘daily_bw_url’ and ‘daily_served_url’ parameters need to be be created, assigned to the global profile, and have a value of a grafana graph. For more information on configuring grafana, see the <a class="reference external" href="../traffic_stats.html">Traffic Stats</a> section.</p>
</div>
</div>
<div class="section" id="server">
@@ -562,8 +562,8 @@ must have an ssh key on the edge servers.</td>
<p>The fields in the Delivery Service view are:</p>
<table border="1" class="docutils">
<colgroup>
-<col width="19%" />
-<col width="81%" />
+<col width="16%" />
+<col width="84%" />
</colgroup>
<thead valign="bottom">
<tr class="row-odd"><th class="head">Name</th>
@@ -604,7 +604,7 @@ must have an ssh key on the edge servers.</td>
<td>A human-readable name for the delivery service.</td>
</tr>
<tr class="row-odd"><td>DNS Bypass CNAME</td>
-<td> </td>
+<td>(For DNS routed delivery services only) This is a CNAME to respond to DNS requests with when a Delivery Service is unavailable.</td>
</tr>
<tr class="row-even"><td>DNS Bypass Ip</td>
<td>(For DNS routed delivery services only) This is the address to respond to A requests with when the max Bps or Max Tps for this delivery service are exceeded.</td>
@@ -613,7 +613,7 @@ must have an ssh key on the edge servers.</td>
<td>(For DNS routed delivery services only) This is the address to respond to AAAA requests with when the max Bps or Max Tps for this delivery service are exceeded.</td>
</tr>
<tr class="row-even"><td>DNS Bypass TTL</td>
-<td> </td>
+<td>(For DNS routed delivery services only) This is the TTL to use for DNS Bypass responses when a delivery service is unavailable.</td>
</tr>
<tr class="row-odd"><td>DSCP Tag</td>
<td>The DSCP value to mark IP packets to the client with.</td>
@@ -634,7 +634,7 @@ must have an ssh key on the edge servers.</td>
<td>(for HTTP routed delivery services only) This is the URL Traffic Router will redirect to when Geo Limit Failure. See <a class="reference internal" href="../traffic_router.html#rl-tr-ngb"><span class="std std-ref">GeoLimit Failure Redirect feature</span></a></td>
</tr>
<tr class="row-odd"><td>Geo Limit Countries</td>
-<td> </td>
+<td>A comma delimited list of Country Codes that will be allowed to make requests from the Delivery Service</td>
</tr>
<tr class="row-even"><td>Geo Miss Default Latitude</td>
<td>Default Latitude for this delivery service. When client localization fails for both Coverage Zone and Geo Lookup, the client will be routed as if it was at this lat.</td>
@@ -643,7 +643,7 @@ must have an ssh key on the edge servers.</td>
<td>Default Longitude for this delivery service. When client localization fails for both Coverage Zone and Geo Lookup, the client will be routed as if it was at this long.</td>
</tr>
<tr class="row-even"><td>Geolocation Provider</td>
-<td> </td>
+<td>An ordered list of Geolocation Providers to be used in make geo location decisions.</td>
</tr>
<tr class="row-odd"><td>Global Max Mbps</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
@@ -660,7 +660,7 @@ must have an ssh key on the edge servers.</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>Initial Dispersion</td>
-<td> </td>
+<td>For HTTP delivery services - the number of caches that will be used by Traffic Router. Traffic Router will consistently return the same caches as long as they are healthy.</td>
</tr>
<tr class="row-even"><td>IPv6 Routing Enabled</td>
<td>When set to yes, the Traffic Router will respond to AAAA DNS requests for the routed name of this delivery service. Otherwise, only A records will be served.</td>
@@ -669,19 +669,19 @@ must have an ssh key on the edge servers.</td>
<td>A unique string that identifies this delivery service.</td>
</tr>
<tr class="row-even"><td>Logs Enabled?</td>
-<td> </td>
+<td>Whether or not Traffic Logs is enabled for the delivery service. This feature is currently incomplete without Traffic Logs</td>
</tr>
<tr class="row-odd"><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>Long Description 2</td>
-<td> </td>
+<td>Another Long Description</td>
</tr>
<tr class="row-odd"><td>Long Description 3</td>
-<td> </td>
+<td>Another Long Description</td>
</tr>
<tr class="row-even"><td>Max DNS Answers</td>
-<td> </td>
+<td>For DNS delivery services - the max number of DNS answers that will be returned by Traffic Router.</td>
</tr>
<tr class="row-odd"><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="#id7" id="id3">[1]</a></td>
@@ -736,7 +736,7 @@ To set the qstring without the use of regex remap, or for further options, see <
</td>
</tr>
<tr class="row-odd"><td>Regional Geo-Blocking</td>
-<td> </td>
+<td><a class="reference external" href="../quick_howto/regionalgeo.html">See documentation here</a></td>
</tr>
<tr class="row-even"><td>Routing Name</td>
<td>The routing name to use for the delivery FQDN, i.e. <code class="docutils literal"><span class="pre"><routing-name>.<deliveryservice>.<cdn-domain></span></code>. It must be a valid hostname without periods. <a class="footnote-reference" href="#id8" id="id6">[2]</a></td>
@@ -745,16 +745,16 @@ To set the qstring without the use of regex remap, or for further options, see <
<td> </td>
</tr>
<tr class="row-even"><td>SSL Key Version</td>
-<td> </td>
+<td>The most recent version for SSL keys, this is incremented each time new certificates or generated or pasted in traffic ops</td>
</tr>
<tr class="row-odd"><td>Tenant</td>
<td>By selecting a tenant for the delivery service, you restrict access of that delivery service to only those users that belong to the same tenant or a parent tenant.</td>
</tr>
<tr class="row-even"><td>Traffic Router Request Headers</td>
-<td> </td>
+<td>Additional request header to be logged by Traffic Router</td>
</tr>
<tr class="row-odd"><td>Traffic Router Response Headers</td>
-<td> </td>
+<td>Reponse headers to be returned by Traffic Router for each request</td>
</tr>
</tbody>
</table>
@@ -817,7 +817,7 @@ on the RAM disks. Use this for linear TV. The MID tier is NOT bypassed for this
<td>The Delivery Service will be used to route to other delivery services. The target delivery services and the routing weights for those delivery services will be defined by an admin or steering user. For more information see the <a class="reference external" href="../traffic_router.html#steering-feature">steering feature</a> documentation</td>
</tr>
<tr class="row-odd"><td>CLIENT_STEERING</td>
-<td> </td>
+<td>Simliar to STEERING except that a client can send a request to Traffic Router with a query param of <cite>trred=false</cite> and Traffic Router will return a HTTP 200 reponse with a body that contians a list of Delivery Service URLs that the client connect to. Therefore the client is doing the steering, not the Traffic Router.</td>
</tr>
</tbody>
</table>