http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png b/docs/latest/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png deleted file mode 100644 index 9998e81..0000000 Binary files a/docs/latest/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/12m.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/12m.png b/docs/latest/_images/12m.png deleted file mode 100644 index 36ce934..0000000 Binary files a/docs/latest/_images/12m.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png b/docs/latest/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png deleted file mode 100644 index 1a6ad24..0000000 Binary files a/docs/latest/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png b/docs/latest/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png deleted file mode 100644 index 96fddab..0000000 Binary files a/docs/latest/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/D22DCAA3-18CC-48F4-965B-5312993F9820.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/D22DCAA3-18CC-48F4-965B-5312993F9820.png b/docs/latest/_images/D22DCAA3-18CC-48F4-965B-5312993F9820.png deleted file mode 100644 index 59d5b8e..0000000 Binary files a/docs/latest/_images/D22DCAA3-18CC-48F4-965B-5312993F9820.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png b/docs/latest/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png deleted file mode 100644 index 6d05b19..0000000 Binary files a/docs/latest/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/bad.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/bad.png b/docs/latest/_images/bad.png deleted file mode 100644 index 485e3da..0000000 Binary files a/docs/latest/_images/bad.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/bad1.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/bad1.png b/docs/latest/_images/bad1.png deleted file mode 100644 index 485e3da..0000000 Binary files a/docs/latest/_images/bad1.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/cache_groups_1.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/cache_groups_1.png b/docs/latest/_images/cache_groups_1.png deleted file mode 100644 index d03d320..0000000 Binary files a/docs/latest/_images/cache_groups_1.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/clock-black.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/clock-black.png b/docs/latest/_images/clock-black.png deleted file mode 100644 index 4783c01..0000000 Binary files a/docs/latest/_images/clock-black.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/dnssec01.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/dnssec01.png b/docs/latest/_images/dnssec01.png deleted file mode 100644 index 044538f..0000000 Binary files a/docs/latest/_images/dnssec01.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/dnssec02.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/dnssec02.png b/docs/latest/_images/dnssec02.png deleted file mode 100644 index 82fa75a..0000000 Binary files a/docs/latest/_images/dnssec02.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/dnssec03.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/dnssec03.png b/docs/latest/_images/dnssec03.png deleted file mode 100644 index 1fc3cce..0000000 Binary files a/docs/latest/_images/dnssec03.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/dnssec04.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/dnssec04.png b/docs/latest/_images/dnssec04.png deleted file mode 100644 index f9b8d32..0000000 Binary files a/docs/latest/_images/dnssec04.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/federation01.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/federation01.png b/docs/latest/_images/federation01.png deleted file mode 100644 index bbbd924..0000000 Binary files a/docs/latest/_images/federation01.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/federation02.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/federation02.png b/docs/latest/_images/federation02.png deleted file mode 100644 index 9db970e..0000000 Binary files a/docs/latest/_images/federation02.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/federation03.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/federation03.png b/docs/latest/_images/federation03.png deleted file mode 100644 index abd52d2..0000000 Binary files a/docs/latest/_images/federation03.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/federation04.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/federation04.png b/docs/latest/_images/federation04.png deleted file mode 100644 index dd5a812..0000000 Binary files a/docs/latest/_images/federation04.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/fwda.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/fwda.png b/docs/latest/_images/fwda.png deleted file mode 100644 index ba63bee..0000000 Binary files a/docs/latest/_images/fwda.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/fwda1.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/fwda1.png b/docs/latest/_images/fwda1.png deleted file mode 100644 index ba63bee..0000000 Binary files a/docs/latest/_images/fwda1.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/good.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/good.png b/docs/latest/_images/good.png deleted file mode 100644 index 84d96cd..0000000 Binary files a/docs/latest/_images/good.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/good1.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/good1.png b/docs/latest/_images/good1.png deleted file mode 100644 index 84d96cd..0000000 Binary files a/docs/latest/_images/good1.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/graph.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/graph.png b/docs/latest/_images/graph.png deleted file mode 100644 index ea0b4c5..0000000 Binary files a/docs/latest/_images/graph.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/info.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/info.png b/docs/latest/_images/info.png deleted file mode 100644 index 5680f06..0000000 Binary files a/docs/latest/_images/info.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/mso-enable.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/mso-enable.png b/docs/latest/_images/mso-enable.png deleted file mode 100644 index 9932de1..0000000 Binary files a/docs/latest/_images/mso-enable.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/mso-rank.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/mso-rank.png b/docs/latest/_images/mso-rank.png deleted file mode 100644 index de80ac5..0000000 Binary files a/docs/latest/_images/mso-rank.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/regionalgeo01.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/regionalgeo01.png b/docs/latest/_images/regionalgeo01.png deleted file mode 100644 index 0443a17..0000000 Binary files a/docs/latest/_images/regionalgeo01.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/regionalgeo02.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/regionalgeo02.png b/docs/latest/_images/regionalgeo02.png deleted file mode 100644 index 5530920..0000000 Binary files a/docs/latest/_images/regionalgeo02.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/regionalgeo03.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/regionalgeo03.png b/docs/latest/_images/regionalgeo03.png deleted file mode 100644 index ce2676b..0000000 Binary files a/docs/latest/_images/regionalgeo03.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/steering01.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/steering01.png b/docs/latest/_images/steering01.png deleted file mode 100644 index 1515011..0000000 Binary files a/docs/latest/_images/steering01.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/steering02.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/steering02.png b/docs/latest/_images/steering02.png deleted file mode 100644 index c2fc22c..0000000 Binary files a/docs/latest/_images/steering02.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/steering03.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/steering03.png b/docs/latest/_images/steering03.png deleted file mode 100644 index f4b110d..0000000 Binary files a/docs/latest/_images/steering03.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/steering04.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/steering04.png b/docs/latest/_images/steering04.png deleted file mode 100644 index 0ab962b..0000000 Binary files a/docs/latest/_images/steering04.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_images/traffic_control_overview_3.png ---------------------------------------------------------------------- diff --git a/docs/latest/_images/traffic_control_overview_3.png b/docs/latest/_images/traffic_control_overview_3.png deleted file mode 100644 index 594983b..0000000 Binary files a/docs/latest/_images/traffic_control_overview_3.png and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/index.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/index.rst.txt b/docs/latest/_sources/admin/index.rst.txt deleted file mode 100644 index e92f5e2..0000000 --- a/docs/latest/_sources/admin/index.rst.txt +++ /dev/null @@ -1,48 +0,0 @@ -.. -.. -.. 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. -.. - -Administrator's Guide -********************* - -Traffic Control is distributed in source form for the developer, but also as a binary package. This guide details how to install and configure a Traffic Control CDN using the binary packages, as well as how to perform common operations running a CDN. - -When installing a complete CDN from scratch, a sample recommended order is: - -1. Traffic Ops -2. Traffic Vault (Riak) -3. Apache Traffic Server Mid-Tier Caches -4. Apache Traffic Server Edge Caches -5. Traffic Monitor -6. Traffic Router -7. Traffic Stats -8. Traffic Portal - -Once everything is installed, you will need to configure the servers to talk to each other. You will also need Origin server(s), which the Mid-Tier Cache(s) get content from. An Origin server is simply an HTTP(S) server which serves the content you wish to cache on the CDN. - -.. toctree:: - :maxdepth: 3 - - traffic_ops_install.rst - traffic_ops_config.rst - traffic_ops_using.rst - traffic_ops_extensions.rst - traffic_portal.rst - traffic_monitor.rst - traffic_router.rst - traffic_stats.rst - traffic_server.rst - traffic_vault.rst - quick_howto/index.rst - http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/quick_howto/dnssec.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/quick_howto/dnssec.rst.txt b/docs/latest/_sources/admin/quick_howto/dnssec.rst.txt deleted file mode 100644 index d336057..0000000 --- a/docs/latest/_sources/admin/quick_howto/dnssec.rst.txt +++ /dev/null @@ -1,72 +0,0 @@ -.. -.. -.. 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. -.. - -.. _rl-dnssec-qht: - -**************** -Configure DNSSEC -**************** - -.. Note:: In order for Traffic Ops to successfully store keys in Traffic Vault, at least one Riak Server needs to be configured in Traffic Ops. See the `Traffic Vault admin page <../traffic_vault.html>`_ for more information. - -.. Note:: Currently DNSSEC is only supported for DNS delivery services. - -1) Go to Tools->Manage DNSSEC Keys choose a CDN and click Manage DNSSEC Keys - -.. image:: dnssec01.png - :scale: 100% - :align: center - -2) Generate keys for a CDN by clicking Generate Keys then entering the following information: - - - Expiration in days for the Zone Signing Key (ZSK) - - Expiration in days for the Key Signing Key (KSK) - - Effective Date - - Once the required information has been entered click on the 'Generate Keys' button. - - Depending upon the number of Delivery Services in the CDN, generating DNSSEC keys may take serveral seconds. - -.. image:: dnssec02.png - :scale: 100% - :align: center - -3) In order for DNSSEC to work properly, the DS Record information needs to be added to the parent zone of the CDN's domain (e.g. If the CDN's domain is 'cdn.kabletown.net' the parent zone is 'kabletown.net'). - - If you control your parent zone you can enter this information yourself, otherwise you will need to work with your DNS team to get the DS Record added to the parent zone. - -.. image:: dnssec03.png - :scale: 70% - :align: center - -4) Once DS Record information has been added to the parent zone, DNSSEC needs to be activated for the CDN so that Traffic Router will sign responses. - - Click on Tools -> Manage DNSSEC Keys -> Choose your CDN -> On the Manage DNSSEC Keys page click the activate DNSSEC Keys button. - - This will add a 'dnssec.enabled = "true"' entry to CRConfig for the chosen CDN. - -.. image:: dnssec04.png - :scale: 70% - :align: center - -5) DNSSEC should now be active on your CDN and Traffic Router should be signing responses. - - A dig command with +dnssec added should show you the signed responses. - - ``dig edge.cdn.kabletown.net. +dnssec`` - -6) When KSK expiration is approaching (default 365 days), it is necessary to manually generate a new KSK for the TLD (Top Level Domain) and add the DS Record to the parent zone. In order to avoid signing errors, it is suggested that an effective date is chosen which allows time for the DS Record to be added to the parent zone before the new KSK becomes active. - - A new KSK can be generated by clicking the 'Regenerate KSK' button on the Manage DNSSEC Keys screen (see screenshot above). http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/quick_howto/federations.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/quick_howto/federations.rst.txt b/docs/latest/_sources/admin/quick_howto/federations.rst.txt deleted file mode 100644 index a17122c..0000000 --- a/docs/latest/_sources/admin/quick_howto/federations.rst.txt +++ /dev/null @@ -1,135 +0,0 @@ -.. -.. -.. 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. -.. - -.. _rl-federations-qht: - -********************* -Configure Federations -********************* - -1) Create a user with a federations role (Misc -> Users -> Add User). This user will have the ability to perform the following actions: - - - Edit the federation - - Delete the federation - - Add IPV4 resolvers - - Add IPV6 resolvers - -.. image:: federation01.png - :scale: 100% - :align: center - -2) As a user with admin priveleges, create a Federation Mapping by going to Delivery Services -> Federations and then clicking 'Add Federation Mapping' - -3) Choose the Delivery Service for the federation to be mapped to and assign it to the Federation User; click Add. - -.. image:: federation02.png - :scale: 100% - :align: center - -4) After the Federation is added, Traffic Ops will display the Federation. - - Changes can be made at this time or the Federation can be deleted. Notice that no resolvers have been added to the fedeation yet. This can only be done by the federation user created in step 1. - - If no further action is necessary, the Close button will close the window and display the list of all Federations. - -.. image:: federation03.png - :scale: 100% - :align: center - - -**The Federation user can now add resolvers to the Federation Mapping in Traffic Ops.** - -5) The federation user logs to traffic ops and stores the mojolicious cookie. The mojolicious cookie can be obtained manually using the debug tools on a web browser or via curl. - - Example:: - - $ curl -i -XPOST "http://localhost:3000/api/1.1/user/login"; -H "Content-Type: application/json" -d '{ "u": "federation_user1", "p": "password" }' - - HTTP/1.1 200 OK - Date: Wed, 02 Dec 2015 21:12:06 GMT - Content-Length: 65 - Access-Control-Allow-Credentials: true - Content-Type: application/json - Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE - Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1MTI2LCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---06b4f870d809d82a91433e92eae8320875c3e8b0; expires=Thu, 03 Dec 2015 01:12:06 GMT; path=/; HttpOnly - Server: Mojolicious (Perl) - Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept - Cache-Control: no-cache, no-store, max-age=0, must-revalidate - Connection: keep-alive - Access-Control-Allow-Origin: http://localhost:8080 - - {"alerts":[{"level":"success","text":"Successfully logged in."}]} - -6) The federation user sends a request to Traffic Ops to add IPV4 and/or IPV6 resolvers - - - Example:: - - $ curl -ki -H "Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1MTI2LCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---06b4f870d809d82a91433e92eae8320875c3e8b0;" -XPUT 'http://localhost:3000/api/1.2/federations' -d ' - {"federations": [ - { "deliveryService": "images-c1", - "mappings": - { "resolve4": [ "8.8.8.8/32", "8.8.4.4/32" ], - "resolve6": ["2001:4860:4860::8888/128", "2001:4860:4860::8844"] - } - } - ] - }' - - HTTP/1.1 200 OK - Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1OTQyLCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---b42be0749415cefd1d14e1a91bb214845b4de556; expires=Thu, 03 Dec 2015 01:25:42 GMT; path=/; HttpOnly - Server: Mojolicious (Perl) - Date: Wed, 02 Dec 2015 21:25:42 GMT - Content-Length: 74 - Access-Control-Allow-Credentials: true - Content-Type: application/json - Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE - Cache-Control: no-cache, no-store, max-age=0, must-revalidate - Access-Control-Allow-Origin: http://localhost:8080 - Connection: keep-alive - Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept - - {"response":"federation_user1 successfully created federation resolvers."} - -7) The resolvers added by the federation user will now visible in Traffic Ops. - -.. image:: federation04.png - :scale: 100% - :align: center - -8) Any requests made from a client that resolves to one of the federation resolvers will now be given a CNAME from Traffic Router. - - Example:: - - $ dig @tr.kabletown.net edge.images-c1.kabletown.net - - ; <<>> DiG 9.7.3-RedHat-9.7.3-2.el6 <<>> @tr.kabletown.net edge.images-c1.kabletown.net - ; (1 server found) - ;; global options: +cmd - ;; Got answer: - ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45110 - ;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 - ;; WARNING: recursion requested but not available - - ;; QUESTION SECTION: - ;edge.images-c1.kabletown.net. IN A - - ;; ANSWER SECTION: - edge.images-c1.kabletown.net. 30 IN CNAME img.mega-cdn.net. - - ;; Query time: 9 msec - ;; SERVER: 10.10.10.10#53(10.10.10.10) - ;; WHEN: Wed Dec 2 22:05:26 2015 - ;; MSG SIZE rcvd: 84 \ No newline at end of file http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/quick_howto/index.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/quick_howto/index.rst.txt b/docs/latest/_sources/admin/quick_howto/index.rst.txt deleted file mode 100644 index 96f098f..0000000 --- a/docs/latest/_sources/admin/quick_howto/index.rst.txt +++ /dev/null @@ -1,28 +0,0 @@ -.. -.. -.. 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. -.. - -Quick How To Guides -******************* - -Traffic Control is a complicated system, and documenting it is not trivial. Sometimes a picture says more than a thousand words, so here are some screen shot based tutorials on how to use some of the more involved features. - -.. toctree:: - :maxdepth: 3 - - multi_site.rst - dnssec.rst - federations.rst - regionalgeo.rst - steering.rst http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/quick_howto/multi_site.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/quick_howto/multi_site.rst.txt b/docs/latest/_sources/admin/quick_howto/multi_site.rst.txt deleted file mode 100644 index 32b5436..0000000 --- a/docs/latest/_sources/admin/quick_howto/multi_site.rst.txt +++ /dev/null @@ -1,95 +0,0 @@ -.. -.. -.. 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. -.. - -.. _rl-multi-site-origin-qht: - -*************************** -Configure Multi Site Origin -*************************** - -1) Create "cachegroups" for the origin locations, and assign the appropriate parent-child relationship between the mid cg's and org cgs (click the image to see full size): - -.. image:: C5C4CD22-949A-48FD-8976-C673083E2177.png - :scale: 100% - :align: center - -2) Create a profile to assign to each of the origins: - -.. image:: 19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png - :scale: 100% - :align: center - -3) Create server entries for the origination vips: - -.. image:: D28614AA-9758-45ED-9EFD-3A284FC4218E.png - :scale: 100% - :align: center - -4) Check the multi-site check box in the delivery service screen and make sure that Content Routing Type is set to HTTP_LIVE_NATL: - -.. image:: mso-enable.png - :scale: 100% - :align: center - -5) Assign the org servers to the delivery service that will have the multi site feature: - -.. image:: 066CEF4F-C1A3-4A89-8B52-4F72B0531367.png - :scale: 100% - :align: center - -.. Note:: âOrigin Server Base URLâ uniqueness: In order to enable MID caches to distinguish delivery services by different MSO algorithms while performing parent failover, it requires that âOrigin Server Base URLâ (OFQDN) for each MSO enabled delivery service is unique unless the exceptions listed afterwards. This means that the OFQDN of a MSO enabled delivery service should be different with the OFQDNs of any other delivery service, regardless of whether they are MSO enabled or not. The exceptions are: - 1) If there are multiple CDNs created on the same Traffic Ops, delivery services across different CDNs may have the same OFQDN configured. - 2) If several delivery services in the same CDN have the same MSO algorithm configured, they may share the same OFQDN. - 3) If delivery services are assigned with different MID cache groups respectively, they can share the same OFQDN. - -6) Select an option from the "Multi Site Origin Algorithm" drop-down list. Four MSO algorithms are supported: - -+------------------+--------------------------------------------------------------------------------------------------------------------+ -| Option | Description | -+==================+====================================================================================================================+ -| Consistent hash | Origin server selection is based on the consistent hash of requested URLs. | -+------------------+--------------------------------------------------------------------------------------------------------------------+ -| Primary/back | Round robin selection does not occur. The first origin server is selected unless it fails. | -| | If the first fails, the second and other following origin servers will be tried by order. | -| | Order is defined by 2 factors - if the origin server's cachegroup is configured as the | -| | parent cachegroup for the mid, then this server will be used as the primary. The same rules | -| | apply for secondary parents, in order. Within the cachegroups, the rank parameter will sort | -| | order further. If no parents are defined at the mid, then only rank is considered. | -+------------------+--------------------------------------------------------------------------------------------------------------------+ -| Strict | MID caches serve requests strictly in turn. For example: origin server 1 serves the first request, | -| round-robin | origin server 2 serves the second request, and so on. | -+------------------+--------------------------------------------------------------------------------------------------------------------+ -| IP based | MID cache goes through the origin server list in a round robin-based on the IP address of EDGE cache. | -| round-robin | | -+------------------+--------------------------------------------------------------------------------------------------------------------+ - -7) Optionally, there are two configuration options that can set the order of the origins used if "Primary/backup" is selected for "Multi Site Origin Algorithm". By creating location-based cachegroups and assigning the origin servers accordingly and defining these cachegroups as parents for specific mids, location-based primary/secondary selection can be made. If primary/secondary selection should be the same for all mids, then a new parameter ârankâ should be configured for each origin server profile. Origin servers with lower values of rank have higher ranking in the origin server list on MID caches, e.g. OS with rank of "2" precedes OS with the rank of "5". For any OS, if rank value is not defined in its profile, its rank value will default to â1â. In the event that both location based cachegroups are used alongside rank, sorting will be by cachegroup first and rank second. In this way it is possible to have specific backup servers for use at specific locations. - -.. image:: mso-rank.png - :scale: 60% - :align: center - -8) Assign the parent.config location parameter to the MID profile: - -.. image:: D22DCAA3-18CC-48F4-965B-5312993F9820.png - :scale: 100% - :align: center - - -9) Configure the mid hdr_rewrite on the delivery service, example: :: - - cond %{REMAP_PSEUDO_HOOK} __RETURN__ set-config proxy.config.http.parent_origin.dead_server_retry_enabled 1 __RETURN__ set-config proxy.config.http.parent_origin.simple_retry_enabled 1 __RETURN__ set-config proxy.config.http.parent_origin.simple_retry_response_codes "400,404,412" __RETURN__ set-config proxy.config.http.parent_origin.dead_server_retry_response_codes "502,503" __RETURN__ set-config proxy.config.http.connect_attempts_timeout 2 __RETURN__ set-config proxy.config.http.connect_attempts_max_retries 2 __RETURN__ set-config proxy.config.http.connect_attempts_max_retries_dead_server 1 __RETURN__ set-config proxy.config.http.transaction_active_timeout_in 5 [L] __RETURN__ - -10) Turn on parent_proxy_routing in the MID profile. http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/quick_howto/regionalgeo.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/quick_howto/regionalgeo.rst.txt b/docs/latest/_sources/admin/quick_howto/regionalgeo.rst.txt deleted file mode 100644 index a903c8a..0000000 --- a/docs/latest/_sources/admin/quick_howto/regionalgeo.rst.txt +++ /dev/null @@ -1,109 +0,0 @@ -.. -.. -.. 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. -.. - -.. _rl-regionalgeo-qht: - -************************************** -Configure Regional Geo-blocking (RGB) -************************************** - -.. Note:: RGB is only supported for HTTP delivery services. - -1) Prepare RGB configuration file - -RGB uses a configuration file in JSON format to define regional geo-blocking rules for delivery services. The file needs to be put on an HTTP server accessible to Traffic Router. An example of the JSON is as follows:: - - { - "deliveryServices": - [ - { - "deliveryServiceId": "hls-live", - "urlRegex": ".*live4\\.m3u8", - "geoLocation": {"includePostalCode":["N0H", "L9V", "L9W"]}, - "redirectUrl": "http://third-party.com/blacked_out.html"; - }, - { - "deliveryServiceId": "hls-live", - "urlRegex": ".*live5\\.m3u8", - "ipWhiteList": [185.68.71.9/22","142.232.0.79/24"], - "geoLocation": {"excludePostalCode":["N0H", "L9V"]}, - "redirectUrl": "/live5_low_bitrate.m3u8" - } - ] - } - -* The value of "deliveryServiceId" shall be equal to the âXML IDâ field of the intended delivery service defined on Traffic Ops. - -* âurlRegexâ is to match request URLs. The URLs matching the regex are applicable to the rule. - -* âgeoLocationâ currently supports âincludePostalCodeâ and âexcludePostalCodeâ attribute. When âincludePostalCodeâ attribute is used, only the clients whose FSAs are in the âincludePostalCodeâ list are able to view the content represented by âurlRegexâ. When âexcludePostalCodeâ is used, any client whose FSA are not in the âexcludePostalCodeâ list are allowed to view the content. âincludePostalCodeâ and âexcludePostalCodeâ are mutually exclusive in one rule. (FSA: Forward Sortation Area, first three postal characters of Canadian postal codes) - -* âredirectUrlâ is the URL that will be responded to the blocked clients. Without a domain name in the URL, the URL will still be served in the same delivery service. Thus Traffic Router will redirect the client to a chosen cache server assigned to the delivery service. If the URL includes a domain name, Traffic Router simply redirects the client to the defined URL. In the later case, the redirect URL must not match the âurlRegexâ part to avoid HTTP 302 loop on Traffic Router. - -* âipWhiteListâ is an optional element. It includes a list of CIDR (Classless Inter-Domain Routing) blocks indicating the IPv4 subnets that are allowed by the rule. If this list exists and the value is not empty, client IP will be matched against the CIDR list, and if there is any match, the request will be allowed and no postal code matching logic is needed. If there is no match in the white list, postal code matching logic will be processed further. - - -2) Add RGB parameters on Traffic Ops - -The two new parameters in following table are required to be added into CRConfig.json: - -* "regional_geoblocking.polling.url": the HTTP URL of RGB configuration file. Traffic Router will fetch the file from this URL. -* "regional_geoblocking.polling.interval": the interval that Traffic Router polls the RGB configuration file. - -.. image:: regionalgeo01.png - :scale: 100% - :align: center - -3) Enable RGB for a delivery service - -.. image:: regionalgeo02.png - :scale: 100% - :align: center - -4) Make configuration effective - -Go to Tools->Snapshot CRConfig, perform âDiff CRConfigâ and click "Write CRConfig". - -.. image:: regionalgeo03.png - :scale: 70% - :align: center - -5) Traffic Router access log with RGB - -RGB extends the field of "rtype" and adds a new field "rgb" in Traffic Router access.log to help to monitor the working of this feature. - -For "rtype", RGALT indicates that a request is redirected to an alternate URL by RGB; RGDENY indicates that a request is denied by RGB because there is no matching rule in JSON for this request. - -For "rgb", when RGB is enabled, it will be non-empty with following format:: - - {FSA}:{allowed/disallowed}:{include/exclude postal}:{fallback config/current config}:{allowed by whitelist/otherwise} - - -* {FSA}: It is the clientâs FSA part of its postal code, which is retrieved from geo-location database. If FSA is empty, dash (â-â) is filled in. -* {allowed/disallowed}: This flag shows if a request is allowed or disallowed by RGB (1 for yes, and 0 for no). -* {include/exclude postal}: It shows that when a rule in JSON is matched for a request, it is an include or exclude list of postal codes (i.e. FSAs). âIâ for include, and âXâ for exclude. If no rule matches, dash (â-â) is filled in. -* {fallback config/current config}: when TR fails to parse an RGB JSON, TR will handle requests with latest valid JSON configuration, but will set {fallback config} flag to 1. If the new JSON is valid, then the flag is set to 0. -* {allowed by whitelist/otherwise}: If a request is allowed by whitelist, this flag is set to 1; for all other cases, it is 0. - - -Example:: - - 1446442214.685 qtype=HTTP chi=129.100.254.79 url="http://ccr.geo2.cdn.com/live5.m3u8"; cqhm=GET cqhv=HTTP/1.1 rtype=GEO rloc="-" rdtl=- rerr="-" rgb="N6G:1:X:0:0" pssc=302 ttms=3 rurl=http://cent6-44.geo2.cdn.com/live5.m3u8 rh="-" - - 1446442219.181 qtype=HTTP chi=184.68.71.9 url="http://ccr.geo2.cdn.com/live5.m3u8"; cqhm=GET cqhv=HTTP/1.1 rtype=RGALT rloc="-" rdtl=- rerr="-" rgb="-:0:X:0:0" pssc=302 ttms=3 rurl=http://cent6-44.geo2.cdn.com/low_bitrate.m3u8 rh="-" - - 1446445521.677 qtype=HTTP chi=24.114.29.79 url="http://ccr.geo2.cdn.com/live51.m3u8"; cqhm=GET cqhv=HTTP/1.1 rtype=RGDENY rloc="-" rdtl=- rerr="-" rgb="L4S:0:-:0:0" pssc=520 ttms=3 rurl="-" rh="-" - - http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/quick_howto/steering.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/quick_howto/steering.rst.txt b/docs/latest/_sources/admin/quick_howto/steering.rst.txt deleted file mode 100644 index 1060f29..0000000 --- a/docs/latest/_sources/admin/quick_howto/steering.rst.txt +++ /dev/null @@ -1,95 +0,0 @@ -.. -.. -.. 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. -.. - -.. _rl-steering-qht: - -*********************************** -Configure Delivery Service Steering -*********************************** - -1) Create two target delivery services in Traffic Ops. They must both be HTTP delivery services that are part of the same CDN. - -.. image:: steering01.png - :scale: 100% - :align: center - -2) Create a delivery service with type STEERING in Traffic Ops. - -.. image:: steering02.png - :scale: 100% - :align: center - -3) Click the 'Manage Steering Assignments' button on the delivery service screen to assign targets. - -.. image:: steering03.png - :scale: 100% - :align: center - -4) Create a user with the role of Steering. - -.. image:: steering04.png - :scale: 100% - :align: center - -5) As the steering user, assign weights to target delivery services. This will require logging in to Traffic Ops first via ``http://to.kabletown.net/api/1.2/user/login`` and storing the mojolicious cookie. - - Sample cURL: ``curl -H "Cookie: mojolicious=xxxyyy" -XPUT "https://to.kabletown.net/internal/api/1.2/steering/steering-ds"; -d @/tmp/steering.json`` - - Sample JSON body: - -:: - - { - "targets": [ - { - "weight": "1000", - "deliveryService": "target-deliveryservice-1" - }, - { - "weight": "9000", - "deliveryService": "target-deliveryservice-2" - } - ] - } - -6) If desired, the steering user can create filters for the target delivery services. - - Sample cURL: ``curl -H "Cookie: mojolicious=xxxyyy" -XPUT "https://to.kabletown.net/internal/api/1.2/steering/steering-ds"; -d @/tmp/steering.json`` - - Sample JSON body: - -:: - - { - "filters": [ - { - "pattern": ".*\\gototarget1\\..*", - "deliveryService": "target-deliveryservice-1" - } - ], - "targets": [ - { - "weight": "1000", - "deliveryService": "target-deliveryservice-1" - }, - { - "weight": "9000", - "deliveryService": "target-deliveryservice-2" - } - ] - } - -7) Any requests to Traffic Router for the steering delivery service should now be routed to target delivery services based on configured weight. Example: ``curl -Lvs http://tr.steering-ds.cdn.kabletown.net/foo`` - http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/traffic_monitor.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/traffic_monitor.rst.txt b/docs/latest/_sources/admin/traffic_monitor.rst.txt deleted file mode 100644 index 3a06e78..0000000 --- a/docs/latest/_sources/admin/traffic_monitor.rst.txt +++ /dev/null @@ -1,142 +0,0 @@ -.. -.. -.. 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 Monitor Administration -****************************** -Installing Traffic Monitor -========================== -The following are requirements to ensure an accurate set up: - -* CentOS 6 -* 4 vCPUs -* 8GB RAM -* Successful install of Traffic Ops -* Tomcat -* Administrative access to the Traffic Ops -* Physical address of the site -* perl-JSON -* perl-WWW-Curl - -1. Enter the Traffic Monitor server into Traffic Ops -2. Make sure the FQDN of the Traffic Monitor is resolvable in DNS. -3. Install Traffic Monitor and Perl mods: ``sudo yum -y install traffic_monitor perl-JSON perl-WWW-Curl`` -4. Take the config from Traffic Ops - run : ``sudo /opt/traffic_monitor/bin/traffic_monitor_config.pl`` - - Sample output: :: - - traffic_mon # /opt/traffic_monitor/bin/traffic_monitor_config.pl https://traffic-ops.cdn.kabletown.net admin:password prompt - DEBUG: traffic_ops selected: https://traffic-ops.cdn.kabletown.net - DEBUG: traffic_ops login: admin:kl0tevax - DEBUG: Config write mode: prompt - DEBUG: Found profile from traffic_ops: RASCAL_CDN - DEBUG: Found CDN name from traffic_ops: kabletown_cdn - DEBUG: Found location for rascal-config.txt from traffic_ops: /opt/traffic_monitor/conf - WARN: Param not in traffic_ops: allow.config.edit description: Allow the running configuration to be edited through the UI Using default value of: false - WARN: Param not in traffic_ops: default.accessControlAllowOrigin description: The value for the header: Access-Control-Allow-Origin for published jsons... should be narrowed down to TMs Using default value of: * - WARN: Param not in traffic_ops: default.connection.timeout description: Default connection time for all queries (cache, peers, TM) Using default value of: 2000 - WARN: Param not in traffic_ops: hack.forceSystemExit description: Call System.exit on shutdown Using default value of: false - WARN: Param not in traffic_ops: hack.peerOptimistic description: The assumption of a caches availability when unknown by peers Using default value of: true - WARN: Param not in traffic_ops: hack.publishDsStates description: If true, the delivery service states will be included in the CrStates.json Using default value of: true - WARN: Param not in traffic_ops: health.ds.interval description: The polling frequency for calculating the deliveryService states Using default value of: 1000 - WARN: Param not in traffic_ops: health.ds.leniency description: The amount of time before the deliveryService disregards the last update from a non-responsive cache Using default value of: 30000 - WARN: Param not in traffic_ops: health.event-count description: The number of historical events that will be kept Using default value of: 200 - WARN: Param not in traffic_ops: health.polling.interval description: The polling frequency for getting the states from caches Using default value of: 5000 - WARN: Param not in traffic_ops: health.startupMinCycles description: The number of query cycles that must be completed before this Traffic Monitor will start reporting Using default value of: 2 - WARN: Param not in traffic_ops: health.timepad description: A delay between each separate cache query Using default value of: 10 - WARN: Param not in traffic_ops: peers.polling.interval description: Polling frequency for getting states from peer monitors Using default value of: 5000 - WARN: Param not in traffic_ops: peers.polling.url description: The url for current, unfiltered states from peer monitors Using default value of: http://${hostname}/publish/CrStates?raw - WARN: Param not in traffic_ops: peers.threadPool description: The number of threads given to the pool for querying peers Using default value of: 1 - WARN: Param not in traffic_ops: tm.auth.url description: The url for the authentication form Using default value of: https://${tmHostname}/login - WARN: Param not in traffic_ops: tm.crConfig.json.polling.url description: Url for the cr-config (json) Using default value of: https://${tmHostname}/CRConfig-Snapshots/${cdnName}/CRConfig.json - WARN: Param not in traffic_ops: tm.healthParams.polling.url description: The url for the heath params (json) Using default value of: https://${tmHostname}/health/${cdnName} - WARN: Param not in traffic_ops: tm.polling.interval description: The polling frequency for getting updates from TM Using default value of: 10000 - DEBUG: allow.config.edit needed in config, but does not exist in config on disk. - DEBUG: cdnName value on disk () does not match value needed in config (kabletown_cdn). - DEBUG: default.accessControlAllowOrigin needed in config, but does not exist in config on disk. - DEBUG: default.connection.timeout needed in config, but does not exist in config on disk. - DEBUG: hack.forceSystemExit needed in config, but does not exist in config on disk. - DEBUG: hack.peerOptimistic needed in config, but does not exist in config on disk. - DEBUG: hack.publishDsStates needed in config, but does not exist in config on disk. - DEBUG: health.ds.interval needed in config, but does not exist in config on disk. - DEBUG: health.ds.leniency needed in config, but does not exist in config on disk. - DEBUG: health.startupMinCycles needed in config, but does not exist in config on disk. - DEBUG: health.timepad value on disk (20) does not match value needed in config (10). - DEBUG: peers.polling.interval needed in config, but does not exist in config on disk. - DEBUG: peers.threadPool needed in config, but does not exist in config on disk. - DEBUG: tm.auth.password value on disk () does not match value needed in config (kl0tevax). - DEBUG: tm.auth.username value on disk () does not match value needed in config (admin). - DEBUG: tm.hostname value on disk () does not match value needed in config (traffic-ops.cdn.kabletown.net). - DEBUG: Proposed traffic_monitor_config: - { - "traffic_monitor_config":{ - "default.accessControlAllowOrigin":"*", - "health.startupMinCycles":"2", - "tm.auth.password":"kl0tevax", - "tm.auth.url":"https://${tmHostname}/login";, - "tm.healthParams.polling.url":"https://${tmHostname}/health/${cdnName}";, - "allow.config.edit":"false", - "tm.crConfig.json.polling.url":"https://${tmHostname}/CRConfig-Snapshots/${cdnName}/CRConfig.json";, - "tm.auth.username":"admin", - "peers.polling.url":"http://${hostname}/publish/CrStates?raw";, - "health.timepad":"10", - "hack.publishDsStates":"true", - "default.connection.timeout":"2000", - "health.ds.interval":"1000", - "peers.polling.interval":"5000", - "hack.forceSystemExit":"false", - "health.ds.leniency":"30000", - "cdnName":"kabletown_cdn", - "peers.threadPool":"1", - "tm.polling.interval":"10000", - "health.polling.interval":"5000", - "health.event-count":"200", - "hack.peerOptimistic":"true", - "tm.hostname":"traffic-ops.cdn.kabletown.net" - } - } - ---------------------------------------------- - ----OK to write this config to disk? (Y/n) [n]y - ---------------------------------------------- - ---------------------------------------------- - ----OK to write this config to disk? (Y/n) [n]Y - ---------------------------------------------- - DEBUG: Writing /opt/traffic_monitor/conf/traffic_monitor_config.js - traffic_mon # - -5. Start Tomcat: ``sudo service tomcat start`` :: - - - Using CATALINA_BASE: /opt/tomcat - Using CATALINA_HOME: /opt/tomcat - Using CATALINA_TMPDIR: /opt/tomcat/temp - Using JRE_HOME: /usr - Using CLASSPATH:/opt/tomcat/bin/bootstrap.jar - Using CATALINA_PID:/var/run/tomcat/tomcat.pid - Starting tomcat [ OK ] - -6. Verify Traffic Monitor is running by pointing your browser to port 80 on the Traffic Monitor host. - -Configuring Traffic Monitor -=========================== - -Configuration Overview ----------------------- -Traffic Monitor is configured using its JSON configuration file, ``traffic_monitor_config.js``. Specify the URL, username, password, and CDN name for the instance of Traffic Ops for which this Traffic Monitor is a member, and start the software. Once started with the correct configuration, Traffic Monitor downloads its configuration from Traffic Ops and begins polling caches. Once a configurable number of polling cycles completes, health protocol state is available via RESTful JSON endpoints. - - -Troubleshooting and log files -============================= -Traffic Monitor log files are in ``/opt/traffic_monitor/var/log/``, and tomcat log files are in ``/opt/tomcat/logs/``. http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/traffic_ops_config.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/traffic_ops_config.rst.txt b/docs/latest/_sources/admin/traffic_ops_config.rst.txt deleted file mode 100644 index 0ca57da..0000000 --- a/docs/latest/_sources/admin/traffic_ops_config.rst.txt +++ /dev/null @@ -1,186 +0,0 @@ -.. -.. -.. 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. -.. - -Configuring Traffic Ops -%%%%%%%%%%%%%%%%%%%%%%% - -Follow the steps below to configure the newly installed Traffic Ops Instance. - -Installing the SSL Cert -======================= -By default, Traffic Ops runs as an SSL web server, and a certificate needs to be installed. TBD. - -Content Delivery Networks -========================= - -.. _rl-param-prof: - -Profile Parameters -====================== -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: - - -.. index:: - Global Profile - -+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| Name | Config file | Value | -+==========================+===============+=======================================================================================================================================+ -| tm.url | global | The URL where this Traffic Ops instance is being served from. | -+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| tm.toolname | global | The name of the Traffic Ops tool. Usually "Traffic Ops". Used in the About screen and in the comments headers of the files generated. | -+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| tm.infourl | global | This is the "for more information go here" URL, which is visible in the About page. | -+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| tm.logourl | global | This is the URL of the logo for Traffic Ops and can be relative if the logo is under traffic_ops/app/public. | -+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| tm.instance_name | global | The name of the Traffic Ops instance. Can be used when multiple instances are active. Visible in the About page. | -+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| tm.traffic_mon_fwd_proxy | global | 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. | -+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| geolocation.polling.url | CRConfig.json | The location to get the GeoLiteCity database from. | -+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| geolocation6.polling.url | CRConfig.json | The location to get the IPv6 GeoLiteCity database from. | -+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ - -These parameters should be set to reflect the local environment. - - -After running the postinstall script, Traffic Ops has the following profiles pre-loaded: - -+----------+-------------------------------------------------------------------------------------------------+ -| Name | Description | -+==========+=================================================================================================+ -| EDGE1 | The profile to be applied to the latest supported version of ATS, when running as an EDGE cache | -+----------+-------------------------------------------------------------------------------------------------+ -| TR1 | The profile to be applied to the latest version of Traffic Router | -+----------+-------------------------------------------------------------------------------------------------+ -| TM1 | The profile to be applied to the latest version of Traffic Monitor | -+----------+-------------------------------------------------------------------------------------------------+ -| MID1 | The profile to be applied to the latest supported version of ATS, when running as an MID cache | -+----------+-------------------------------------------------------------------------------------------------+ -| RIAK_ALL | Riak profile for all CDNs to be applied to the Traffic Vault servers | -+----------+-------------------------------------------------------------------------------------------------+ - -.. Note:: The Traffic Server profiles contain some information that is specific to the hardware being used (most notably the disk configuration), so some parameters will have to be changed to reflect your configuration. Future releases of Traffic Control will separate the hardware and software profiles so it is easier to "mix-and-match" different hardware configurations. - -Below is a list of cache parameters that are likely to need changes from the default profiles shipped with Traffic Ops: - -+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+ -| Name | Config file | Description | -+==========================+===================+=========================================================================================================================+ -| allow_ip | astats.config | This is a comma separated list of IPv4 CIDR blocks that will have access to the astats statistics on the caches. | -| | | The Traffic Monitor IP addresses have to be included in this, if they are using IPv4 to monitor the caches. | -+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+ -| allow_ip6 | astats.config | This is a comma separated list of IPv6 CIDR blocks that will have access to the astats statistics on the caches. | -| | | The Traffic Monitor IP addresses have to be included in this, if they are using IPv6 to monitor the caches. | -+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+ -| Drive_Prefix | storage.config | JvD/Jeff to supply blurb | -+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+ -| Drive_Letters | storage.config | JvD/Jeff to supply blurb | -+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+ -| purge_allow_ip | ip_allow.config | The IP address range that is allowed to execute the PURGE method on the caches (not related to :ref:`rl-purge`) | -+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+ -| health.threshold.loadavg | rascal.properties | The Unix load average at which Traffic Router will stop sending traffic to this cache | -+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+ -| health.threshold.\\ | rascal.properties | The amount of bandwidth that Traffic Router will try to keep available on the cache. | -| availableBandwidthInKbps | | For example: "">1500000" means stop sending new traffic to this cache when traffic is at 8.5Gbps on a 10Gbps interface. | -+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+ - -Below is a list of Traffic Server plugins that need to be configured in the parameter table: - -+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+ -| Name | Config file | Description | Details | -+==================+===============+======================================================+============================================================================================================+ -| astats_over_http | package | The package version for the astats_over_http plugin. | `astats_over_http <http://trafficcontrol.apache.org/downloads/index.html>`_ | -+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+ -| trafficserver | package | The package version for the trafficserver plugin. | `trafficserver <http://trafficcontrol.apache.org/downloads/index.html>`_ | -+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+ -| regex_revalidate | plugin.config | The config to be used for regex_revalidate. | `regex_revalidate <https://docs.trafficserver.apache.org/en/5.3.x/reference/plugins/regex_remap.en.html>`_ | -| | | For example: --config regex_revalidate.config | | -+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+ -| remap_stats | plugin.config | The config to be used for remap_stats. | `remap_stats <https://github.com/apache/trafficserver/tree/master/plugins/experimental/remap_stats>`_ | -| | | Value is left blank. | | -+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+ - - -Regions, Locations and Cache Groups -=================================== -All servers have to have a `location`, which is their physical location. Each location is part of a `region`, and each region is part of a `division`. For Example, ``Denver`` could be a location in the ``Mile High`` region and that region could be part of the ``West`` division. Enter your divisions first in `Misc->Divisions`, then enter the regions in `Misc->Regions`, referencing the divisions entered, and finally, enter the physical locations in `Misc->Locations`, referencing the regions entered. - -All servers also have to be part of a `cache group`. A cache group is a logical grouping of caches, that don't have to be in the same physical location (in fact, usually a cache group is spread across minimally 2 physical Locations for redundancy purposes), but share geo coordinates for content routing purposes. JvD to add more. - - - -Configuring Content Purge -========================= -Content purge using ATS is not simple; there is no file system to delete files/directories from, and in large caches it can be hard to delete a simple regular expression from the cache. This is why Traffic Control uses the `Regex Revalidate Plugin <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_revalidate.en.html>`_ to purge content from the system. We don't actually remove the content, we have a check that gets run before each request on each cache to see if this request matches a list of regular expressions, and if it does, we force a revalidation to the origin, making the original content inaccessible. The regex_revalidate plugin will monitor it's config file, and will pick up changes to it without a `traffic_line -x` signal to ATS. Changes to this file need to be distributed to the highest tier (MID) caches in the CDN before they are distributed to the lower tiers, to prevent filling the lower tiers with the content that should be purged from the highe r tiers without hitting the origin. This is why the ort script (see :ref:`reference-traffic-ops-ort`) will by default push out config changes to MID first, confirm that they have all been updated, and then push out the changes to the lower tiers. In large CDNs, this can make the distribution and time to activation of the purge too long, and because of that there is the option to not distribute the `regex_revalidate.config` file using the ort script, but to do this using other means. By default, Traffic Ops will use ort to distribute the `regex_revalidate.config` file. - -Content Purge is controlled by the following parameters in the profile of the cache: - -+----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+ -| Name | Config file | Description | Details | -+======================+=========================+==================================================+=========================================================================================================================================================+ -| location | regex_revalidate.config | What location the file should be in on the cache | The presence of this parameter tells ort to distribute this file; delete this parameter from the profile if this file is distributed using other means. | -+----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+ -| maxRevalDurationDays | regex_revalidate.config | The maximum time a purge can be active | To prevent a build up of many checks before each request, this is longest time the system will allow | -+----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+ -| regex_revalidate | plugin.config | The config to be used for regex_revalidate. | `regex_revalidate <https://docs.trafficserver.apache.org/en/5.3.x/reference/plugins/regex_remap.en.html>`_ | -| | | For example: --config regex_revalidate.config | | -+----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+ - -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 `proxy-config-http-cache-guaranteed-min-lifetime <https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-config-http-cache-guaranteed-min-lifetime>`_ 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 `maxRevalDurationDays` (Note that the former is in seconds and the latter is in days, so convert appropriately). - - - -.. _Creating-CentOS-Kickstart: - -Creating the CentOS Kickstart File -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The kickstart file is a text file, containing a list of items, each identified by a keyword. You can create it by using the Kickstart Configurator application, or writing it from scratch. The Red Hat Enterprise Linux installation program also creates a sample kickstart file based on the options that you selected during installation. It is written to the file ``/root/anaconda-ks.cfg``. This file is editable using most text editors that can save files as ASCII text. - -To generate ISO, the CentOS Kickstart is necessary: - -1. Create a kickstart file. -2. Create a boot media with the kickstart file or make the kickstart file available on the network. -3. Make the installation tree available. -4. Start the kickstart installation. - -Create a ks.src file in the root of the selection location. See the example below: - -:: - - - mkdir newdir - cd newdir/ - cp -r ../centos65/* . - vim ks.src - vim isolinux/isolinux.cfg - cd vim osversions.cfg - vim osversions.cfg - - -This is a standard kickstart formatted file that the generate ISO process uses to create the kickstart (ks.cfg) file for the install. The generate ISO process uses the ks.src, overwriting any information set in the Generate ISO tab in Traffic Ops, creating ks.cfg. - -.. Note:: Streamline your install folder for under 1GB, which assists in creating a CD. - -.. seealso:: For in-depth instructions, please see `Kickstart Installation <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-howuse.html>`_ - - - - http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/9694fb23/docs/latest/_sources/admin/traffic_ops_extensions.rst.txt ---------------------------------------------------------------------- diff --git a/docs/latest/_sources/admin/traffic_ops_extensions.rst.txt b/docs/latest/_sources/admin/traffic_ops_extensions.rst.txt deleted file mode 100644 index 4aceebb..0000000 --- a/docs/latest/_sources/admin/traffic_ops_extensions.rst.txt +++ /dev/null @@ -1,88 +0,0 @@ -.. -.. -.. 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. -.. - -.. _admin-to-ext-script: - -Managing Traffic Ops Extensions -******************************* - -Each script is a separate bash script located in ``$TO_HOME/bin/checks/``. - -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 ``/opt/traffic_ops/app/bin/extensions -a``. - -The below extensions are automatically registered with the Traffic Ops database (``to_extension`` table) at install time (see ``traffic_ops/app/db/seeds.sql``). However, cron must still be configured to run these checks periodically. - -The scripts are called as follows: :: - - - $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 - <traffic_ops_ip> is the IP address of the Traffic Ops Server - <check_name> is the name of the check. For example: CDU, CHR, DSCP, MTU, etc... - <log_level> is between 1 and 4, with 4 being the most verbose. This field is optional - - -Example Cron File -================= -Edit with ``crontab -e``. You may need to adjust the path to your $TO_HOME to match your system. - -:: - - - PERL5LIB=/opt/traffic_ops/app/local/lib/perl5:/opt/traffic_ops/app/lib - - # IPv4 ping examples - The 'select: ["hostName","domainName"]' works but, if you want to check DNS resolution use FQDN. - */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"10G\", \"select\": [\"hostName\",\"domainName\"]}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"10G\", \"select\": \"ipAddress\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"10G\", \"name\": \"IPv4 Ping\", \"select\": \"ipAddress\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1 - - # IPv6 ping examples - */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"10G6\", \"name\": \"IPv6 Ping\", \"select\": \"ip6Address\", \"syslog_facility\": \"local0\"}" >/dev/null 2>&1 - */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"10G6\", \"select\": \"ip6Address\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - - # iLO ping - 18 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"ILO\", \"select\": \"iloIpAddress\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - 18 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"ILO\", \"name\": \"ILO ping\", \"select\": \"iloIpAddress\", \"syslog_facility\": \"local0\"}" >/dev/null 2>&1 - - # MTU ping - 45 0 * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"MTU\", \"select\": \"ipAddress\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - 45 0 * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"MTU\", \"select\": \"ip6Address\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - 45 0 * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"MTU\", \"name\": \"Max Trans Unit\", \"select\": \"ipAddress\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1 - 45 0 * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"MTU\", \"name\": \"Max Trans Unit\", \"select\": \"ip6Address\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1 - - # FQDN - 27 * * * * root /opt/traffic_ops/app/bin/checks/ToFQDNCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"FQDN\"" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - 27 * * * * root /opt/traffic_ops/app/bin/checks/ToFQDNCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"FQDN\", \"name\": \"DNS Lookup\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1 - - # DSCP - 36 * * * * root /opt/traffic_ops/app/bin/checks/ToDSCPCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"DSCP\", \"cms_interface\": \"eth0\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - 36 * * * * root /opt/traffic_ops/app/bin/checks/ToDSCPCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"DSCP\", \"name\": \"Delivery Service\", \"cms_interface\": \"eth0\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1 - - # RTR - 10 * * * * root /opt/traffic_ops/app/bin/checks/ToRTRCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"RTR\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - 10 * * * * root /opt/traffic_ops/app/bin/checks/ToRTRCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"RTR\", \"name\": \"Content Router Check\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1 - - # CHR - */15 * * * * root /opt/traffic_ops/app/bin/checks/ToCHRCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"CHR\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - - # CDU - 20 * * * * root /opt/traffic_ops/app/bin/checks/ToCDUCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"CDU\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - - # ORT - 40 * * * * ssh_key_edge_user /opt/traffic_ops/app/bin/checks/ToORTCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"ORT\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1 - 40 * * * * ssh_key_edge_user /opt/traffic_ops/app/bin/checks/ToORTCheck.pl -c "{\"base_url\": \"https://localhost\";, \"check_name\": \"ORT\", \"name\": \"Operational Readiness Test\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1 -
