trafficcontrol-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From neu...@apache.org
Subject [incubator-trafficcontrol] 01/02: making a change in branch
Date Wed, 31 Jan 2018 20:59:26 GMT
This is an automated email from the ASF dual-hosted git repository.

neuman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-trafficcontrol.git

commit 7a35935d1e50f5d11eef2c1da153c8cb6aff62d3
Author: Ashish Timilsina <timilsina.ashish.03@gmail.com>
AuthorDate: Tue Jan 30 11:27:44 2018 -0700

    making a change in branch
---
 docs/source/admin/traffic_server.rst | 65 ++++++++++++++++++------------------
 1 file changed, 33 insertions(+), 32 deletions(-)

diff --git a/docs/source/admin/traffic_server.rst b/docs/source/admin/traffic_server.rst
index 9283708..1a8697e 100644
--- a/docs/source/admin/traffic_server.rst
+++ b/docs/source/admin/traffic_server.rst
@@ -1,17 +1,17 @@
-.. 
-.. 
+..
+..
 .. Licensed under the Apache License, Version 2.0 (the "License");
 .. you may not use this file except in compliance with the License.
 .. You may obtain a copy of the License at
-.. 
+..
 ..     http://www.apache.org/licenses/LICENSE-2.0
-.. 
+..
 .. Unless required by applicable law or agreed to in writing, software
 .. distributed under the License is distributed on an "AS IS" BASIS,
 .. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 .. See the License for the specific language governing permissions and
 .. limitations under the License.
-.. 
+..
 
 *****************************
 Traffic Server Administration
@@ -19,14 +19,17 @@ Traffic Server Administration
 Installing Traffic Server
 =========================
 
-#.  Get the Traffic Server RPM and the astats RPM.
+#. Build the Traffic Server RPM: ::
 
-    Sample command: ::
+    http://archive.apache.org/dist/trafficserver/?C=M;O=D
+#. Build the astats RPM using the appropriate version number: ::
 
-        wget http://traffic-control-cdn.net/downloads/1.7.0/RELEASE-1.7.0/trafficserver-5.3.2-759.ee14bbe.el6.x86_64.rpm
-        wget http://traffic-control-cdn.net/downloads/1.6.1/RELEASE-1.6.1/astats_over_http-1.2-8.el6.x86_64.rpm
+    https://github.com/apache/incubator-trafficcontrol/tree/<version>/traffic_server
+
+   Sample link: ::
+
+     https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_server
 
-    (astats was not released as part of 1.7, so in this examples 1.6.1 was used)
 #.  Install Traffic Server and astats: ::
 
         sudo yum -y install trafficserver-*.rpm astats_over_http*.rpm
@@ -36,15 +39,14 @@ Installing Traffic Server
     #. Select **Servers**.
     #. Scroll to the bottom of the page and click **Add Server**.
     #. Complete the "Required Info:" section:
-        * Set 'Interface Name' to the name of the interface from which traffic server delivers
content. 
+        * Set 'Interface Name' to the name of the interface from which traffic server delivers
content.
         * Set 'Type' to 'MID' or 'EDGE'.
-
     #. Click **Submit**.
     #. Click **Save**.
-    #. Click **Online Server**. 
+    #. Click **Online Server**.
     #. Verify that the server status is now listed as **Reported**
 
-#.  Install the ORT script and run it in 'badass' mode to create the initial configuration,
see :ref:`reference-traffic-ops-ort` 
+#.  Install the ORT script and run it in 'badass' mode to create the initial configuration,
see :ref:`reference-traffic-ops-ort`
 
 #.  Start the service: ``sudo service trafficserver start``
 
@@ -52,26 +54,26 @@ Installing Traffic Server
 
 #.  Verify that the installation is good:
 
-    #. Make sure that the service is running: ``sudo service trafficserver status``
+    #. Make sure that the service is running: ``sudo systemctl status trafficserver``
 
-    #. Assuming a traffic monitor is already installed, browse to it, and verify that the
traffic server appears in the "Cahce States" table, in white.
+    #. Assuming a traffic monitor is already installed, browse to it, i.e. http://<trafficmonitorURL>,
and verify that the traffic server appears in the "Cache States" table, in white.
 
 
 .. _reference-traffic-ops-ort:
 
 Configuring Traffic Server
 ==========================
-All of the Traffic Server application configuration files are generated by Traffic Ops and
installed by way of the traffic_ops_ort.pl script. 
+All of the Traffic Server application configuration files are generated by Traffic Ops and
installed by way of the traffic_ops_ort.pl script.
 The traffic_ops_ort.pl should be installed on all caches (by puppet or other non Traffic
Ops means), usually in /opt/ort. It is used to do the initial install of the config files
when the cache is being deployed, and to keep the config files up to date when the cache is
already in service.  The usage message of the script is shown below: ::
 
     $ sudo /opt/ort/traffic_ops_ort.pl
-    Thu May 26 15:52:11 UTC 2016
     ====-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-====
     Usage: ./traffic_ops_ort.pl <Mode> <Log_Level> <Traffic_Ops_URL> <Traffic_Ops_Login>
[optional flags]
       <Mode> = interactive - asks questions during config process.
       <Mode> = report - prints config differences and exits.
       <Mode> = badass - attempts to fix all config differences that it can.
       <Mode> = syncds - syncs delivery services with what is configured in Traffic
Ops.
+      <Mode> = revalidate - checks for updated revalidations in Traffic Ops and applies
them.  Requires Traffic Ops 2.1.
 
       <Log_Level> => ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, NONE
 
@@ -81,6 +83,7 @@ The traffic_ops_ort.pl should be installed on all caches (by puppet or other
non
 
       [optional flags]:
         dispersion=<time>      => wait a random number between 0 and <time>
before starting. Default = 300.
+        login_dispersion=<time>  => wait a random number between 0 and <time>
before login. Default = 0.
         retries=<number>       => retry connection to Traffic Ops URL <number>
times. Default = 3.
         wait_for_parents=<0|1> => do not update if parent_pending = 1 in the update
json. Default = 1, wait for parents.
     ====-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-====
@@ -89,16 +92,15 @@ The traffic_ops_ort.pl should be installed on all caches (by puppet or
other non
 Installing the ORT script
 --------------------------
 
-#.  The ORT script is not a part of the traffic server distribution. In this sample session,
we get it manually from github: ::
+#.  Build the ORT script RPM and install it: ::
 
-        sudo mkdir /opt/ort
-        sudo wget -P /opt/ort https://raw.githubusercontent.com/apache/incubator-trafficcontrol/1.7.x/traffic_ops/bin/traffic_ops_ort.pl
-        sudo chmod +x /opt/ort/traffic_ops_ort.pl
+        sudo wget https://builds.apache.org/view/S-Z/view/TrafficControl/job/incubator-trafficcontrol-2.1.x-build/lastSuccessfulBuild/artifact/dist/traffic_ops_ort-2.1.0-6807.1dcd512f.el7.x86_64.rpm
+        sudo yum install traffic_ops_ort*.rpm
 
-#.  Install modules required by ORT: ``sudo yum -y install perl-JSON perl-Crypt-SSLeay``
+#.  Install modules required by ORT if needed: ``sudo yum -y install perl-JSON perl-Crypt-SSLeay``
 
-#.  For initial configuration or when major changes (like a Profile change) need to be made,
run the script in "badass mode". All required rpm packages 
-    will be installed, all Traffic Server config files will be fetched and installed, and
(if needed) the Traffic Server application will be restarted.  
+#.  For initial configuration or when major changes (like a Profile change) need to be made,
run the script in "badass mode". All required rpm packages
+    will be installed, all Traffic Server config files will be fetched and installed, and
(if needed) the Traffic Server application will be restarted.
 
     Example run below: ::
 
@@ -107,18 +109,18 @@ Installing the ORT script
     .. Note:: First run gives a lot of state errors that are expected. The "badass" mode
fixes these issue s. Run it a second time, this should be cleaner.
        Also, note that many ERROR messages emitted by ORT are actually information messages.
Do not panic.
 
-#.  Create a cron entry for running ort in 'syncds' mode every 15 minutes. 
+#.  Create a cron entry for running ort in 'syncds' mode every 15 minutes.
     This makes traffic control check periodically if 'Queue Updates' was run on Traffic Ops,
and it so, get the updated configuration.
 
-    Run ``sudo crontab -e`` and add the following line :: 
+    Run ``sudo crontab -e`` and add the following line ::
 
   	  	*/15 * * * * /opt/ort/traffic_ops_ort.pl syncds warn https://traffops.kabletown.net
admin:password --login_dispersion=30 --dispersion=180 > /tmp/ort/syncds.log 2>&1
 
     Changing ``https://traffops.kabletown.net``, ``admin``, and ``password`` to your CDN
URL and credentials.
 
-    .. Note:: By default, running ort on an edge traffic server waits for it's parent (mid)
servers to download their configuration before 
-       it downloads it's own configuration. Because of this, scheduling ort for running every
15 minutes (with 5 minutes default dispersion) means 
-       that it might take up to ~35 minutes for a "Queue Updates" operation to affect all
traffic servers.  To customize this dispersion time, use 
+    .. Note:: By default, running ort on an edge traffic server waits for it's parent (mid)
servers to download their configuration before
+       it downloads it's own configuration. Because of this, scheduling ort for running every
15 minutes (with 5 minutes default dispersion) means
+       that it might take up to ~35 minutes for a "Queue Updates" operation to affect all
traffic servers.  To customize this dispersion time, use
        the command line option --dispersion=x where x is the number of seconds for the dispersion
period.  Servers will select a random number from
        within this dispersion period to being pulling down configuration files from Traffic
Ops.  Another option, --login_dispersion=x can be used.
        This option creates a dispersion period after the job begins during which ORT will
wait before logging in and checking Traffic Ops for updates
@@ -137,7 +139,6 @@ Installing the ORT script
 #.  If Rapid Revalidate is enabled in Traffic Ops, create a second cron job for revalidation
checks.  ORT will not check revalidation files if Rapid Revalidate
     is enabled. This setting allows for a separate check to be performed every 60 seconds
to verify if a revalidation update has been made.
 
-    Run ``sudo crontab -e`` and add the following line :: 
+    Run ``sudo crontab -e`` and add the following line ::
 
         */1 * * * * /opt/ort/traffic_ops_ort.pl revalidate warn https://traffops.kabletown.net
admin:password --login_dispersion=30 > /tmp/ort/syncds.log 2>&1
-

-- 
To stop receiving notification emails like this one, please contact
neuman@apache.org.

Mime
View raw message