You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficcontrol.apache.org by fr...@apache.org on 2017/06/14 19:36:32 UTC

[1/9] incubator-trafficcontrol git commit: updated the documentation for migrating from 1.0 to 2.0 for Traffic Ops

Repository: incubator-trafficcontrol
Updated Branches:
  refs/heads/2.0.x dde8674ac -> b8cdd626d


http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/80ab6944/docs/source/admin/traffic_ops_using.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops_using.rst b/docs/source/admin/traffic_ops_using.rst
deleted file mode 100644
index 2bb1749..0000000
--- a/docs/source/admin/traffic_ops_using.rst
+++ /dev/null
@@ -1,1079 +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.
-..
-
-.. |graph| image:: ../../../traffic_ops/app/public/images/graph.png
-.. |info| image:: ../../../traffic_ops/app/public/images/info.png
-.. |checkmark| image:: ../../../traffic_ops/app/public/images/good.png
-.. |X| image:: ../../../traffic_ops/app/public/images/bad.png
-.. |clock| image:: ../../../traffic_ops/app/public/images/clock-black.png
-
-Using Traffic Ops
-%%%%%%%%%%%%%%%%%
-
-
-The Traffic Ops Menu
-====================
-
-.. image:: 12m.png
-
-The following tabs are available in the menu at the top of the Traffic Ops user interface.
-
-.. index::
-  Health Tab
-
-* **Health**
-
-  Information on the health of the system. Hover over this tab to get to the following options:
-
-  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
-  |     Option    |                                                            Description                                                             |
-  +===============+====================================================================================================================================+
-  | Table View    | A real time view into the main performance indicators of the CDNs managed by Traffic Control.                                      |
-  |               | This view is sourced directly by the Traffic Monitor data and is updated every 10 seconds.                                         |
-  |               | This is the default screen of Traffic Ops.                                                                                         |
-  |               | See :ref:`rl-health-table` for details.                                                                                            |
-  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
-  | Graph View    | A real graphical time view into the main performance indicators of the CDNs managed by Traffic Control.                            |
-  |               | This view is sourced by the Traffic Monitor data and is updated every 10 seconds.                                                  |
-  |               | On loading, this screen will show a history of 24 hours of data from Traffic Stats                                                 |
-  |               | See :ref:`rl-health-graph` for details.                                                                                            |
-  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
-  | Server Checks | A table showing the results of the periodic check extension scripts that are run. See :ref:`rl-server-checks`                      |
-  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
-  | Daily Summary | A graph displaying the daily peaks of bandwidth, overall bytes served per day, and overall bytes served since initial installation |
-  |               | per CDN.                                                                                                                           |
-  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
-
-* **Delivery Services**
-
-  The main Delivery Service table. This is where you Create/Read/Update/Delete Delivery Services of all types. Hover over to get the following sub option:
-
-  +-------------+--------------------------------------+
-  |    Option   |             Description              |
-  +=============+======================================+
-  | Federations | Add/Edit/Delete Federation Mappings. |
-  +-------------+--------------------------------------+
-
-* **Servers**
-
-  The main Servers table. This is where you Create/Read/Update/Delete servers of all types.  Click the main tab to get to the main table, and hover over to get these sub options:
-
-  +-------------------+------------------------------------------------------------------------------------------+
-  |       Option      |                                       Description                                        |
-  +===================+==========================================================================================+
-  | Upload Server CSV | Bulk add of servers from a csv file. See :ref:`rl-bulkserver`                            |
-  +-------------------+------------------------------------------------------------------------------------------+
-
-* **Parameters**
-
-  Parameters and Profiles can be edited here. Hover over the tab to get the following options:
-
-  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-  |        Option       |                                                                             Description                                                                             |
-  +=====================+=====================================================================================================================================================================+
-  | Global Profile      | The table of global parameters. See :ref:`rl-param-prof`. This is where you Create/Read/Update/Delete parameters in the Global profile                              |
-  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-  | All Cache Groups    | The table of all parameters *that are assgined to a cachegroup* - this may be slow to pull up, as there can be thousands of parameters.                             |
-  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-  | All Profiles        | The table of all parameters *that are assgined to a profile* - this may be slow to pull up, as there can be thousands of parameters.                                |
-  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-  | Select Profile      | Select the parameter list by profile first, then get a table of just the parameters for that profile.                                                               |
-  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-  | Orphaned Parameters | A table of parameters that are not associated to any profile of cache group. These parameters either should be deleted or associated with a profile of cache group. |
-  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-* **Tools**
-
-  Tools for working with Traffic Ops and it's servers. Hover over this tab to get the following options:
-
-  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
-  |       Option       |                                                            Description                                                            |
-  +====================+===================================================================================================================================+
-  | Generate ISO       | Generate a bootable image for any of the servers in the Servers table (or any server for that matter). See :ref:`rl-generate-iso` |
-  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
-  | Queue Updates      | Send Updates to the caches. See :ref:`rl-queue-updates`                                                                           |
-  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
-  | DB Dump            | Backup the Database to a .sql file.                                                                                               |
-  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
-  | Snapshot CRConfig  | Send updates to the Traffic Monitor / Traffic Router servers.  See :ref:`rl-queue-updates`                                        |
-  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
-  | Invalidate Content | Invalidate or purge content from all caches in the CDN. See :ref:`rl-purge`                                                       |
-  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
-  | Manage DNSSEC keys | Manage DNSSEC Keys for a chosen CDN.                                                                                              |
-  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
-
-
-* **Misc**
-
-  Miscellaneous editing options. Hover over this tab to get the following options:
-
-  +--------------------+-------------------------------------------------------------------------------------------+
-  |       Option       |                                        Description                                        |
-  +====================+===========================================================================================+
-  | Cache Groups       | Create/Read/Update/Delete cache groups                                                    |
-  +--------------------+-------------------------------------------------------------------------------------------+
-  | Users              | Create/Read/Update/Delete users                                                           |
-  +--------------------+-------------------------------------------------------------------------------------------+
-  | Profiles           | Create/Read/Update/Delete profiles. See :ref:`rl-working-with-profiles`                   |
-  +--------------------+-------------------------------------------------------------------------------------------+
-  | Networks(ASNs)     | Create/Read/Update/Delete Autonomous System Numbers See :ref:`rl-asn-czf`                 |
-  +--------------------+-------------------------------------------------------------------------------------------+
-  | Hardware           | Get detailed hardware information (note: this should be moved to a Traffic Ops Extension) |
-  +--------------------+-------------------------------------------------------------------------------------------+
-  | Data Types         | Create/Read/Update/Delete data types                                                      |
-  +--------------------+-------------------------------------------------------------------------------------------+
-  | Divisions          | Create/Read/Update/Delete divisions                                                       |
-  +--------------------+-------------------------------------------------------------------------------------------+
-  | Regions            | Create/Read/Update/Delete regions                                                         |
-  +--------------------+-------------------------------------------------------------------------------------------+
-  | Physical Locations | Create/Read/Update/Delete locations                                                       |
-  +--------------------+-------------------------------------------------------------------------------------------+
-
-.. index::
-  Change Log
-
-* **ChangeLog**
-
-  The Changelog table displays the changes that are being made to the Traffic Ops database through the Traffic Ops user interface. This tab will show the number of changes since you last visited this tab in (brackets) since the last time you visited this tab. There are currently no sub menus for this tab.
-
-
-* **Help**
-
-  Help for Traffic Ops and Traffic Control. Hover over this tab to get the following options:
-
-  +---------------+---------------------------------------------------------------------+
-  |     Option    |                             Description                             |
-  +===============+=====================================================================+
-  | About         | Traffic Ops information, such as version, database information, etc |
-  +---------------+---------------------------------------------------------------------+
-  | Release Notes | Release notes for the most recent releases of Traffic Ops           |
-  +---------------+---------------------------------------------------------------------+
-  | Logout        | Logout from Traffic Ops                                             |
-  +---------------+---------------------------------------------------------------------+
-
-
-.. index::
-  Edge Health
-  Health
-
-Health
-======
-
-.. _rl-health-table:
-
-The Health Table
-++++++++++++++++
-The Health table is the default landing screen for Traffic Ops, it displays the status of the EDGE caches in a table form directly from Traffic Monitor (bypassing Traffic Stats), sorted by Mbps Out. The columns in this table are:
-
-
-* **Profile**: the Profile of this server or ALL, meaning this row shows data for multiple servers, and the row shows the sum of all values.
-* **Host Name**: the host name of the server or ALL, meaning this row shows data for multiple servers, and the row shows the sum of all values.
-* **Edge Cache Group**: the edge cache group short name or ALL, meaning this row shows data for multiple servers, and the row shows the sum of all values.
-* **Healthy**: indicates if this cache is healthy according to the Health Protocol. A row with ALL in any of the columns will always show a |checkmark|, this column is valid only for individual EDGE caches.
-* **Admin**: shows the administrative status of the server.
-* **Connections**: the number of connections this cache (or group of caches) has open (``ats.proxy.process.http.current_client_connections`` from ATS).
-* **Mbps Out**: the bandwidth being served out if this cache (or group of caches)
-
-Since the top line has ALL, ALL, ALL, it shows the total connections and bandwidth for all caches managed by this instance of Traffic Ops.
-
-.. _rl-health-graph:
-
-Graph View
-++++++++++
-The Graph View shows a live view of the last 24 hours of bits per seconds served and open connections at the edge in a graph. This data is sourced from Traffic Stats. If there are 2 CDNs configured, this view will show the statistis for both, and the graphs are stacked. On the left-hand side, the totals and immediate values as well as the percentage of total possible capacity are displayed. This view is update every 10 seconds.
-
-
-.. _rl-server-checks:
-
-Server Checks
-+++++++++++++
-The server checks page is inteded to give an overview of the Servers managed by Traffic Control as well as their status. This data comes from `Traffic Ops extensions <traffic_ops_extensions.html>`_.
-
-+------+-----------------------------------------------------------------------+
-| Name |                 Description                                           |
-+======+=======================================================================+
-| ILO  | Ping the iLO interface for EDGE or MID servers                        |
-+------+-----------------------------------------------------------------------+
-| 10G  | Ping the IPv4 address of the EDGE or MID servers                      |
-+------+-----------------------------------------------------------------------+
-| 10G6 | Ping the IPv6 address of the EDGE or MID servers                      |
-+------+-----------------------------------------------------------------------+
-| MTU  | Ping the EDGE or MID using the configured MTU from Traffic Ops        |
-+------+-----------------------------------------------------------------------+
-| FQDN | DNS check that matches what the DNS servers responds with compared to |
-|      | what Traffic Ops has.                                                 |
-+------+-----------------------------------------------------------------------+
-| DSCP | Checks the DSCP value of packets from the edge server to the Traffic  |
-|      | Ops server.                                                           |
-+------+-----------------------------------------------------------------------+
-| RTR  | Content Router checks. Checks the health of the Content Routers.      |
-|      | Checks the health of the caches using the Content Routers.            |
-+------+-----------------------------------------------------------------------+
-| CHR  | Cache Hit Ratio in percent.                                           |
-+------+-----------------------------------------------------------------------+
-| CDU  | Total Cache Disk Usage in percent.                                    |
-+------+-----------------------------------------------------------------------+
-| ORT  | Operational Readiness Test. Uses the ORT script on the edge and mid   |
-|      | servers to determine if the configuration in Traffic Ops matches the  |
-|      | configuration on the edge or mid. The user that this script runs as   |
-|      | must have an ssh key on the edge servers.                             |
-+------+-----------------------------------------------------------------------+
-
-Daily Summary
-+++++++++++++
-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 `Traffic Stats <traffic_stats.html>`_  section.
-
-.. _rl-server:
-
-Server
-======
-This view shows a table of all the servers in Traffic Ops. The table columns show the most important details of the server. The **IPAddrr** column is clickable to launch an ``ssh://`` link to this server. The |graph| icon will link to a Traffic Stats graph of this server for caches, and the |info| will link to the server status pages for other server types.
-
-
-Server Types
-++++++++++++
-These are the types of servers that can be managed in Traffic Ops:
-
-+---------------+---------------------------------------------+
-|      Name     |                 Description                 |
-+===============+=============================================+
-| EDGE          | Edge Cache                                  |
-+---------------+---------------------------------------------+
-| MID           | Mid Tier Cache                              |
-+---------------+---------------------------------------------+
-| ORG           | Origin                                      |
-+---------------+---------------------------------------------+
-| CCR           | Comcast Content Router                      |
-+---------------+---------------------------------------------+
-| RASCAL        | Rascal health polling & reporting           |
-+---------------+---------------------------------------------+
-| TOOLS_SERVER  | Ops hosts for managment                     |
-+---------------+---------------------------------------------+
-| RIAK          | Riak keystore                               |
-+---------------+---------------------------------------------+
-| SPLUNK        | SPLUNK indexer search head etc              |
-+---------------+---------------------------------------------+
-| TRAFFIC_STATS | traffic_stats server                        |
-+---------------+---------------------------------------------+
-| INFLUXDB      | influxDb server                             |
-+---------------+---------------------------------------------+
-
-
-.. index::
-  Bulk Upload Server
-
-.. _rl-bulkserver:
-
-Bulk Upload Server
-++++++++++++++++++
-
-
-
-Delivery Service
-================
-The fields in the Delivery Service view are:
-
-.. Sorry for the width of this table, don't know how to make the bullet lists work otherwise. Just set your monitor to 2560*1600, and put on your glasses.
-
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|                       Name                       |                                                                                                     Description                                                                                                     |
-+==================================================+=====================================================================================================================================================================================================================+
-| XML ID                                           | A unique string that identifies this delivery service.                                                                                                                                                              |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Content Routing Type                             | The type of content routing this delivery service will use. See :ref:`rl-ds-types`.                                                                                                                                 |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Protocol                                         | The protocol to serve this delivery service to the clients with:                                                                                                                                                    |
-|                                                  |                                                                                                                                                                                                                     |
-|                                                  | -  0 http                                                                                                                                                                                                           |
-|                                                  | -  1 https                                                                                                                                                                                                          |
-|                                                  | -  2 both http and https                                                                                                                                                                                            |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| DSCP Tag                                         | The DSCP value to mark IP packets to the client with.                                                                                                                                                               |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Signed URLs                                      | Use Signed URLs? See :ref:`rl-signed-urls`.                                                                                                                                                                         |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Query String Handling                            | How to treat query strings:                                                                                                                                                                                         |
-|                                                  |                                                                                                                                                                                                                     |
-|                                                  | - 0 use in cache key and hand up to origin -this means each unique query string Is treated as a unique URL.                                                                                                         |
-|                                                  | - 1 Do not use in cache key, but pass up to origin - this means a 2 URLs that are the same except for the query string will match, and cache HIT, while the origin still sees original query string in the request. |
-|                                                  | - 2 Drop at edge - this means a 2 URLs that are the same except for  the query string will match, and cache HIT, while the origin will not see original query string in the request.                                |
-|                                                  |                                                                                                                                                                                                                     |
-|                                                  | **Note:** Choosing to drop query strings at the edge will preclude the use of a Regex Remap Expression. See :ref:`rl-regex-remap`.                                                                                  |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Geo Limit?                                       | Some services are intended to be limited by geography. The possible settings are are:                                                                                                                               |
-|                                                  |                                                                                                                                                                                                                     |
-|                                                  | - None - Do not limit by geography.                                                                                                                                                                                 |
-|                                                  | - CZF only - If the requesting IP is not in the Coverage Zone File, do not serve the request.                                                                                                                       |
-|                                                  | - CZF + US - If the requesting IP is not in the Coverage Zone File or not in the United States, do not serve the request.                                                                                           |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Geo Limit Redirect URL                           | (for HTTP routed delivery services only) This is the URL Traffic Router will redirect to when Geo Limit Failure. See :ref:`rl-tr-ngb`                                                                               |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Bypass FQDN                                      | (for HTTP routed delivery services only) This is the FQDN Traffic Router will redirect to (with the same path) when the max Bps or Max Tps for this deliveryservice are exceeded.                                   |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Bypass Ipv4                                      | (For DNS routed delivery services only) This is the address to respond to A requests with when the the max Bps or Max Tps for this delivery service are exceeded.                                                   |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Bypass IPv6                                      | (For DNS routed delivery services only) This is the address to respond to AAAA requests with when the the max Bps or Max Tps for this delivery service are exceeded.                                                |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| IPv6 Routing Enabled?                            | When set to yes, the Traffic Router will respond to AAAA DNS requests for the tr. and edge. names of this delivery service. Otherwise, only A records will be served.                                               |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Range Request Handling                           | (experimental)  How to treat range requests:                                                                                                                                                                        |
-|                                                  |                                                                                                                                                                                                                     |
-|                                                  | - 0 Do not cache (ranges requested from files taht are already cached due to a non range request will be a HIT)                                                                                                     |
-|                                                  | - 1 Use the `background_fetch <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/background_fetch.en.html>`_ plugin.                                                                              |
-|                                                  | - 2 Use the cache_range_requests plugin.                                                                                                                                                                            |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Delivery Service DNS TTL                         | The Time To Live on the DNS record for the Traffic Router A and AAAA records (``tr.<deliveryservice>.<cdn-domain>``) for a HTTP delivery service *or* for the A and                                                 |
-|                                                  | AAAA records of the edge name (``edge.<deliveryservice>.<cdn-domain>``).                                                                                                                                            |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Origin Server Base URL                           | The Origin Server's base URL. This includes the protocol (http or https). Example: ``http://movies.origin.com``                                                                                                     |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Use Multi Site Origin Feature                    | Enable the Multi Site Origin feature for this delivery service. See :ref:`rl-multi-site-origin`                                                                                                                     |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Multi Site Origin Algorithm                      | - 1 Consistent Hash spreads requests across multiple parents simultaneously based on hash of content URL.                                                                                                           |
-|                                                  | - 2 Strict Round Robin spreads requests across multiple parents simultaneously based on order of requests.                                                                                                          |
-|                                                  | - 3 IP Based Round Robin spreads requests across multiple parents simultaneously based on order of requests, but ensures that requests from the same IP always go to the same parent if available.                  |
-|                                                  | - 4 Latched uses only a single parent at any given time and switches to a new parent only if the current parent fails.                                                                                              |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| CCR profile                                      | The Traffic Router  profile for this delivery service. See :ref:`rl-ccr-profile`.                                                                                                                                   |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Maximum Bits per Second allowed globally         | The maximum bits per second this delivery service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6  will be used     |
-|                                                  | (depending on whether this was a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used.                                                                                                   |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Maximum Transactions per Second allowed globally | The maximum transactions per se this delivery service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6  will be used |
-|                                                  | (depending on whether this was a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used.                                                                                                   |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Geo Miss Default Latitude                        | Default Latitude for this delivery service. When client localization fails for both Coverage Zone and Geo Lookup, this the client will be routed as if it was at this lat.                                          |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Geo Miss Default Longitude                       | Default Longitude for this delivery service. When client localization fails for bot Coverage Zone and Geo Lookup, this the client will be routed as if it was at this long.                                         |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Edge Header Rewrite Rules                        | Header Rewrite rules to apply for this delivery service at the EDGE tier. See :ref:`rl-header-rewrite`. [1]_                                                                                                        |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Mid Header Rewrite Rules                         | Header Rewrite rules to apply for this delivery service at the MID tier. See :ref:`rl-header-rewrite`. [1]_                                                                                                         |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Regex Remap Expression                           | Regex Remap rule to apply to this delivery service at the Edge tier. See `ATS documentation on regex_remap <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_remap.en.html>`_. [1]_        |
-|                                                  |                                                                                                                                                                                                                     |
-|                                                  | **Note:** you will not be able to save a Regex Remap Expression if you have Query String Handling set to drop query strings at the edge. See :ref:`rl-regex-remap`.                                                 |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Cache URL expression                             | Cache URL rule to apply to this delivery service. See `ATS documentation on cacheurl <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cacheurl.en.html>`_. [1]_                                 |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Raw remap text                                   | For HTTP and DNS deliveryservices, this will get added to the end of the remap line on the cache verbatim. For ANY_MAP deliveryservices this is the remap line. [1]_                                                |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Long Description                                 | Long description for this delivery service. To be consumed from the APIs by downstream tools (Portal).                                                                                                              |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Customer                                         | Customer description for this delivery service. To be consumed from the APIs by downstream tools (Portal).                                                                                                          |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Service                                          | Service description for this delivery service. To be consumed from the APIs by downstream tools (Portal).                                                                                                           |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Info URL                                         | Info URL  for this delivery service. To be consumed from the APIs by downstream tools (Portal).                                                                                                                     |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Check Path                                       | A path (ex: /crossdomain.xml) to verify the connection to the origin server with. This can be used by Check Extension scripts to do periodic health checks against the delivery service.                            |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Origin Shield (Pipe Delimited String)            | Experimental. Origin Shield string.                                                                                                                                                                                 |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Active                                           | When this is set to no Traffic Router will not serve DNS or HTTP responses for this delivery service.                                                                                                               |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Last Updated                                     | (Read Only) The last time this delivery service was updated.                                                                                                                                                        |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Number of edges assigned                         | (Read Only - change by clicking the **Server Assignments** button at the bottom) The number of EDGE caches assigned to this delivery service. See :ref:`rl-assign-edges`.                                           |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Number of static DNS entries                     | (Read Only - change by clicking the **Static DNS** button at the bottom) The number of static DNS entries for this delivery service. See :ref:`rl-static-dns`.                                                      |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Example delivery URL                             | (Read Only) An example of how the delivery URL may start. This could be multiple rows if multiple HOST_REGEXP entries have been entered.                                                                            |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Regular expressions for this delivery service    | A subtable of the regular expressions to use when routing traffic for this delivery service. See :ref:`rl-ds-regexp`.                                                                                               |
-+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-.. [1] These fields are not validated by Traffic Ops to be correct syntactically, and can cause Traffic Server to not start if invalid. Please use with caution.
-
-
-.. index::
-  Delivery Service Type
-
-.. _rl-ds-types:
-
-Delivery Service Types
-++++++++++++++++++++++
-One of the most important settings when creating the delivery service is the selection of the delivery service *type*. This type determines the routing method and the primary storage for the delivery service.
-
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|       Name      |                                                                                                                                                         Description                                                                                                                                                          |
-+=================+==============================================================================================================================================================================================================================================================================================================================+
-| HTTP            | HTTP Content Routing  - The Traffic Router DNS auth server returns its own IP address on DNS queries, and the client gets redirected to a specific cache                                                                                                                                                                     |
-|                 | in the nearest cache group using HTTP 302.  Use this for long sessions like HLS/HDS/Smooth live streaming, where a longer setup time is not a.                                                                                                                                                                               |
-|                 | problem.                                                                                                                                                                                                                                                                                                                     |
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| DNS             | DNS Content Routing - The Traffic Router DNS auth server returns an edge cache IP address to the client right away. The client will find the cache quickly                                                                                                                                                                   |
-|                 | but the Traffic Router can not route to a cache that already has this content in the cache group. Use this for smaller objects like web page images / objects.                                                                                                                                                               |
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| HTTP_NO_CACHE   | HTTP Content Routing, but the caches will not actually cache the content, they act as just proxies. The MID tier is bypassed.                                                                                                                                                                                                |
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| HTTP_LIVE       | HTTP Content routing, but where for "standard" HTTP content routing the objects are stored on disk, for this delivery service type the objects are stored                                                                                                                                                                    |
-|                 | on the RAM disks. Use this for linear TV. The MID tier is bypassed for this type.                                                                                                                                                                                                                                            |
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| HTTP_LIVE_NATNL | HTTP Content routing, same as HTTP_LIVE, but the MID tier is NOT bypassed.                                                                                                                                                                                                                                                   |
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| DNS_LIVE_NATNL  | DNS Content routing, but where for "standard" DNS content routing the objects are stored on disk, for this delivery service type the objects are stored                                                                                                                                                                      |
-|                 | on the RAM disks. Use this for linear TV. The MID tier is NOT bypassed for this type.                                                                                                                                                                                                                                        |
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| DNS_LIVE        | DNS Content routing, same as DNS_LIVE_NATNL, but the MID tier is bypassed.                                                                                                                                                                                                                                                   |
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| ANY_MAP         | ANY_MAP is not known to Traffic Router. For this deliveryservice, the "Raw remap text" field in the input form will be used as the remap line on the cache.                                                                                                                                                                  |
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| STEERING        | The Delivery Service will be used to route to other delivery services.  The target delivery services Traffic Router and the routing weights for those delivery services will be defined by an admin or steering user.  For more information see the `steering feature <traffic_router.html#steering-feature>`_ documentation |
-+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-
-.. Note:: Once created, the Traffic Ops user interface does not allow you to change the delivery service type; the drop down is greyed out. There are many things that can go wrong when changing the type, and it is safer to delete the delivery service, and recreate it.
-
-Federations
-+++++++++++
-  Federations allow for other (federated) CDNs (at a different ISP, MSO, etc) to add a list of resolvers and a CNAME to a delivery service Traffic Ops.  When a request is made from one of federated CDN's clients, Traffic Router will return the CNAME configured in the federation mapping.  This allows the federated CDN to serve the content without the content provider changing the URL, or having to manage multiple URLs.
-
-  Before adding a federation in the Traffic Ops UI, a user with the federations role needs to be created.  This user will be assigned to the federation and will be able to add resolvers to the federation via the Traffic Ops `Federation API <../development/traffic_ops_api/v12/federation.html>`_.
-
-.. index::
-  Header Rewrite
-
-.. _rl-header-rewrite:
-
-Header Rewrite Options and DSCP
-+++++++++++++++++++++++++++++++
-Most header manipulation and per-delivery service configuration overrides are done using the `ATS Header Rewrite Plugin <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/header_rewrite.en.html>`_. Traffic Control allows you to enter header rewrite rules to be applied at the edge and at the mid level. The syntax used in Traffic Ops is the same as the one described in the ATS documentation, except for some special strings that will get replaced:
-
-+-------------------+--------------------------+
-| Traffic Ops Entry |    Gets Replaced with    |
-+===================+==========================+
-| __RETURN__        | A newline                |
-+-------------------+--------------------------+
-| __CACHE_IPV4__    | The cache's IPv4 address |
-+-------------------+--------------------------+
-
-The deliveryservice screen also allows you to set the DSCP value of traffic sent to the client. This setting also results in a header_rewrite rule to be generated and applied to at the edge.
-
-.. Note:: The DSCP setting in the UI is *only* for setting traffic towards the client, and gets applied *after* the initial TCP handshake is complete, and the HTTP request is received (before that the cache can't determine what deliveryservice this request is for, and what DSCP to apply), so the DSCP feature can not be used for security settings - the TCP SYN-ACK is not going to be DSCP marked.
-
-
-.. index::
-  Token Based Authentication
-  Signed URLs
-
-.. _rl-signed-urls:
-
-Token Based Authentication
-++++++++++++++++++++++++++
-Token based authentication or *signed URLs* is implemented using the Traffic Server ``url_sig`` plugin. To sign a URL at the signing portal take the full URL, without any query string, and add on a query string with the following parameters:
-
-Client IP address
-        The client IP address that this signature is valid for.
-
-        ``C=<client IP address>``
-
-Expiration
-        The Expiration time (seconds since epoch) of this signature.
-
-        ``E=<expiration time in secs since unix epoch>``
-
-Algorithm
-        The Algorithm used to create the signature. Only 1 (HMAC_SHA1)
-        and 2 (HMAC_MD5) are supported at this time
-
-        ``A=<algorithm number>``
-
-Key index
-        Index of the key used. This is the index of the key in the
-        configuration file on the cache. The set of keys is a shared
-        secret between the signing portal and the edge caches. There
-        is one set of keys per reverse proxy domain (fqdn).
-
-        ``K=<key index used>``
-Parts
-        Parts to use for the signature, always excluding the scheme
-        (http://).  parts0 = fqdn, parts1..x is the directory parts
-        of the path, if there are more parts to the path than letters
-        in the parts param, the last one is repeated for those.
-        Examples:
-
-                1: use fqdn and all of URl path
-                0110: use part1 and part 2 of path only
-                01: use everything except the fqdn
-
-        ``P=<parts string (0's and 1's)>``
-
-Signature
-        The signature over the parts + the query string up to and
-        including "S=".
-
-        ``S=<signature>``
-
-.. seealso:: The url_sig `README <https://github.com/apache/trafficserver/blob/master/plugins/experimental/url_sig/README>`_.
-
-Generate URL Sig Keys
-^^^^^^^^^^^^^^^^^^^^^
-To generate a set of random signed url keys for this delivery service and store them in Traffic Vault, click the **Generate URL Sig Keys** button at the bottom of the delivery service details screen.
-
-
-.. rl-parent-selection:
-
-Parent Selection
-++++++++++++++++
-
-Parameters in the Edge (child) profile that influence this feature:
-
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-|                      Name                     |    Filename    |    Default    |                      Description                      |
-+===============================================+================+===============+=======================================================+
-| CONFIG proxy.config.                          | records.config | INT 1         | enable parent selection.  This is a required setting. |
-| http.parent_proxy_routing_enable              |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 1         | required for parent selection.                        |
-| url_remap.remap_required                      |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 0         | See                                                   |
-| http.no_dns_just_forward_to_parent            |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 1         |                                                       |
-| http.uncacheable_requests_bypass_parent       |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 1         |                                                       |
-| http.parent_proxy_routing_enable              |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 300       |                                                       |
-| http.parent_proxy.retry_time                  |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 10        |                                                       |
-| http.parent_proxy.fail_threshold              |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 4         |                                                       |
-| http.parent_proxy.total_connect_attempts      |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 2         |                                                       |
-| http.parent_proxy.per_parent_connect_attempts |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 30        |                                                       |
-| http.parent_proxy.connect_attempts_timeout    |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 0         |                                                       |
-| http.forward.proxy_auth_to_parent             |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 0         |                                                       |
-| http.parent_proxy_routing_enable              |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | STRING        |                                                       |
-| http.parent_proxy.file                        |                | parent.config |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config.                          | records.config | INT 3         |                                                       |
-| http.parent_proxy.connect_attempts_timeout    |                |               |                                                       |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| algorithm                                     | parent.config  | urlhash       | The algorithm to use.                                 |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-
-
-Parameters in the Mid (parent) profile that influence this feature:
-
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|      Name      |    Filename   | Default |                                                                                    Description                                                                                    |
-+================+===============+=========+===================================================================================================================================================================================+
-| domain_name    | CRConfig.json | -       | Only parents with the same value as the edge are going to be used as parents (to keep separation between CDNs)                                                                    |
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| weight         | parent.config | 1.0     | The weight of this parent, translates to the number of replicas in the consistent hash ring. This parameter only has effect with algorithm at the client set to "consistent_hash" |
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| port           | parent.config | 80      | The port this parent is listening on as a forward proxy.                                                                                                                          |
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| use_ip_address | parent.config | 0       | 1 means use IP(v4) address of this parent in the parent.config, 0 means use the host_name.domain_name concatenation.                                                              |
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-.. _rl-multi-site-origin:
-
-Multi Site Origin
-+++++++++++++++++
-.. Note:: The Multi Site Origin feature is based upon a feature n ATS that has yet to be submitted to Traffic Server upstream, until it is, set this to 0, or use the ATS rpm supplied on the trafficcontrol.apache.org website.
-
-Normally, the mid servers are not aware of any redundancy at the origin layer. With Multi Site Origin enabled this changes - Traffic Server (and Traffic Ops) are now made aware of the fact there are multiple origins, and can be configured to do more advanced failover and loadbalancing actions.
-
-With This feature enabled, origin servers (or origin server VIP names for a site) are going to be entered as servers in to the Traiffic Ops UI. Server type is ""
-
-
-Parameters in the Origin profile that influence this feature:
-
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-|                                   Name                                   |    Filename    |  Default   |                                            Description                                             |
-+==========================================================================+================+============+====================================================================================================+
-| CONFIG proxy.config. http.parent_proxy_routing_enable                    | records.config | INT 1      | enable parent selection.  This is a required setting.                                              |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| CONFIG proxy.config. url_remap.remap_required                            | records.config | INT 1      | required for parent selection.                                                                     |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| CONFIG proxy.config. http.parent_proxy.per_parent_connect_attempts       | records.config | INT 5      | maximum of 5 connection attempts per parent (parent.config list) within a transaction.             |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| CONFIG proxy.config. http.parent_proxy.total_connect_attempts            | records.config | INT 10     | maximum of 10 total connection attempts within a transaction.                                      |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| CONFIG proxy.config. http.parent_origin.simple_retry_enabled             | records.config | INT 1      | enables simple retry.                                                                              |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| CONFIG proxy.config. http.parent_origin.simple_retry_response_codes      | records.config | STRING 404 | the response code that invokes simple retry.  May be a comman separated list of response codes.    |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| CONFIG proxy.config. http.parent_origin.dead_server_retry_response_codes | records.config | STRING 503 | the response code that invokes dead server retry.  May be a comma separated list of response codes |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| CONFIG proxy.config. http.parent_origin.dead_server_retry_enabled        | records.config | INT 1      | enables dead server retry.                                                                         |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| CONFIG proxy.config. diags.debug.enabled                                 | records.config | INT 1      | enable debugging for testing only                                                                  |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-
-see :ref:`rl-multi-site-origin-qht` for a *quick how to* on this feature.
-
-.. _rl-ccr-profile:
-
-CCR Profile or Traffic Router Profile
-+++++++++++++++++++++++++++++++++++++
-
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|                   Name                  |      Config_file       |                                                                                                Description                                                                                                |
-+=========================================+========================+===========================================================================================================================================================================================================+
-| location                                | dns.zone               | Location to store the DNS zone files in the local file system of Traffic Router.                                                                                                                          |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| location                                | http-log4j.properties  | Location to find the log4j.properties file for Traffic Router.                                                                                                                                            |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| location                                | dns-log4j.properties   | Location to find the dns-log4j.properties file for Traffic Router.                                                                                                                                        |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| location                                | geolocation.properties | Location to find the log4j.properties file for Traffic Router.                                                                                                                                            |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| CDN_name                                | rascal-config.txt      | The human readable name of the CDN for this profile.                                                                                                                                                      |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| CoverageZoneJsonURL                     | CRConfig.xml           | The location (URL) to retrieve the coverage zone map file in JSON format from.                                                                                                                            |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| geolocation.polling.url                 | CRConfig.json          | The location (URL) to retrieve the geo database file from.                                                                                                                                                |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| geolocation.polling.interval            | CRConfig.json          | How often to refresh the coverage geo location database  in ms                                                                                                                                            |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| coveragezone.polling.interval           | CRConfig.json          | How often to refresh the coverage zone map in ms                                                                                                                                                          |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| coveragezone.polling.url                | CRConfig.json          | The location (URL) to retrieve the coverage zone map file in XML format from.                                                                                                                             |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| domain_name                             | CRConfig.json          | The top level domain of this Traffic Router instance.                                                                                                                                                     |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.expire                          | CRConfig.json          | The value for the expire field the Traffic Router DNS Server will respond with on Start of Authority (SOA) records.                                                                                       |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.minimum                         | CRConfig.json          | The value for the minimum field the Traffic Router DNS Server will respond with on SOA records.                                                                                                           |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.admin                           | CRConfig.json          | The DNS Start of Authority admin.  Should be a valid support email address for support if DNS is not working correctly.                                                                                   |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.retry                           | CRConfig.json          | The value for the retry field the Traffic Router DNS Server will respond with on SOA records.                                                                                                             |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.refresh                         | CRConfig.json          | The TTL the Traffic Router DNS Server will respond with on A records.                                                                                                                                     |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.ttls.NS                             | CRConfig.json          | The TTL the Traffic Router DNS Server will respond with on NS records.                                                                                                                                    |
-+-----------------------------------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------

<TRUNCATED>


[9/9] incubator-trafficcontrol git commit: This closes #674

Posted by fr...@apache.org.
This closes #674


Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/commit/b8cdd626
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/tree/b8cdd626
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/diff/b8cdd626

Branch: refs/heads/2.0.x
Commit: b8cdd626d743ece5f8f54734c4981ddef6bc1e23
Parents: 80ab694
Author: Eric Friedrich <fr...@apache.org>
Authored: Wed Jun 14 15:36:21 2017 -0400
Committer: Eric Friedrich <fr...@apache.org>
Committed: Wed Jun 14 15:36:21 2017 -0400

----------------------------------------------------------------------

----------------------------------------------------------------------



[4/9] incubator-trafficcontrol git commit: updated the documentation for migrating from 1.0 to 2.0 for Traffic Ops

Posted by fr...@apache.org.
updated the documentation for migrating from 1.0 to 2.0 for Traffic Ops

(cherry picked from commit 643796409da4f9918213e5f9d199c6b587ad4879)


Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/commit/80ab6944
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/tree/80ab6944
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/diff/80ab6944

Branch: refs/heads/2.0.x
Commit: 80ab6944c66a4100fef1d31edb5ecc49da0d92be
Parents: 5ccf06f
Author: Dewayne Richardson <de...@apache.org>
Authored: Wed Jun 14 09:49:45 2017 -0600
Committer: Eric Friedrich <fr...@apache.org>
Committed: Wed Jun 14 15:35:59 2017 -0400

----------------------------------------------------------------------
 docs/source/admin/index.rst                     |   10 +-
 docs/source/admin/traffic_ops/configuration.rst |  194 ++++
 docs/source/admin/traffic_ops/extensions.rst    |   88 ++
 docs/source/admin/traffic_ops/installation.rst  |  484 ++++++++
 .../traffic_ops/migration_from_10_to_20.rst     |   88 ++
 docs/source/admin/traffic_ops/using.rst         | 1079 ++++++++++++++++++
 docs/source/admin/traffic_ops_config.rst        |  194 ----
 docs/source/admin/traffic_ops_extensions.rst    |   88 --
 docs/source/admin/traffic_ops_install.rst       |  484 --------
 docs/source/admin/traffic_ops_using.rst         | 1079 ------------------
 10 files changed, 1938 insertions(+), 1850 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/80ab6944/docs/source/admin/index.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/index.rst b/docs/source/admin/index.rst
index e92f5e2..0dcf2f6 100644
--- a/docs/source/admin/index.rst
+++ b/docs/source/admin/index.rst
@@ -34,10 +34,11 @@ Once everything is installed, you will need to configure the servers to talk to
 .. toctree::
   :maxdepth: 3
 
-  traffic_ops_install.rst
-  traffic_ops_config.rst
-  traffic_ops_using.rst
-  traffic_ops_extensions.rst
+  traffic_ops/installation.rst
+  traffic_ops/migration_from_10_to_20.rst
+  traffic_ops/configuration.rst
+  traffic_ops/using.rst
+  traffic_ops/extensions.rst
   traffic_portal.rst
   traffic_monitor.rst
   traffic_router.rst
@@ -45,4 +46,3 @@ Once everything is installed, you will need to configure the servers to talk to
   traffic_server.rst
   traffic_vault.rst
   quick_howto/index.rst
-

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/80ab6944/docs/source/admin/traffic_ops/configuration.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops/configuration.rst b/docs/source/admin/traffic_ops/configuration.rst
new file mode 100644
index 0000000..14b8189
--- /dev/null
+++ b/docs/source/admin/traffic_ops/configuration.rst
@@ -0,0 +1,194 @@
+.. 
+.. 
+.. 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 Ops - Configuring
+%%%%%%%%%%%%%%%%%%%%%%%%%
+
+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`)         |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| coalesce_masklen_v4	   | ip_allow.config   | The masklen to use when coalescing v4 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| coalesce_number_v4 	   | ip_allow.config   | The number to use when coalescing v4 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm  |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| coalesce_masklen_v6	   | ip_allow.config   | The masklen to use when coalescing v6 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| coalesce_masklen_v6	   | ip_allow.config   | The masklen to use when coalescing v6 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| 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/blob/80ab6944/docs/source/admin/traffic_ops/extensions.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops/extensions.rst b/docs/source/admin/traffic_ops/extensions.rst
new file mode 100644
index 0000000..4aceebb
--- /dev/null
+++ b/docs/source/admin/traffic_ops/extensions.rst
@@ -0,0 +1,88 @@
+.. 
+.. 
+.. 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
+   

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/80ab6944/docs/source/admin/traffic_ops/installation.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops/installation.rst b/docs/source/admin/traffic_ops/installation.rst
new file mode 100644
index 0000000..d5965a5
--- /dev/null
+++ b/docs/source/admin/traffic_ops/installation.rst
@@ -0,0 +1,484 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. index::
+  Traffic Ops - Installing 
+  
+.. _rl-to-install:
+
+Traffic Ops - Installing
+%%%%%%%%%%%%%%%%%%%%%%%%
+
+System Requirements
+-------------------
+The user must have the following for a successful install:
+
+* CentOS 6
+* 4 vCPUs
+* 32GB RAM
+* 20 GB disk space
+* YUM repository with minimally the following dependecies avaliable
+
+  * apr 1.3.9-5 
+  * apr-util 1.3.9-3 
+  * apr-util-ldap 1.3.9-3   
+  * expat-devel 2.0.1-11 
+  * genisoimage 1.1.9-12  
+  * httpd 2.2.15
+  * httpd-tools 2.2.15  
+  * libpcap-devel 14:1.4
+  * mod_ssl  1:2.2.15-29
+  * mysql 5.1.71 
+  * autoconf 2.63-5.1.
+  * automake 1.11.1-4
+  * gcc 4.4.7-4
+  * gettext 0.17-16
+  * libcurl-devel 7.19.7-37
+  * libtool 2.2.6-15.5
+  * mysql-devel 5.1.73-3
+  * perl-CPAN 1.9402-136
+  * libcurl 7.19.7-37
+  * openssl 1.0.1e-30
+  * cloog-ppl 0.15.7-1.2
+  * cpp 4.4.7-4
+  * cvs 1.11.23-16
+  * libgomp 4.4.7-4
+  * libidn-devel 1.18-2
+  * m4 1.4.13-5
+  * mpfr 2.4.1-6
+  * perl-Digest-SHA 1:5.47-136
+  * ppl 0.10.2-11
+  * curl 7.19.7-37
+  * openssl-devel 1.0.1e-30
+ 
+* Access to `The Comprehensive Perl Archive Network (CPAN) <http://www.cpan.org/>`_
+
+.. Note:: The above versions are known to work on CentOS 6.5. Higher versions may work.
+
+.. Note:: Although Traffic Ops supports both MySQL and Postgres as a database, support for MySQL is more mature and better tested. It is best to use MySQL when first getting started, and the rest of this guide assumes MySQL as the database.
+
+Navigating the Install
+-----------------------
+To begin the install:
+
+1. Install Traffic Ops: 
+
+  Download the traffic_ops rpm package from http://trafficcontrol.apache.org/downloads/index.html
+  
+  ``sudo rpm -ivh traffic_ops-1.*.*-****.x86_64.rpm``
+
+
+
+
+
+2. After installation of Traffic Ops rpm enter the following command: ``sudo /opt/traffic_ops/install/bin/postinstall``
+
+  Example output::
+
+
+      trafficops-vm # /opt/traffic_ops/install/bin/postinstall
+
+      This script will build and package the required Traffic Ops perl modules.
+      In order to complete this operation, Development tools such as the gcc
+      compiler must be installed on this machine.
+
+      Hit ENTER to continue:
+
+
+  The first thing postinstall will do is install additional packages needed from the yum repo.
+
+  Ater that, it will automatically proceed to installing the required Perl packages from CPAN.
+
+  .. Note:: Especially when installing Traffic Ops for the first time on a system this can take a long time, since many dependencies for the Mojolicous application need to be downloaded. Expect 30 minutes. 
+
+  If there are any prompts in this phase, please just answer with the defaults (some CPAN installs can prompt for install questions). 
+
+  When this phase is complete, you will see:: 
+
+      ...
+      Successfully installed Test-Differences-0.63
+      Successfully installed DBIx-Class-Schema-Loader-0.07042
+      Successfully installed Time-HiRes-1.9726 (upgraded from 1.9719)
+      Successfully installed Mojolicious-Plugin-Authentication-1.26
+      113 distributions installed
+      Complete! Modules were installed into /opt/traffic_ops/app/local
+      Linking perl libraries...
+      Installing perl scripts
+
+
+      This script will initialize the Traffic Ops database.
+      Please enter the following information in order to completely
+      configure the Traffic Ops mysql database.
+
+
+      Database type [mysql]:
+
+
+  The next phase of the install will ask you about the local environment for your CDN.
+
+  .. Note:: Before proceeding to this step, the database has to have at least a root password, and needs to be started. When using mysql, please type ``service mysqld start`` as root in another terminal and follow the instructions on the screen to set the root password.
+
+  .. Note:: CentOS files note.
+
+  Example output::
+
+      Database type [mysql]:
+      Database name [traffic_ops_db]:
+      Database server hostname IP or FQDN [localhost]:
+      Database port number [3306]:
+      Traffic Ops database user [traffic_ops]:
+      Password for traffic_ops:
+      Re-Enter password for traffic_ops:
+
+      Error: passwords do not match, try again.
+
+      Password for traffic_ops:
+      Re-Enter password for traffic_ops:
+
+      Database server root (admin) user name [root]:
+      Database server root password:
+      Database Type: mysql
+      Database Name: traffic_ops_db
+      Hostname: localhost
+      Port: 3306
+      Database User: traffic_ops
+      Is the above information correct (y/n) [n]:  y
+
+      The database properties have been saved to /opt/traffic_ops/app/conf/production/database.conf
+
+        The database configuration has been saved.  Now we need to set some custom
+        fields that are necessary for the CDN to function correctly.
+
+
+      Traffic Ops url [https://localhost]:  https://traffic-ops.kabletown.net
+      Human-readable CDN Name.  (No whitespace, please) [kabletown_cdn]:
+      DNS sub-domain for which your CDN is authoritative [cdn1.kabletown.net]:
+      Fully qualified name of your CentOS 6.5 ISO kickstart tar file, or 'na' to skip and add files later [/var/cache/centos65.tgz]:  na
+      Fully qualified location to store your ISO kickstart files [/var/www/files]:
+
+      Traffic Ops URL: https://traffic-ops.kabletown.net
+      Traffic Ops Info URL: https://traffic-ops.kabletown.net/info
+      Domainname: cdn1.kabletown.net
+      CDN Name: kabletown_cdn
+      GeoLocation Polling URL: https://traffic-ops.kabletown.net/routing/GeoIP2-City.mmdb.gz
+      CoverageZone Polling URL: https://traffic-ops.kabletown.net/routing/coverage-zone.json
+
+      Is the above information correct (y/n) [n]:  y
+      Install information has been saved to /opt/traffic_ops/install/data/json/post_install.json
+
+
+      Adding an administration user to the Traffic Ops database.
+
+      Administration username for Traffic Ops:  admin
+      Password for the admin user admin:
+      Verify the password for admin:
+      Do you wish to create an ldap configuration for access to traffic ops [y/n] ? [n]:  n
+      creating database
+      Creating database...
+      Creating user...
+      Flushing privileges...
+      setting up database
+      Executing 'drop database traffic_ops_db'
+      Executing 'create database traffic_ops_db'
+      Creating database tables...
+      Migrating database...
+      goose: migrating db environment 'production', current version: 0, target: 20150316100000
+      OK    20141222103718_extension.sql
+      OK    20150108100000_add_job_deliveryservice.sql
+      OK    20150205100000_cg_location.sql
+      OK    20150209100000_cran_to_asn.sql
+      OK    20150210100000_ds_keyinfo.sql
+      OK    20150304100000_add_ip6_ds_routing.sql
+      OK    20150310100000_add_bg_fetch.sql
+      OK    20150316100000_move_hdr_rw.sql
+      Seeding database...
+      Database initialization succeeded.
+      seeding profile data...
+      name EDGE1 description Edge 1
+      name TR1 description Traffic Router 1
+      name TM1 description Traffic Monitor 1
+      name MID1 description Mid 1
+      seeding parameter data...
+
+  Explanation of the information that needs to be provided:
+
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    |                       Field                        |                                          Description                                          |
+    +====================================================+===============================================================================================+
+    | Database type                                      | mysql or postgres                                                                             |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Database name                                      | The name of the database Traffic Ops uses to store the configuration information              |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Database server hostname IP or FQDN                | The hostname of the database server                                                           |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Database port number                               | The database port number                                                                      |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Traffic Ops database user                          | The username Traffic Ops will use to read/write from the database                             |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Password for traffic ops                           | The password for the above database user                                                      |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Database server root (admin) user name             | Privileged database user that has permission to create the database and user for Traffic Ops  |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Database server root (admin) user password         | The password for the above privileged database user                                           |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Traffic Ops url                                    | The URL to connect to this instance of Traffic Ops, usually https://<traffic ops host FQDN>/  |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Human-readable CDN Name                            | The name of the first CDN traffic Ops will be managing                                        |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | DNS sub-domain for which your CDN is authoritative | The DNS domain that will be delegated to this Traffic Control CDN                             |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | name of your CentOS 6.5 ISO kickstart tar file     | See :ref:`Creating-CentOS-Kickstart`                                                          |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Administration username for Traffic Ops            | The Administration (highest privilege) Traffic Ops user to create;                            |
+    |                                                    | use this user to login for the first time and create other users                              |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+    | Password for the admin user                        | The password for the above user                                                               |
+    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
+
+
+  The postinstall script will now seed the database with some inital configuration settings for the CDN and the servers in the CDN.
+
+  The next phase is the download of the geo location database and configuration of information needed for SSL certificates.
+
+  Example output::
+
+    Downloading MaxMind data.
+    --2015-04-14 02:14:32--  http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.mmdb.gz
+    Resolving geolite.maxmind.com... 141.101.115.190, 141.101.114.190, 2400:cb00:2048:1::8d65:73be, ...
+    Connecting to geolite.maxmind.com|141.101.115.190|:80... connected.
+    HTTP request sent, awaiting response... 200 OK
+    Length: 17633433 (17M) [application/octet-stream]
+    Saving to: "GeoLite2-City.mmdb.gz"
+
+    100%[==================================================================================================================================================================>] 17,633,433  7.03M/s   in 2.4s
+
+    2015-04-14 02:14:35 (7.03 MB/s) - "GeoLite2-City.mmdb.gz" saved [17633433/17633433]
+
+    Copying coverage zone file to public dir.
+
+    Installing SSL Certificates.
+
+      We're now running a script to generate a self signed X509 SSL certificate.
+      When prompted to enter a pass phrase, just enter 'pass' each time.  The
+      pass phrase will be stripped from the private key before installation.
+
+      When prompted to enter a 'challenge password', just hit the ENTER key.
+
+      The remaining enformation Country, State, Locality, etc... are required to
+      generate a properly formatted SSL certificate.
+
+    Hit Enter when you are ready to continue:
+    Postinstall SSL Certificate Creation.
+
+    Generating an RSA Private Server Key.
+
+    Generating RSA private key, 1024 bit long modulus
+    ..........................++++++
+    .....................++++++
+    e is 65537 (0x10001)
+    Enter pass phrase for server.key:
+    Verifying - Enter pass phrase for server.key:
+
+    The server key has been generated.
+
+    Creating a Certificate Signing Request (CSR)
+
+    Enter pass phrase for server.key:
+    You are about to be asked to enter information that will be incorporated
+    into your certificate request.
+    What you are about to enter is what is called a Distinguished Name or a DN.
+    There are quite a few fields but you can leave some blank
+    For some fields there will be a default value,
+    If you enter '.', the field will be left blank.
+    -----
+    Country Name (2 letter code) [XX]:US
+    State or Province Name (full name) []:CO
+    Locality Name (eg, city) [Default City]:Denver
+    Organization Name (eg, company) [Default Company Ltd]:
+    Organizational Unit Name (eg, section) []:
+    Common Name (eg, your name or your server's hostname) []:
+    Email Address []:
+
+    Please enter the following 'extra' attributes
+    to be sent with your certificate request
+    A challenge password []:pass
+    An optional company name []:
+
+    The Certificate Signing Request has been generated.
+    Removing the pass phrase from the server key.
+    Enter pass phrase for server.key.orig:
+    writing RSA key
+
+    The pass phrase has been removed from the server key.
+
+    Generating a Self-signed certificate.
+    Signature ok
+    subject=/C=US/ST=CO/L=Denver/O=Default Company Ltd
+    Getting Private key
+
+    A server key and self signed certificate has been generated.
+
+    Installing the server key and server certificate.
+
+    The private key has been installed.
+
+    Installing the self signed certificate.
+
+    Saving the self signed csr.
+
+      The self signed certificate has now been installed.
+
+      You may obtain a certificate signed by a Certificate Authority using the
+      server.csr file saved in the current directory.  Once you have obtained
+      a signed certificate, copy it to /etc/pki/tls/certs/localhost.crt and
+      restart Traffic Ops.
+
+
+
+    SSL Certificates have been installed.
+
+    Starting Traffic Ops.
+
+    Starting Traffic Ops
+
+    Subroutine TrafficOps::has redefined at /opt/traffic_ops/app/local/lib/perl5/Mojo/Base.pm line 38.
+    Subroutine TrafficOps::has redefined at /opt/traffic_ops/app/local/lib/perl5/Mojo/Base.pm line 38.
+    Loading config from /opt/traffic_ops/app/conf/cdn.conf
+    Reading log4perl config from /opt/traffic_ops/app/conf/production/log4perl.conf
+    Starting hot deployment for Hypnotoad server 32192.
+
+    Waiting for Traffic Ops to start.
+
+
+    Shutdown Traffic Ops [y/n] [n]:  n
+
+    To start Traffic Ops:  service traffic_ops start
+    To stop Traffic Ops:   service traffic_ops stop
+
+    traffic_ops #
+
+Traffic Ops is now installed!
+
+Upgrading Traffic Ops
+=====================
+To upgrade:
+
+1. Enter the following command:``service traffic_ops stop``
+2. Enter the following command:``yum upgrade traffic_ops``
+3. See :ref:`rl-ps` to run postinstall.
+4. Enter the following command:``service traffic_ops start``
+
+Manually Generating and Installing the SSL Certificate
+------------------------------------------------------
+
+.. Note:: This section is valid for traffic-control 2.0.0 and later.
+
+Self-signed Certificate (Development)
+=====================================
+
+    Example Procedure::
+
+      $ openssl genrsa -des3 -passout pass:x -out localhost.pass.key 2048
+      Generating RSA private key, 2048 bit long modulus
+      ...
+      $ openssl rsa -passin pass:x -in localhost.pass.key -out localhost.key
+      writing RSA key
+      $ rm localhost.pass.key
+
+      $ openssl req -new -key localhost.key -out localhost.csr
+      You are about to be asked to enter information that will be incorporated
+      into your certificate request.
+      What you are about to enter is what is called a Distinguished Name or a DN.
+      There are quite a few fields but you can leave some blank
+      For some fields there will be a default value,
+      If you enter '.', the field will be left blank.
+      -----
+      Country Name (2 letter code) [XX]:US<enter>
+      State or Province Name (full name) []:CO<enter>
+      Locality Name (eg, city) [Default City]:Denver<enter>
+      Organization Name (eg, company) [Default Company Ltd]: <enter>
+      Organizational Unit Name (eg, section) []: <enter>
+      Common Name (eg, your name or your server's hostname) []: <enter>
+      Email Address []: <enter>
+
+      Please enter the following 'extra' attributes
+      to be sent with your certificate request
+      A challenge password []: pass<enter>
+      An optional company name []: <enter>
+      $ openssl x509 -req -sha256 -days 365 -in localhost.csr -signkey localhost.key -out localhost.crt
+      Signature ok
+      subject=/C=US/ST=CO/L=Denver/O=Default Company Ltd
+      Getting Private key
+      $ sudo cp localhost.crt /etc/pki/tls/certs
+      $ sudo cp localhost.key /etc/pki/tls/private
+      $ sudo chown trafops:trafops /etc/pki/tls/certs/localhost.crt
+      $ sudo chown trafops:trafops /etc/pki/tls/private/localhost.key
+
+Certificate from Certificate Authority (Production)
+===================================================
+
+.. Note:: You will need to know the appropriate answers when generating the certificate request file `trafficopss.csr` below.
+
+    Example Procedure::
+
+      $ openssl genrsa -des3 -passout pass:x -out trafficops.pass.key 2048
+      Generating RSA private key, 2048 bit long modulus
+      ...
+      $ openssl rsa -passin pass:x -in trafficops.pass.key -out trafficops.key
+      writing RSA key
+      $ rm localhost.pass.key
+
+      Generate the Certificate Signing Request (CSR) file needed for Certificate Authority (CA) request.
+
+      $ openssl req -new -key trafficops.key -out trafficops.csr
+      You are about to be asked to enter information that will be incorporated
+      into your certificate request.
+      What you are about to enter is what is called a Distinguished Name or a DN.
+      There are quite a few fields but you can leave some blank
+      For some fields there will be a default value,
+      If you enter '.', the field will be left blank.
+      -----
+      Country Name (2 letter code) [XX]: <enter country code>
+      State or Province Name (full name) []: <enter state or province>
+      Locality Name (eg, city) [Default City]: <enter locality name>
+      Organization Name (eg, company) [Default Company Ltd]: <enter organization name>
+      Organizational Unit Name (eg, section) []: <enter organizational unit name>
+      Common Name (eg, your name or your server's hostname) []: <enter server's hostname name>
+      Email Address []: <enter e-mail address>
+
+      Please enter the following 'extra' attributes
+      to be sent with your certificate request
+      A challenge password []: <enter challenge password>
+      An optional company name []: <enter>
+      $ sudo cp trafficops.key /etc/pki/tls/private
+      $ sudo chown trafops:trafops /etc/pki/tls/private/trafficops.key
+
+      You must then take the output file trafficops.csr and submit a request to your Certificate Authority (CA).
+      Once you get approved and receive your trafficops.crt file:
+
+      $ sudo cp trafficops.crt /etc/pki/tls/certs
+      $ sudo chown trafops:trafops /etc/pki/tls/certs/trafficops.crt
+
+      If necessary, install the CA certificates .pem and .crt in /etc/pki/tls/certs.
+
+      You will need to update the file /opt/traffic_ops/app/conf/cdn.conf with the following changes:
+            ...
+            e.g. given trafficops.crt and trafficops.key
+            'hypnotoad' => ...
+                'listen' => 'https://[::]:443?cert=/etc/pki/tls/certs/trafficops.crt&key=/etc/pki/tls/private/trafficops.key&ca=/etc/pki/tls/certs/localhost.ca&verify=0x00&ciphers=AES128-GCM-SHA256:HIGH:!RC4:!MD5:!aNULL:!EDH:!ED'
+             ...
+
+
+

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/80ab6944/docs/source/admin/traffic_ops/migration_from_10_to_20.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops/migration_from_10_to_20.rst b/docs/source/admin/traffic_ops/migration_from_10_to_20.rst
new file mode 100644
index 0000000..4133fee
--- /dev/null
+++ b/docs/source/admin/traffic_ops/migration_from_10_to_20.rst
@@ -0,0 +1,88 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. index::
+  Traffic Ops - Migrating from Traffic Ops 1.x to Traffic Ops 2.x
+  
+.. _rl-ps:
+
+Traffic Ops - Migrating from 1.x to 2.x
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+In Traffic Ops 2.x MySQL was removed and Postgres was replaced as the database of choice for the unforeseen future.  A Docker-based migration tool was developed to
+help with that conversion using an open source Postgres tool called `pgloader <http://pgloader.io/>`_.  The following instructions will help configuring the Migration tool
+
+System Requirements
+-------------------
+The user must have the following for a successful minimal install:
+
+* CentOS 7.2+
+* Docker installed (this migration was tested against version **docker-engine-selinux-17.05.0.ce-1.el7.centos.noarch.rpm**)
+* Postgres has been installed according to :ref:`rl-to-install`
+
+Setup the traffic_ops_db directory
+----------------------------------
+
+   Modify /opt dir permission to make it writable and owned by postgres:postgres
+
+   ::
+
+   $ sudo chmod 755 /opt 
+   
+   Download the Traffic Control tarball for 2.0.0
+
+   :: 
+
+     $ cd /opt
+     $ wget https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/<tarball_version>
+
+   Extract the **traffic_ops_db** dir to **/opt/traffic_ops_db**
+
+   :: 
+
+   $ tar -zxvf trafficcontrol-incubating-<version>.tar.gz --strip=1 trafficcontrol-incubating-<version>/traffic_ops_db
+   $ sudo chown -R postgres:postgres /opt/traffic_ops_db
+
+.. highlight:: none
+
+Migration Preparation
+---------------------
+Be sure there is connectivity between your MySQL server's IP address/port and your Postgres server's IP address/port.
+
+Navigating the Database Migration
+---------------------------------
+Begin the database migration after settings up the **/opt/traffic_ops_db** directory
+
+   Switch to the postgres user so permissions stay intact.
+   :: 
+
+   $ su - postgres
+   $ cd /opt/traffic_ops_db/
+
+1. Configure the **/opt/traffic_ops_db/pg-migration/mysql-to-postgres.env** migration for your source MySQL and target Postgres settings
+
+
+2. Run the migration, watch the console output for any errors (it may take some time)
+   :: 
+
+   $ ./migrate.sh
+
+
+  Your MySQL data should now be ported into your new instance of Postgres!
+
+
+
+
+


[3/9] incubator-trafficcontrol git commit: updated the documentation for migrating from 1.0 to 2.0 for Traffic Ops

Posted by fr...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/80ab6944/docs/source/admin/traffic_ops/using.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops/using.rst b/docs/source/admin/traffic_ops/using.rst
new file mode 100644
index 0000000..738cc1c
--- /dev/null
+++ b/docs/source/admin/traffic_ops/using.rst
@@ -0,0 +1,1079 @@
+..
+..
+.. 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.
+..
+
+.. |graph| image:: ../../../../traffic_ops/app/public/images/graph.png
+.. |info| image:: ../../../../traffic_ops/app/public/images/info.png
+.. |checkmark| image:: ../../../../traffic_ops/app/public/images/good.png
+.. |X| image:: ../../../../traffic_ops/app/public/images/bad.png
+.. |clock| image:: ../../../../traffic_ops/app/public/images/clock-black.png
+
+Traffic Ops - Using
+%%%%%%%%%%%%%%%%%%%
+
+
+The Traffic Ops Menu
+====================
+
+.. image:: ../12m.png
+
+The following tabs are available in the menu at the top of the Traffic Ops user interface.
+
+.. index::
+  Health Tab
+
+* **Health**
+
+  Information on the health of the system. Hover over this tab to get to the following options:
+
+  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
+  |     Option    |                                                            Description                                                             |
+  +===============+====================================================================================================================================+
+  | Table View    | A real time view into the main performance indicators of the CDNs managed by Traffic Control.                                      |
+  |               | This view is sourced directly by the Traffic Monitor data and is updated every 10 seconds.                                         |
+  |               | This is the default screen of Traffic Ops.                                                                                         |
+  |               | See :ref:`rl-health-table` for details.                                                                                            |
+  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
+  | Graph View    | A real graphical time view into the main performance indicators of the CDNs managed by Traffic Control.                            |
+  |               | This view is sourced by the Traffic Monitor data and is updated every 10 seconds.                                                  |
+  |               | On loading, this screen will show a history of 24 hours of data from Traffic Stats                                                 |
+  |               | See :ref:`rl-health-graph` for details.                                                                                            |
+  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
+  | Server Checks | A table showing the results of the periodic check extension scripts that are run. See :ref:`rl-server-checks`                      |
+  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
+  | Daily Summary | A graph displaying the daily peaks of bandwidth, overall bytes served per day, and overall bytes served since initial installation |
+  |               | per CDN.                                                                                                                           |
+  +---------------+------------------------------------------------------------------------------------------------------------------------------------+
+
+* **Delivery Services**
+
+  The main Delivery Service table. This is where you Create/Read/Update/Delete Delivery Services of all types. Hover over to get the following sub option:
+
+  +-------------+--------------------------------------+
+  |    Option   |             Description              |
+  +=============+======================================+
+  | Federations | Add/Edit/Delete Federation Mappings. |
+  +-------------+--------------------------------------+
+
+* **Servers**
+
+  The main Servers table. This is where you Create/Read/Update/Delete servers of all types.  Click the main tab to get to the main table, and hover over to get these sub options:
+
+  +-------------------+------------------------------------------------------------------------------------------+
+  |       Option      |                                       Description                                        |
+  +===================+==========================================================================================+
+  | Upload Server CSV | Bulk add of servers from a csv file. See :ref:`rl-bulkserver`                            |
+  +-------------------+------------------------------------------------------------------------------------------+
+
+* **Parameters**
+
+  Parameters and Profiles can be edited here. Hover over the tab to get the following options:
+
+  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+  |        Option       |                                                                             Description                                                                             |
+  +=====================+=====================================================================================================================================================================+
+  | Global Profile      | The table of global parameters. See :ref:`rl-param-prof`. This is where you Create/Read/Update/Delete parameters in the Global profile                              |
+  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+  | All Cache Groups    | The table of all parameters *that are assgined to a cachegroup* - this may be slow to pull up, as there can be thousands of parameters.                             |
+  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+  | All Profiles        | The table of all parameters *that are assgined to a profile* - this may be slow to pull up, as there can be thousands of parameters.                                |
+  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+  | Select Profile      | Select the parameter list by profile first, then get a table of just the parameters for that profile.                                                               |
+  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+  | Orphaned Parameters | A table of parameters that are not associated to any profile of cache group. These parameters either should be deleted or associated with a profile of cache group. |
+  +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+
+* **Tools**
+
+  Tools for working with Traffic Ops and it's servers. Hover over this tab to get the following options:
+
+  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
+  |       Option       |                                                            Description                                                            |
+  +====================+===================================================================================================================================+
+  | Generate ISO       | Generate a bootable image for any of the servers in the Servers table (or any server for that matter). See :ref:`rl-generate-iso` |
+  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
+  | Queue Updates      | Send Updates to the caches. See :ref:`rl-queue-updates`                                                                           |
+  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
+  | DB Dump            | Backup the Database to a .sql file.                                                                                               |
+  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
+  | Snapshot CRConfig  | Send updates to the Traffic Monitor / Traffic Router servers.  See :ref:`rl-queue-updates`                                        |
+  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
+  | Invalidate Content | Invalidate or purge content from all caches in the CDN. See :ref:`rl-purge`                                                       |
+  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
+  | Manage DNSSEC keys | Manage DNSSEC Keys for a chosen CDN.                                                                                              |
+  +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
+
+
+* **Misc**
+
+  Miscellaneous editing options. Hover over this tab to get the following options:
+
+  +--------------------+-------------------------------------------------------------------------------------------+
+  |       Option       |                                        Description                                        |
+  +====================+===========================================================================================+
+  | Cache Groups       | Create/Read/Update/Delete cache groups                                                    |
+  +--------------------+-------------------------------------------------------------------------------------------+
+  | Users              | Create/Read/Update/Delete users                                                           |
+  +--------------------+-------------------------------------------------------------------------------------------+
+  | Profiles           | Create/Read/Update/Delete profiles. See :ref:`rl-working-with-profiles`                   |
+  +--------------------+-------------------------------------------------------------------------------------------+
+  | Networks(ASNs)     | Create/Read/Update/Delete Autonomous System Numbers See :ref:`rl-asn-czf`                 |
+  +--------------------+-------------------------------------------------------------------------------------------+
+  | Hardware           | Get detailed hardware information (note: this should be moved to a Traffic Ops Extension) |
+  +--------------------+-------------------------------------------------------------------------------------------+
+  | Data Types         | Create/Read/Update/Delete data types                                                      |
+  +--------------------+-------------------------------------------------------------------------------------------+
+  | Divisions          | Create/Read/Update/Delete divisions                                                       |
+  +--------------------+-------------------------------------------------------------------------------------------+
+  | Regions            | Create/Read/Update/Delete regions                                                         |
+  +--------------------+-------------------------------------------------------------------------------------------+
+  | Physical Locations | Create/Read/Update/Delete locations                                                       |
+  +--------------------+-------------------------------------------------------------------------------------------+
+
+.. index::
+  Change Log
+
+* **ChangeLog**
+
+  The Changelog table displays the changes that are being made to the Traffic Ops database through the Traffic Ops user interface. This tab will show the number of changes since you last visited this tab in (brackets) since the last time you visited this tab. There are currently no sub menus for this tab.
+
+
+* **Help**
+
+  Help for Traffic Ops and Traffic Control. Hover over this tab to get the following options:
+
+  +---------------+---------------------------------------------------------------------+
+  |     Option    |                             Description                             |
+  +===============+=====================================================================+
+  | About         | Traffic Ops information, such as version, database information, etc |
+  +---------------+---------------------------------------------------------------------+
+  | Release Notes | Release notes for the most recent releases of Traffic Ops           |
+  +---------------+---------------------------------------------------------------------+
+  | Logout        | Logout from Traffic Ops                                             |
+  +---------------+---------------------------------------------------------------------+
+
+
+.. index::
+  Edge Health
+  Health
+
+Health
+======
+
+.. _rl-health-table:
+
+The Health Table
+++++++++++++++++
+The Health table is the default landing screen for Traffic Ops, it displays the status of the EDGE caches in a table form directly from Traffic Monitor (bypassing Traffic Stats), sorted by Mbps Out. The columns in this table are:
+
+
+* **Profile**: the Profile of this server or ALL, meaning this row shows data for multiple servers, and the row shows the sum of all values.
+* **Host Name**: the host name of the server or ALL, meaning this row shows data for multiple servers, and the row shows the sum of all values.
+* **Edge Cache Group**: the edge cache group short name or ALL, meaning this row shows data for multiple servers, and the row shows the sum of all values.
+* **Healthy**: indicates if this cache is healthy according to the Health Protocol. A row with ALL in any of the columns will always show a |checkmark|, this column is valid only for individual EDGE caches.
+* **Admin**: shows the administrative status of the server.
+* **Connections**: the number of connections this cache (or group of caches) has open (``ats.proxy.process.http.current_client_connections`` from ATS).
+* **Mbps Out**: the bandwidth being served out if this cache (or group of caches)
+
+Since the top line has ALL, ALL, ALL, it shows the total connections and bandwidth for all caches managed by this instance of Traffic Ops.
+
+.. _rl-health-graph:
+
+Graph View
+++++++++++
+The Graph View shows a live view of the last 24 hours of bits per seconds served and open connections at the edge in a graph. This data is sourced from Traffic Stats. If there are 2 CDNs configured, this view will show the statistis for both, and the graphs are stacked. On the left-hand side, the totals and immediate values as well as the percentage of total possible capacity are displayed. This view is update every 10 seconds.
+
+
+.. _rl-server-checks:
+
+Server Checks
++++++++++++++
+The server checks page is inteded to give an overview of the Servers managed by Traffic Control as well as their status. This data comes from `Traffic Ops extensions <traffic_ops_extensions.html>`_.
+
++------+-----------------------------------------------------------------------+
+| Name |                 Description                                           |
++======+=======================================================================+
+| ILO  | Ping the iLO interface for EDGE or MID servers                        |
++------+-----------------------------------------------------------------------+
+| 10G  | Ping the IPv4 address of the EDGE or MID servers                      |
++------+-----------------------------------------------------------------------+
+| 10G6 | Ping the IPv6 address of the EDGE or MID servers                      |
++------+-----------------------------------------------------------------------+
+| MTU  | Ping the EDGE or MID using the configured MTU from Traffic Ops        |
++------+-----------------------------------------------------------------------+
+| FQDN | DNS check that matches what the DNS servers responds with compared to |
+|      | what Traffic Ops has.                                                 |
++------+-----------------------------------------------------------------------+
+| DSCP | Checks the DSCP value of packets from the edge server to the Traffic  |
+|      | Ops server.                                                           |
++------+-----------------------------------------------------------------------+
+| RTR  | Content Router checks. Checks the health of the Content Routers.      |
+|      | Checks the health of the caches using the Content Routers.            |
++------+-----------------------------------------------------------------------+
+| CHR  | Cache Hit Ratio in percent.                                           |
++------+-----------------------------------------------------------------------+
+| CDU  | Total Cache Disk Usage in percent.                                    |
++------+-----------------------------------------------------------------------+
+| ORT  | Operational Readiness Test. Uses the ORT script on the edge and mid   |
+|      | servers to determine if the configuration in Traffic Ops matches the  |
+|      | configuration on the edge or mid. The user that this script runs as   |
+|      | must have an ssh key on the edge servers.                             |
++------+-----------------------------------------------------------------------+
+
+Daily Summary
++++++++++++++
+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 `Traffic Stats <traffic_stats.html>`_  section.
+
+.. _rl-server:
+
+Server
+======
+This view shows a table of all the servers in Traffic Ops. The table columns show the most important details of the server. The **IPAddrr** column is clickable to launch an ``ssh://`` link to this server. The |graph| icon will link to a Traffic Stats graph of this server for caches, and the |info| will link to the server status pages for other server types.
+
+
+Server Types
+++++++++++++
+These are the types of servers that can be managed in Traffic Ops:
+
++---------------+---------------------------------------------+
+|      Name     |                 Description                 |
++===============+=============================================+
+| EDGE          | Edge Cache                                  |
++---------------+---------------------------------------------+
+| MID           | Mid Tier Cache                              |
++---------------+---------------------------------------------+
+| ORG           | Origin                                      |
++---------------+---------------------------------------------+
+| CCR           | Comcast Content Router                      |
++---------------+---------------------------------------------+
+| RASCAL        | Rascal health polling & reporting           |
++---------------+---------------------------------------------+
+| TOOLS_SERVER  | Ops hosts for managment                     |
++---------------+---------------------------------------------+
+| RIAK          | Riak keystore                               |
++---------------+---------------------------------------------+
+| SPLUNK        | SPLUNK indexer search head etc              |
++---------------+---------------------------------------------+
+| TRAFFIC_STATS | traffic_stats server                        |
++---------------+---------------------------------------------+
+| INFLUXDB      | influxDb server                             |
++---------------+---------------------------------------------+
+
+
+.. index::
+  Bulk Upload Server
+
+.. _rl-bulkserver:
+
+Bulk Upload Server
+++++++++++++++++++
+
+
+
+Delivery Service
+================
+The fields in the Delivery Service view are:
+
+.. Sorry for the width of this table, don't know how to make the bullet lists work otherwise. Just set your monitor to 2560*1600, and put on your glasses.
+
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|                       Name                       |                                                                                                     Description                                                                                                     |
++==================================================+=====================================================================================================================================================================================================================+
+| XML ID                                           | A unique string that identifies this delivery service.                                                                                                                                                              |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Content Routing Type                             | The type of content routing this delivery service will use. See :ref:`rl-ds-types`.                                                                                                                                 |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Protocol                                         | The protocol to serve this delivery service to the clients with:                                                                                                                                                    |
+|                                                  |                                                                                                                                                                                                                     |
+|                                                  | -  0 http                                                                                                                                                                                                           |
+|                                                  | -  1 https                                                                                                                                                                                                          |
+|                                                  | -  2 both http and https                                                                                                                                                                                            |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| DSCP Tag                                         | The DSCP value to mark IP packets to the client with.                                                                                                                                                               |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Signed URLs                                      | Use Signed URLs? See :ref:`rl-signed-urls`.                                                                                                                                                                         |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Query String Handling                            | How to treat query strings:                                                                                                                                                                                         |
+|                                                  |                                                                                                                                                                                                                     |
+|                                                  | - 0 use in cache key and hand up to origin -this means each unique query string Is treated as a unique URL.                                                                                                         |
+|                                                  | - 1 Do not use in cache key, but pass up to origin - this means a 2 URLs that are the same except for the query string will match, and cache HIT, while the origin still sees original query string in the request. |
+|                                                  | - 2 Drop at edge - this means a 2 URLs that are the same except for  the query string will match, and cache HIT, while the origin will not see original query string in the request.                                |
+|                                                  |                                                                                                                                                                                                                     |
+|                                                  | **Note:** Choosing to drop query strings at the edge will preclude the use of a Regex Remap Expression. See :ref:`rl-regex-remap`.                                                                                  |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Geo Limit?                                       | Some services are intended to be limited by geography. The possible settings are are:                                                                                                                               |
+|                                                  |                                                                                                                                                                                                                     |
+|                                                  | - None - Do not limit by geography.                                                                                                                                                                                 |
+|                                                  | - CZF only - If the requesting IP is not in the Coverage Zone File, do not serve the request.                                                                                                                       |
+|                                                  | - CZF + US - If the requesting IP is not in the Coverage Zone File or not in the United States, do not serve the request.                                                                                           |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Geo Limit Redirect URL                           | (for HTTP routed delivery services only) This is the URL Traffic Router will redirect to when Geo Limit Failure. See :ref:`rl-tr-ngb`                                                                               |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Bypass FQDN                                      | (for HTTP routed delivery services only) This is the FQDN Traffic Router will redirect to (with the same path) when the max Bps or Max Tps for this deliveryservice are exceeded.                                   |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Bypass Ipv4                                      | (For DNS routed delivery services only) This is the address to respond to A requests with when the the max Bps or Max Tps for this delivery service are exceeded.                                                   |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Bypass IPv6                                      | (For DNS routed delivery services only) This is the address to respond to AAAA requests with when the the max Bps or Max Tps for this delivery service are exceeded.                                                |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| IPv6 Routing Enabled?                            | When set to yes, the Traffic Router will respond to AAAA DNS requests for the tr. and edge. names of this delivery service. Otherwise, only A records will be served.                                               |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Range Request Handling                           | (experimental)  How to treat range requests:                                                                                                                                                                        |
+|                                                  |                                                                                                                                                                                                                     |
+|                                                  | - 0 Do not cache (ranges requested from files taht are already cached due to a non range request will be a HIT)                                                                                                     |
+|                                                  | - 1 Use the `background_fetch <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/background_fetch.en.html>`_ plugin.                                                                              |
+|                                                  | - 2 Use the cache_range_requests plugin.                                                                                                                                                                            |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Delivery Service DNS TTL                         | The Time To Live on the DNS record for the Traffic Router A and AAAA records (``tr.<deliveryservice>.<cdn-domain>``) for a HTTP delivery service *or* for the A and                                                 |
+|                                                  | AAAA records of the edge name (``edge.<deliveryservice>.<cdn-domain>``).                                                                                                                                            |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Origin Server Base URL                           | The Origin Server's base URL. This includes the protocol (http or https). Example: ``http://movies.origin.com``                                                                                                     |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Use Multi Site Origin Feature                    | Enable the Multi Site Origin feature for this delivery service. See :ref:`rl-multi-site-origin`                                                                                                                     |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Multi Site Origin Algorithm                      | - 1 Consistent Hash spreads requests across multiple parents simultaneously based on hash of content URL.                                                                                                           |
+|                                                  | - 2 Strict Round Robin spreads requests across multiple parents simultaneously based on order of requests.                                                                                                          |
+|                                                  | - 3 IP Based Round Robin spreads requests across multiple parents simultaneously based on order of requests, but ensures that requests from the same IP always go to the same parent if available.                  |
+|                                                  | - 4 Latched uses only a single parent at any given time and switches to a new parent only if the current parent fails.                                                                                              |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| CCR profile                                      | The Traffic Router  profile for this delivery service. See :ref:`rl-ccr-profile`.                                                                                                                                   |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Maximum Bits per Second allowed globally         | The maximum bits per second this delivery service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6  will be used     |
+|                                                  | (depending on whether this was a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used.                                                                                                   |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Maximum Transactions per Second allowed globally | The maximum transactions per se this delivery service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6  will be used |
+|                                                  | (depending on whether this was a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used.                                                                                                   |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Geo Miss Default Latitude                        | Default Latitude for this delivery service. When client localization fails for both Coverage Zone and Geo Lookup, this the client will be routed as if it was at this lat.                                          |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Geo Miss Default Longitude                       | Default Longitude for this delivery service. When client localization fails for bot Coverage Zone and Geo Lookup, this the client will be routed as if it was at this long.                                         |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Edge Header Rewrite Rules                        | Header Rewrite rules to apply for this delivery service at the EDGE tier. See :ref:`rl-header-rewrite`. [1]_                                                                                                        |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Mid Header Rewrite Rules                         | Header Rewrite rules to apply for this delivery service at the MID tier. See :ref:`rl-header-rewrite`. [1]_                                                                                                         |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Regex Remap Expression                           | Regex Remap rule to apply to this delivery service at the Edge tier. See `ATS documentation on regex_remap <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_remap.en.html>`_. [1]_        |
+|                                                  |                                                                                                                                                                                                                     |
+|                                                  | **Note:** you will not be able to save a Regex Remap Expression if you have Query String Handling set to drop query strings at the edge. See :ref:`rl-regex-remap`.                                                 |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Cache URL expression                             | Cache URL rule to apply to this delivery service. See `ATS documentation on cacheurl <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cacheurl.en.html>`_. [1]_                                 |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Raw remap text                                   | For HTTP and DNS deliveryservices, this will get added to the end of the remap line on the cache verbatim. For ANY_MAP deliveryservices this is the remap line. [1]_                                                |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Long Description                                 | Long description for this delivery service. To be consumed from the APIs by downstream tools (Portal).                                                                                                              |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Customer                                         | Customer description for this delivery service. To be consumed from the APIs by downstream tools (Portal).                                                                                                          |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Service                                          | Service description for this delivery service. To be consumed from the APIs by downstream tools (Portal).                                                                                                           |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Info URL                                         | Info URL  for this delivery service. To be consumed from the APIs by downstream tools (Portal).                                                                                                                     |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Check Path                                       | A path (ex: /crossdomain.xml) to verify the connection to the origin server with. This can be used by Check Extension scripts to do periodic health checks against the delivery service.                            |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Origin Shield (Pipe Delimited String)            | Experimental. Origin Shield string.                                                                                                                                                                                 |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Active                                           | When this is set to no Traffic Router will not serve DNS or HTTP responses for this delivery service.                                                                                                               |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Last Updated                                     | (Read Only) The last time this delivery service was updated.                                                                                                                                                        |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Number of edges assigned                         | (Read Only - change by clicking the **Server Assignments** button at the bottom) The number of EDGE caches assigned to this delivery service. See :ref:`rl-assign-edges`.                                           |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Number of static DNS entries                     | (Read Only - change by clicking the **Static DNS** button at the bottom) The number of static DNS entries for this delivery service. See :ref:`rl-static-dns`.                                                      |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Example delivery URL                             | (Read Only) An example of how the delivery URL may start. This could be multiple rows if multiple HOST_REGEXP entries have been entered.                                                                            |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Regular expressions for this delivery service    | A subtable of the regular expressions to use when routing traffic for this delivery service. See :ref:`rl-ds-regexp`.                                                                                               |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+
+.. [1] These fields are not validated by Traffic Ops to be correct syntactically, and can cause Traffic Server to not start if invalid. Please use with caution.
+
+
+.. index::
+  Delivery Service Type
+
+.. _rl-ds-types:
+
+Delivery Service Types
+++++++++++++++++++++++
+One of the most important settings when creating the delivery service is the selection of the delivery service *type*. This type determines the routing method and the primary storage for the delivery service.
+
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|       Name      |                                                                                                                                                         Description                                                                                                                                                          |
++=================+==============================================================================================================================================================================================================================================================================================================================+
+| HTTP            | HTTP Content Routing  - The Traffic Router DNS auth server returns its own IP address on DNS queries, and the client gets redirected to a specific cache                                                                                                                                                                     |
+|                 | in the nearest cache group using HTTP 302.  Use this for long sessions like HLS/HDS/Smooth live streaming, where a longer setup time is not a.                                                                                                                                                                               |
+|                 | problem.                                                                                                                                                                                                                                                                                                                     |
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| DNS             | DNS Content Routing - The Traffic Router DNS auth server returns an edge cache IP address to the client right away. The client will find the cache quickly                                                                                                                                                                   |
+|                 | but the Traffic Router can not route to a cache that already has this content in the cache group. Use this for smaller objects like web page images / objects.                                                                                                                                                               |
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| HTTP_NO_CACHE   | HTTP Content Routing, but the caches will not actually cache the content, they act as just proxies. The MID tier is bypassed.                                                                                                                                                                                                |
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| HTTP_LIVE       | HTTP Content routing, but where for "standard" HTTP content routing the objects are stored on disk, for this delivery service type the objects are stored                                                                                                                                                                    |
+|                 | on the RAM disks. Use this for linear TV. The MID tier is bypassed for this type.                                                                                                                                                                                                                                            |
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| HTTP_LIVE_NATNL | HTTP Content routing, same as HTTP_LIVE, but the MID tier is NOT bypassed.                                                                                                                                                                                                                                                   |
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| DNS_LIVE_NATNL  | DNS Content routing, but where for "standard" DNS content routing the objects are stored on disk, for this delivery service type the objects are stored                                                                                                                                                                      |
+|                 | on the RAM disks. Use this for linear TV. The MID tier is NOT bypassed for this type.                                                                                                                                                                                                                                        |
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| DNS_LIVE        | DNS Content routing, same as DNS_LIVE_NATNL, but the MID tier is bypassed.                                                                                                                                                                                                                                                   |
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| ANY_MAP         | ANY_MAP is not known to Traffic Router. For this deliveryservice, the "Raw remap text" field in the input form will be used as the remap line on the cache.                                                                                                                                                                  |
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| STEERING        | The Delivery Service will be used to route to other delivery services.  The target delivery services Traffic Router and the routing weights for those delivery services will be defined by an admin or steering user.  For more information see the `steering feature <traffic_router.html#steering-feature>`_ documentation |
++-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+
+
+.. Note:: Once created, the Traffic Ops user interface does not allow you to change the delivery service type; the drop down is greyed out. There are many things that can go wrong when changing the type, and it is safer to delete the delivery service, and recreate it.
+
+Federations
++++++++++++
+  Federations allow for other (federated) CDNs (at a different ISP, MSO, etc) to add a list of resolvers and a CNAME to a delivery service Traffic Ops.  When a request is made from one of federated CDN's clients, Traffic Router will return the CNAME configured in the federation mapping.  This allows the federated CDN to serve the content without the content provider changing the URL, or having to manage multiple URLs.
+
+  Before adding a federation in the Traffic Ops UI, a user with the federations role needs to be created.  This user will be assigned to the federation and will be able to add resolvers to the federation via the Traffic Ops `Federation API <../development/traffic_ops_api/v12/federation.html>`_.
+
+.. index::
+  Header Rewrite
+
+.. _rl-header-rewrite:
+
+Header Rewrite Options and DSCP
++++++++++++++++++++++++++++++++
+Most header manipulation and per-delivery service configuration overrides are done using the `ATS Header Rewrite Plugin <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/header_rewrite.en.html>`_. Traffic Control allows you to enter header rewrite rules to be applied at the edge and at the mid level. The syntax used in Traffic Ops is the same as the one described in the ATS documentation, except for some special strings that will get replaced:
+
++-------------------+--------------------------+
+| Traffic Ops Entry |    Gets Replaced with    |
++===================+==========================+
+| __RETURN__        | A newline                |
++-------------------+--------------------------+
+| __CACHE_IPV4__    | The cache's IPv4 address |
++-------------------+--------------------------+
+
+The deliveryservice screen also allows you to set the DSCP value of traffic sent to the client. This setting also results in a header_rewrite rule to be generated and applied to at the edge.
+
+.. Note:: The DSCP setting in the UI is *only* for setting traffic towards the client, and gets applied *after* the initial TCP handshake is complete, and the HTTP request is received (before that the cache can't determine what deliveryservice this request is for, and what DSCP to apply), so the DSCP feature can not be used for security settings - the TCP SYN-ACK is not going to be DSCP marked.
+
+
+.. index::
+  Token Based Authentication
+  Signed URLs
+
+.. _rl-signed-urls:
+
+Token Based Authentication
+++++++++++++++++++++++++++
+Token based authentication or *signed URLs* is implemented using the Traffic Server ``url_sig`` plugin. To sign a URL at the signing portal take the full URL, without any query string, and add on a query string with the following parameters:
+
+Client IP address
+        The client IP address that this signature is valid for.
+
+        ``C=<client IP address>``
+
+Expiration
+        The Expiration time (seconds since epoch) of this signature.
+
+        ``E=<expiration time in secs since unix epoch>``
+
+Algorithm
+        The Algorithm used to create the signature. Only 1 (HMAC_SHA1)
+        and 2 (HMAC_MD5) are supported at this time
+
+        ``A=<algorithm number>``
+
+Key index
+        Index of the key used. This is the index of the key in the
+        configuration file on the cache. The set of keys is a shared
+        secret between the signing portal and the edge caches. There
+        is one set of keys per reverse proxy domain (fqdn).
+
+        ``K=<key index used>``
+Parts
+        Parts to use for the signature, always excluding the scheme
+        (http://).  parts0 = fqdn, parts1..x is the directory parts
+        of the path, if there are more parts to the path than letters
+        in the parts param, the last one is repeated for those.
+        Examples:
+
+                1: use fqdn and all of URl path
+                0110: use part1 and part 2 of path only
+                01: use everything except the fqdn
+
+        ``P=<parts string (0's and 1's)>``
+
+Signature
+        The signature over the parts + the query string up to and
+        including "S=".
+
+        ``S=<signature>``
+
+.. seealso:: The url_sig `README <https://github.com/apache/trafficserver/blob/master/plugins/experimental/url_sig/README>`_.
+
+Generate URL Sig Keys
+^^^^^^^^^^^^^^^^^^^^^
+To generate a set of random signed url keys for this delivery service and store them in Traffic Vault, click the **Generate URL Sig Keys** button at the bottom of the delivery service details screen.
+
+
+.. rl-parent-selection:
+
+Parent Selection
+++++++++++++++++
+
+Parameters in the Edge (child) profile that influence this feature:
+
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+|                      Name                     |    Filename    |    Default    |                      Description                      |
++===============================================+================+===============+=======================================================+
+| CONFIG proxy.config.                          | records.config | INT 1         | enable parent selection.  This is a required setting. |
+| http.parent_proxy_routing_enable              |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 1         | required for parent selection.                        |
+| url_remap.remap_required                      |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 0         | See                                                   |
+| http.no_dns_just_forward_to_parent            |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 1         |                                                       |
+| http.uncacheable_requests_bypass_parent       |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 1         |                                                       |
+| http.parent_proxy_routing_enable              |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 300       |                                                       |
+| http.parent_proxy.retry_time                  |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 10        |                                                       |
+| http.parent_proxy.fail_threshold              |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 4         |                                                       |
+| http.parent_proxy.total_connect_attempts      |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 2         |                                                       |
+| http.parent_proxy.per_parent_connect_attempts |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 30        |                                                       |
+| http.parent_proxy.connect_attempts_timeout    |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 0         |                                                       |
+| http.forward.proxy_auth_to_parent             |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 0         |                                                       |
+| http.parent_proxy_routing_enable              |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | STRING        |                                                       |
+| http.parent_proxy.file                        |                | parent.config |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| CONFIG proxy.config.                          | records.config | INT 3         |                                                       |
+| http.parent_proxy.connect_attempts_timeout    |                |               |                                                       |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+| algorithm                                     | parent.config  | urlhash       | The algorithm to use.                                 |
++-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
+
+
+Parameters in the Mid (parent) profile that influence this feature:
+
++----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|      Name      |    Filename   | Default |                                                                                    Description                                                                                    |
++================+===============+=========+===================================================================================================================================================================================+
+| domain_name    | CRConfig.json | -       | Only parents with the same value as the edge are going to be used as parents (to keep separation between CDNs)                                                                    |
++----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| weight         | parent.config | 1.0     | The weight of this parent, translates to the number of replicas in the consistent hash ring. This parameter only has effect with algorithm at the client set to "consistent_hash" |
++----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| port           | parent.config | 80      | The port this parent is listening on as a forward proxy.                                                                                                                          |
++----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| use_ip_address | parent.config | 0       | 1 means use IP(v4) address of this parent in the parent.config, 0 means use the host_name.domain_name concatenation.                                                              |
++----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+
+.. _rl-multi-site-origin:
+
+Multi Site Origin
++++++++++++++++++
+.. Note:: The Multi Site Origin feature is based upon a feature n ATS that has yet to be submitted to Traffic Server upstream, until it is, set this to 0, or use the ATS rpm supplied on the trafficcontrol.apache.org website.
+
+Normally, the mid servers are not aware of any redundancy at the origin layer. With Multi Site Origin enabled this changes - Traffic Server (and Traffic Ops) are now made aware of the fact there are multiple origins, and can be configured to do more advanced failover and loadbalancing actions.
+
+With This feature enabled, origin servers (or origin server VIP names for a site) are going to be entered as servers in to the Traiffic Ops UI. Server type is ""
+
+
+Parameters in the Origin profile that influence this feature:
+
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+|                                   Name                                   |    Filename    |  Default   |                                            Description                                             |
++==========================================================================+================+============+====================================================================================================+
+| CONFIG proxy.config. http.parent_proxy_routing_enable                    | records.config | INT 1      | enable parent selection.  This is a required setting.                                              |
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+| CONFIG proxy.config. url_remap.remap_required                            | records.config | INT 1      | required for parent selection.                                                                     |
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+| CONFIG proxy.config. http.parent_proxy.per_parent_connect_attempts       | records.config | INT 5      | maximum of 5 connection attempts per parent (parent.config list) within a transaction.             |
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+| CONFIG proxy.config. http.parent_proxy.total_connect_attempts            | records.config | INT 10     | maximum of 10 total connection attempts within a transaction.                                      |
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+| CONFIG proxy.config. http.parent_origin.simple_retry_enabled             | records.config | INT 1      | enables simple retry.                                                                              |
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+| CONFIG proxy.config. http.parent_origin.simple_retry_response_codes      | records.config | STRING 404 | the response code that invokes simple retry.  May be a comman separated list of response codes.    |
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+| CONFIG proxy.config. http.parent_origin.dead_server_retry_response_codes | records.config | STRING 503 | the response code that invokes dead server retry.  May be a comma separated list of response codes |
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+| CONFIG proxy.config. http.parent_origin.dead_server_retry_enabled        | records.config | INT 1      | enables dead server retry.                                                                         |
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+| CONFIG proxy.config. diags.debug.enabled                                 | records.config | INT 1      | enable debugging for testing only                                                                  |
++--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
+
+see :ref:`rl-multi-site-origin-qht` for a *quick how to* on this feature.
+
+.. _rl-ccr-profile:
+
+CCR Profile or Traffic Router Profile
++++++++++++++++++++++++++++++++++++++
+
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|                   Name                  |      Config_file       |                                                                                                Description                                                                                                |
++=========================================+========================+===========================================================================================================================================================================================================+
+| location                                | dns.zone               | Location to store the DNS zone files in the local file system of Traffic Router.                                                                                                                          |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| location                                | http-log4j.properties  | Location to find the log4j.properties file for Traffic Router.                                                                                                                                            |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| location                                | dns-log4j.properties   | Location to find the dns-log4j.properties file for Traffic Router.                                                                                                                                        |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| location                                | geolocation.properties | Location to find the log4j.properties file for Traffic Router.                                                                                                                                            |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| CDN_name                                | rascal-config.txt      | The human readable name of the CDN for this profile.                                                                                                                                                      |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| CoverageZoneJsonURL                     | CRConfig.xml           | The location (URL) to retrieve the coverage zone map file in JSON format from.                                                                                                                            |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| geolocation.polling.url                 | CRConfig.json          | The location (URL) to retrieve the geo database file from.                                                                                                                                                |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| geolocation.polling.interval            | CRConfig.json          | How often to refresh the coverage geo location database  in ms                                                                                                                                            |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| coveragezone.polling.interval           | CRConfig.json          | How often to refresh the coverage zone map in ms                                                                                                                                                          |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| coveragezone.polling.url                | CRConfig.json          | The location (URL) to retrieve the coverage zone map file in XML format from.                                                                                                                             |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| domain_name                             | CRConfig.json          | The top level domain of this Traffic Router instance.                                                                                                                                                     |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.soa.expire                          | CRConfig.json          | The value for the expire field the Traffic Router DNS Server will respond with on Start of Authority (SOA) records.                                                                                       |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.soa.minimum                         | CRConfig.json          | The value for the minimum field the Traffic Router DNS Server will respond with on SOA records.                                                                                                           |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.soa.admin                           | CRConfig.json          | The DNS Start of Authority admin.  Should be a valid support email address for support if DNS is not working correctly.                                                                                   |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.soa.retry                           | CRConfig.json          | The value for the retry field the Traffic Router DNS Server will respond with on SOA records.                                                                                                             |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.soa.refresh                         | CRConfig.json          | The TTL the Traffic Router DNS Server will respond with on A records.                                                                                                                                     |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.ttls.NS                             | CRConfig.json          | The TTL the Traffic Router DNS Server will respond with on NS records.                                                                                                                                    |
++-----------------------------------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------

<TRUNCATED>


[2/9] incubator-trafficcontrol git commit: updated the documentation for migrating from 1.0 to 2.0 for Traffic Ops

Posted by fr...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/80ab6944/docs/source/admin/traffic_ops_config.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops_config.rst b/docs/source/admin/traffic_ops_config.rst
deleted file mode 100644
index 390788c..0000000
--- a/docs/source/admin/traffic_ops_config.rst
+++ /dev/null
@@ -1,194 +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`)         |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| coalesce_masklen_v4	   | ip_allow.config   | The masklen to use when coalescing v4 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| coalesce_number_v4 	   | ip_allow.config   | The number to use when coalescing v4 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm  |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| coalesce_masklen_v6	   | ip_allow.config   | The masklen to use when coalescing v6 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| coalesce_masklen_v6	   | ip_allow.config   | The masklen to use when coalescing v6 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| 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/blob/80ab6944/docs/source/admin/traffic_ops_extensions.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops_extensions.rst b/docs/source/admin/traffic_ops_extensions.rst
deleted file mode 100644
index 4aceebb..0000000
--- a/docs/source/admin/traffic_ops_extensions.rst
+++ /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
-   

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/80ab6944/docs/source/admin/traffic_ops_install.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops_install.rst b/docs/source/admin/traffic_ops_install.rst
deleted file mode 100644
index d0caaf8..0000000
--- a/docs/source/admin/traffic_ops_install.rst
+++ /dev/null
@@ -1,484 +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.
-.. 
-
-.. index::
-  Traffic Ops - Installing 
-  
-.. _rl-ps:
-
-Installing Traffic Ops
-%%%%%%%%%%%%%%%%%%%%%%
-
-System Requirements
--------------------
-The user must have the following for a successful install:
-
-* CentOS 6
-* 4 vCPUs
-* 32GB RAM
-* 20 GB disk space
-* YUM repository with minimally the following dependecies avaliable
-
-  * apr 1.3.9-5 
-  * apr-util 1.3.9-3 
-  * apr-util-ldap 1.3.9-3   
-  * expat-devel 2.0.1-11 
-  * genisoimage 1.1.9-12  
-  * httpd 2.2.15
-  * httpd-tools 2.2.15  
-  * libpcap-devel 14:1.4
-  * mod_ssl  1:2.2.15-29
-  * mysql 5.1.71 
-  * autoconf 2.63-5.1.
-  * automake 1.11.1-4
-  * gcc 4.4.7-4
-  * gettext 0.17-16
-  * libcurl-devel 7.19.7-37
-  * libtool 2.2.6-15.5
-  * mysql-devel 5.1.73-3
-  * perl-CPAN 1.9402-136
-  * libcurl 7.19.7-37
-  * openssl 1.0.1e-30
-  * cloog-ppl 0.15.7-1.2
-  * cpp 4.4.7-4
-  * cvs 1.11.23-16
-  * libgomp 4.4.7-4
-  * libidn-devel 1.18-2
-  * m4 1.4.13-5
-  * mpfr 2.4.1-6
-  * perl-Digest-SHA 1:5.47-136
-  * ppl 0.10.2-11
-  * curl 7.19.7-37
-  * openssl-devel 1.0.1e-30
- 
-* Access to `The Comprehensive Perl Archive Network (CPAN) <http://www.cpan.org/>`_
-
-.. Note:: The above versions are known to work on CentOS 6.5. Higher versions may work.
-
-.. Note:: Although Traffic Ops supports both MySQL and Postgres as a database, support for MySQL is more mature and better tested. It is best to use MySQL when first getting started, and the rest of this guide assumes MySQL as the database.
-
-Navigating the Install
------------------------
-To begin the install:
-
-1. Install Traffic Ops: 
-
-  Download the traffic_ops rpm package from http://trafficcontrol.apache.org/downloads/index.html
-  
-  ``sudo rpm -ivh traffic_ops-1.*.*-****.x86_64.rpm``
-
-
-
-
-
-2. After installation of Traffic Ops rpm enter the following command: ``sudo /opt/traffic_ops/install/bin/postinstall``
-
-  Example output::
-
-
-      trafficops-vm # /opt/traffic_ops/install/bin/postinstall
-
-      This script will build and package the required Traffic Ops perl modules.
-      In order to complete this operation, Development tools such as the gcc
-      compiler must be installed on this machine.
-
-      Hit ENTER to continue:
-
-
-  The first thing postinstall will do is install additional packages needed from the yum repo.
-
-  Ater that, it will automatically proceed to installing the required Perl packages from CPAN.
-
-  .. Note:: Especially when installing Traffic Ops for the first time on a system this can take a long time, since many dependencies for the Mojolicous application need to be downloaded. Expect 30 minutes. 
-
-  If there are any prompts in this phase, please just answer with the defaults (some CPAN installs can prompt for install questions). 
-
-  When this phase is complete, you will see:: 
-
-      ...
-      Successfully installed Test-Differences-0.63
-      Successfully installed DBIx-Class-Schema-Loader-0.07042
-      Successfully installed Time-HiRes-1.9726 (upgraded from 1.9719)
-      Successfully installed Mojolicious-Plugin-Authentication-1.26
-      113 distributions installed
-      Complete! Modules were installed into /opt/traffic_ops/app/local
-      Linking perl libraries...
-      Installing perl scripts
-
-
-      This script will initialize the Traffic Ops database.
-      Please enter the following information in order to completely
-      configure the Traffic Ops mysql database.
-
-
-      Database type [mysql]:
-
-
-  The next phase of the install will ask you about the local environment for your CDN.
-
-  .. Note:: Before proceeding to this step, the database has to have at least a root password, and needs to be started. When using mysql, please type ``service mysqld start`` as root in another terminal and follow the instructions on the screen to set the root password.
-
-  .. Note:: CentOS files note.
-
-  Example output::
-
-      Database type [mysql]:
-      Database name [traffic_ops_db]:
-      Database server hostname IP or FQDN [localhost]:
-      Database port number [3306]:
-      Traffic Ops database user [traffic_ops]:
-      Password for traffic_ops:
-      Re-Enter password for traffic_ops:
-
-      Error: passwords do not match, try again.
-
-      Password for traffic_ops:
-      Re-Enter password for traffic_ops:
-
-      Database server root (admin) user name [root]:
-      Database server root password:
-      Database Type: mysql
-      Database Name: traffic_ops_db
-      Hostname: localhost
-      Port: 3306
-      Database User: traffic_ops
-      Is the above information correct (y/n) [n]:  y
-
-      The database properties have been saved to /opt/traffic_ops/app/conf/production/database.conf
-
-        The database configuration has been saved.  Now we need to set some custom
-        fields that are necessary for the CDN to function correctly.
-
-
-      Traffic Ops url [https://localhost]:  https://traffic-ops.kabletown.net
-      Human-readable CDN Name.  (No whitespace, please) [kabletown_cdn]:
-      DNS sub-domain for which your CDN is authoritative [cdn1.kabletown.net]:
-      Fully qualified name of your CentOS 6.5 ISO kickstart tar file, or 'na' to skip and add files later [/var/cache/centos65.tgz]:  na
-      Fully qualified location to store your ISO kickstart files [/var/www/files]:
-
-      Traffic Ops URL: https://traffic-ops.kabletown.net
-      Traffic Ops Info URL: https://traffic-ops.kabletown.net/info
-      Domainname: cdn1.kabletown.net
-      CDN Name: kabletown_cdn
-      GeoLocation Polling URL: https://traffic-ops.kabletown.net/routing/GeoIP2-City.mmdb.gz
-      CoverageZone Polling URL: https://traffic-ops.kabletown.net/routing/coverage-zone.json
-
-      Is the above information correct (y/n) [n]:  y
-      Install information has been saved to /opt/traffic_ops/install/data/json/post_install.json
-
-
-      Adding an administration user to the Traffic Ops database.
-
-      Administration username for Traffic Ops:  admin
-      Password for the admin user admin:
-      Verify the password for admin:
-      Do you wish to create an ldap configuration for access to traffic ops [y/n] ? [n]:  n
-      creating database
-      Creating database...
-      Creating user...
-      Flushing privileges...
-      setting up database
-      Executing 'drop database traffic_ops_db'
-      Executing 'create database traffic_ops_db'
-      Creating database tables...
-      Migrating database...
-      goose: migrating db environment 'production', current version: 0, target: 20150316100000
-      OK    20141222103718_extension.sql
-      OK    20150108100000_add_job_deliveryservice.sql
-      OK    20150205100000_cg_location.sql
-      OK    20150209100000_cran_to_asn.sql
-      OK    20150210100000_ds_keyinfo.sql
-      OK    20150304100000_add_ip6_ds_routing.sql
-      OK    20150310100000_add_bg_fetch.sql
-      OK    20150316100000_move_hdr_rw.sql
-      Seeding database...
-      Database initialization succeeded.
-      seeding profile data...
-      name EDGE1 description Edge 1
-      name TR1 description Traffic Router 1
-      name TM1 description Traffic Monitor 1
-      name MID1 description Mid 1
-      seeding parameter data...
-
-  Explanation of the information that needs to be provided:
-
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    |                       Field                        |                                          Description                                          |
-    +====================================================+===============================================================================================+
-    | Database type                                      | mysql or postgres                                                                             |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Database name                                      | The name of the database Traffic Ops uses to store the configuration information              |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Database server hostname IP or FQDN                | The hostname of the database server                                                           |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Database port number                               | The database port number                                                                      |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Traffic Ops database user                          | The username Traffic Ops will use to read/write from the database                             |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Password for traffic ops                           | The password for the above database user                                                      |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Database server root (admin) user name             | Privileged database user that has permission to create the database and user for Traffic Ops  |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Database server root (admin) user password         | The password for the above privileged database user                                           |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Traffic Ops url                                    | The URL to connect to this instance of Traffic Ops, usually https://<traffic ops host FQDN>/  |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Human-readable CDN Name                            | The name of the first CDN traffic Ops will be managing                                        |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | DNS sub-domain for which your CDN is authoritative | The DNS domain that will be delegated to this Traffic Control CDN                             |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | name of your CentOS 6.5 ISO kickstart tar file     | See :ref:`Creating-CentOS-Kickstart`                                                          |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Administration username for Traffic Ops            | The Administration (highest privilege) Traffic Ops user to create;                            |
-    |                                                    | use this user to login for the first time and create other users                              |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-    | Password for the admin user                        | The password for the above user                                                               |
-    +----------------------------------------------------+-----------------------------------------------------------------------------------------------+
-
-
-  The postinstall script will now seed the database with some inital configuration settings for the CDN and the servers in the CDN.
-
-  The next phase is the download of the geo location database and configuration of information needed for SSL certificates.
-
-  Example output::
-
-    Downloading MaxMind data.
-    --2015-04-14 02:14:32--  http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.mmdb.gz
-    Resolving geolite.maxmind.com... 141.101.115.190, 141.101.114.190, 2400:cb00:2048:1::8d65:73be, ...
-    Connecting to geolite.maxmind.com|141.101.115.190|:80... connected.
-    HTTP request sent, awaiting response... 200 OK
-    Length: 17633433 (17M) [application/octet-stream]
-    Saving to: "GeoLite2-City.mmdb.gz"
-
-    100%[==================================================================================================================================================================>] 17,633,433  7.03M/s   in 2.4s
-
-    2015-04-14 02:14:35 (7.03 MB/s) - "GeoLite2-City.mmdb.gz" saved [17633433/17633433]
-
-    Copying coverage zone file to public dir.
-
-    Installing SSL Certificates.
-
-      We're now running a script to generate a self signed X509 SSL certificate.
-      When prompted to enter a pass phrase, just enter 'pass' each time.  The
-      pass phrase will be stripped from the private key before installation.
-
-      When prompted to enter a 'challenge password', just hit the ENTER key.
-
-      The remaining enformation Country, State, Locality, etc... are required to
-      generate a properly formatted SSL certificate.
-
-    Hit Enter when you are ready to continue:
-    Postinstall SSL Certificate Creation.
-
-    Generating an RSA Private Server Key.
-
-    Generating RSA private key, 1024 bit long modulus
-    ..........................++++++
-    .....................++++++
-    e is 65537 (0x10001)
-    Enter pass phrase for server.key:
-    Verifying - Enter pass phrase for server.key:
-
-    The server key has been generated.
-
-    Creating a Certificate Signing Request (CSR)
-
-    Enter pass phrase for server.key:
-    You are about to be asked to enter information that will be incorporated
-    into your certificate request.
-    What you are about to enter is what is called a Distinguished Name or a DN.
-    There are quite a few fields but you can leave some blank
-    For some fields there will be a default value,
-    If you enter '.', the field will be left blank.
-    -----
-    Country Name (2 letter code) [XX]:US
-    State or Province Name (full name) []:CO
-    Locality Name (eg, city) [Default City]:Denver
-    Organization Name (eg, company) [Default Company Ltd]:
-    Organizational Unit Name (eg, section) []:
-    Common Name (eg, your name or your server's hostname) []:
-    Email Address []:
-
-    Please enter the following 'extra' attributes
-    to be sent with your certificate request
-    A challenge password []:pass
-    An optional company name []:
-
-    The Certificate Signing Request has been generated.
-    Removing the pass phrase from the server key.
-    Enter pass phrase for server.key.orig:
-    writing RSA key
-
-    The pass phrase has been removed from the server key.
-
-    Generating a Self-signed certificate.
-    Signature ok
-    subject=/C=US/ST=CO/L=Denver/O=Default Company Ltd
-    Getting Private key
-
-    A server key and self signed certificate has been generated.
-
-    Installing the server key and server certificate.
-
-    The private key has been installed.
-
-    Installing the self signed certificate.
-
-    Saving the self signed csr.
-
-      The self signed certificate has now been installed.
-
-      You may obtain a certificate signed by a Certificate Authority using the
-      server.csr file saved in the current directory.  Once you have obtained
-      a signed certificate, copy it to /etc/pki/tls/certs/localhost.crt and
-      restart Traffic Ops.
-
-
-
-    SSL Certificates have been installed.
-
-    Starting Traffic Ops.
-
-    Starting Traffic Ops
-
-    Subroutine TrafficOps::has redefined at /opt/traffic_ops/app/local/lib/perl5/Mojo/Base.pm line 38.
-    Subroutine TrafficOps::has redefined at /opt/traffic_ops/app/local/lib/perl5/Mojo/Base.pm line 38.
-    Loading config from /opt/traffic_ops/app/conf/cdn.conf
-    Reading log4perl config from /opt/traffic_ops/app/conf/production/log4perl.conf
-    Starting hot deployment for Hypnotoad server 32192.
-
-    Waiting for Traffic Ops to start.
-
-
-    Shutdown Traffic Ops [y/n] [n]:  n
-
-    To start Traffic Ops:  service traffic_ops start
-    To stop Traffic Ops:   service traffic_ops stop
-
-    traffic_ops #
-
-Traffic Ops is now installed!
-
-Upgrading Traffic Ops
-=====================
-To upgrade:
-
-1. Enter the following command:``service traffic_ops stop``
-2. Enter the following command:``yum upgrade traffic_ops``
-3. See :ref:`rl-ps` to run postinstall.
-4. Enter the following command:``service traffic_ops start``
-
-Manually Generating and Installing the SSL Certificate
-------------------------------------------------------
-
-.. Note:: This section is valid for traffic-control 2.0.0 and later.
-
-Self-signed Certificate (Development)
-=====================================
-
-    Example Procedure::
-
-      $ openssl genrsa -des3 -passout pass:x -out localhost.pass.key 2048
-      Generating RSA private key, 2048 bit long modulus
-      ...
-      $ openssl rsa -passin pass:x -in localhost.pass.key -out localhost.key
-      writing RSA key
-      $ rm localhost.pass.key
-
-      $ openssl req -new -key localhost.key -out localhost.csr
-      You are about to be asked to enter information that will be incorporated
-      into your certificate request.
-      What you are about to enter is what is called a Distinguished Name or a DN.
-      There are quite a few fields but you can leave some blank
-      For some fields there will be a default value,
-      If you enter '.', the field will be left blank.
-      -----
-      Country Name (2 letter code) [XX]:US<enter>
-      State or Province Name (full name) []:CO<enter>
-      Locality Name (eg, city) [Default City]:Denver<enter>
-      Organization Name (eg, company) [Default Company Ltd]: <enter>
-      Organizational Unit Name (eg, section) []: <enter>
-      Common Name (eg, your name or your server's hostname) []: <enter>
-      Email Address []: <enter>
-
-      Please enter the following 'extra' attributes
-      to be sent with your certificate request
-      A challenge password []: pass<enter>
-      An optional company name []: <enter>
-      $ openssl x509 -req -sha256 -days 365 -in localhost.csr -signkey localhost.key -out localhost.crt
-      Signature ok
-      subject=/C=US/ST=CO/L=Denver/O=Default Company Ltd
-      Getting Private key
-      $ sudo cp localhost.crt /etc/pki/tls/certs
-      $ sudo cp localhost.key /etc/pki/tls/private
-      $ sudo chown trafops:trafops /etc/pki/tls/certs/localhost.crt
-      $ sudo chown trafops:trafops /etc/pki/tls/private/localhost.key
-
-Certificate from Certificate Authority (Production)
-===================================================
-
-.. Note:: You will need to know the appropriate answers when generating the certificate request file `trafficopss.csr` below.
-
-    Example Procedure::
-
-      $ openssl genrsa -des3 -passout pass:x -out trafficops.pass.key 2048
-      Generating RSA private key, 2048 bit long modulus
-      ...
-      $ openssl rsa -passin pass:x -in trafficops.pass.key -out trafficops.key
-      writing RSA key
-      $ rm localhost.pass.key
-
-      Generate the Certificate Signing Request (CSR) file needed for Certificate Authority (CA) request.
-
-      $ openssl req -new -key trafficops.key -out trafficops.csr
-      You are about to be asked to enter information that will be incorporated
-      into your certificate request.
-      What you are about to enter is what is called a Distinguished Name or a DN.
-      There are quite a few fields but you can leave some blank
-      For some fields there will be a default value,
-      If you enter '.', the field will be left blank.
-      -----
-      Country Name (2 letter code) [XX]: <enter country code>
-      State or Province Name (full name) []: <enter state or province>
-      Locality Name (eg, city) [Default City]: <enter locality name>
-      Organization Name (eg, company) [Default Company Ltd]: <enter organization name>
-      Organizational Unit Name (eg, section) []: <enter organizational unit name>
-      Common Name (eg, your name or your server's hostname) []: <enter server's hostname name>
-      Email Address []: <enter e-mail address>
-
-      Please enter the following 'extra' attributes
-      to be sent with your certificate request
-      A challenge password []: <enter challenge password>
-      An optional company name []: <enter>
-      $ sudo cp trafficops.key /etc/pki/tls/private
-      $ sudo chown trafops:trafops /etc/pki/tls/private/trafficops.key
-
-      You must then take the output file trafficops.csr and submit a request to your Certificate Authority (CA).
-      Once you get approved and receive your trafficops.crt file:
-
-      $ sudo cp trafficops.crt /etc/pki/tls/certs
-      $ sudo chown trafops:trafops /etc/pki/tls/certs/trafficops.crt
-
-      If necessary, install the CA certificates .pem and .crt in /etc/pki/tls/certs.
-
-      You will need to update the file /opt/traffic_ops/app/conf/cdn.conf with the following changes:
-            ...
-            e.g. given trafficops.crt and trafficops.key
-            'hypnotoad' => ...
-                'listen' => 'https://[::]:443?cert=/etc/pki/tls/certs/trafficops.crt&key=/etc/pki/tls/private/trafficops.key&ca=/etc/pki/tls/certs/localhost.ca&verify=0x00&ciphers=AES128-GCM-SHA256:HIGH:!RC4:!MD5:!aNULL:!EDH:!ED'
-             ...
-
-
-


[6/9] incubator-trafficcontrol git commit: initial version of the traffic_ops_db top level project

Posted by fr...@apache.org.
initial version of the traffic_ops_db top level project

(cherry picked from commit ac0d7d761cfe8266a39e53d7687598f03eb8fdb7)


Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/commit/d20484de
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/tree/d20484de
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/diff/d20484de

Branch: refs/heads/2.0.x
Commit: d20484de7c6e233780511dcdd4d2609e975e6456
Parents: dde8674
Author: Dewayne Richardson <de...@apache.org>
Authored: Thu May 11 11:06:00 2017 -0600
Committer: Eric Friedrich <fr...@apache.org>
Committed: Wed Jun 14 15:35:59 2017 -0400

----------------------------------------------------------------------
 traffic_ops_db/bin/install_systemd_unit.sh      |  16 +++
 traffic_ops_db/docker/Dockerfile                |  25 ++++
 traffic_ops_db/docker/docker-compose.yml        |  42 +++++++
 traffic_ops_db/docker/todb.sh                   |  51 ++++++++
 traffic_ops_db/pg-migration/Dockerfile-convert  |  28 +++++
 traffic_ops_db/pg-migration/Dockerfile-mysql    |  26 ++++
 .../pg-migration/Dockerfile-mysql-to-postgres   |  38 ++++++
 traffic_ops_db/pg-migration/Dockerfile-pgloader |  19 +++
 traffic_ops_db/pg-migration/Dockerfile-postgres |  29 +++++
 traffic_ops_db/pg-migration/Dockerfile-waiter   |  24 ++++
 traffic_ops_db/pg-migration/README.md           |  16 +++
 traffic_ops_db/pg-migration/convert.yml         |  23 ++++
 traffic_ops_db/pg-migration/convert_bools.sql   | 112 +++++++++++++++++
 traffic_ops_db/pg-migration/migrate.sh          | 120 +++++++++++++++++++
 .../pg-migration/mysql-to-postgres.env          |  43 +++++++
 .../pg-migration/mysql-to-postgres.sh           |  65 ++++++++++
 .../pg-migration/mysql-to-postgres.yml          |  24 ++++
 .../pg-migration/mysql/conf.d/mysql.cnf         |  21 ++++
 traffic_ops_db/pg-migration/mysql_host.yml      |  24 ++++
 traffic_ops_db/pg-migration/pgloader.yml        |  23 ++++
 traffic_ops_db/pg-migration/postgres.yml        |  34 ++++++
 traffic_ops_db/pg-migration/runconvert.sh       |  15 +++
 traffic_ops_db/pg-migration/runmysql.sh         |  16 +++
 traffic_ops_db/pg-migration/runpgloader.sh      |  24 ++++
 traffic_ops_db/pg-migration/runwaiter.sh        |  13 ++
 traffic_ops_db/pg-migration/waiter.yml          |  24 ++++
 26 files changed, 895 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/bin/install_systemd_unit.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/bin/install_systemd_unit.sh b/traffic_ops_db/bin/install_systemd_unit.sh
new file mode 100644
index 0000000..321a101
--- /dev/null
+++ b/traffic_ops_db/bin/install_systemd_unit.sh
@@ -0,0 +1,16 @@
+#!/usr/bin/env bash
+
+#
+#  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.
+#
+

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/docker/Dockerfile
----------------------------------------------------------------------
diff --git a/traffic_ops_db/docker/Dockerfile b/traffic_ops_db/docker/Dockerfile
new file mode 100644
index 0000000..23556d6
--- /dev/null
+++ b/traffic_ops_db/docker/Dockerfile
@@ -0,0 +1,25 @@
+#
+#  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.
+#
+FROM postgres:latest
+
+MAINTAINER Dan Kirkwood
+
+# Postgres Access
+ENV POSTGRES_USER=$POSTGRES_USER
+ENV POSTGRES_HOST=$POSTGRES_HOST
+ENV POSTGRES_PORT=$POSTGRES_PORT
+ENV POSTGRES_DATABASE=$POSTGRES_DATABASE
+#COPY docker-entrypoint-initdb.d/* /docker-entrypoint-initdb.d
+
+EXPOSE "5432:5432"

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/docker/docker-compose.yml
----------------------------------------------------------------------
diff --git a/traffic_ops_db/docker/docker-compose.yml b/traffic_ops_db/docker/docker-compose.yml
new file mode 100644
index 0000000..494c154
--- /dev/null
+++ b/traffic_ops_db/docker/docker-compose.yml
@@ -0,0 +1,42 @@
+#
+#  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.
+#
+version: '2'
+
+services:
+  db:
+    build:
+      context: .
+      dockerfile: Dockerfile
+    environment:
+      - POSTGRES_HOST=localhost
+      - POSTGRES_PORT=5432
+      - POSTGRES_DATABASE=traffic_ops
+      - POSTGRES_USER=postgres
+      - POSTGRES_USER_UID=9999
+      - POSTGRES_USER_GID=9999
+      - PGDATA=${PGDATA}
+    ports:
+      - 5432:5432
+    volumes:
+      - ./pgdata:/pgdata
+      - ./logs:/var/log/postgresql
+    networks:
+      - default
+
+networks:
+  default:
+     driver: bridge
+
+volumes:
+  pgdata:

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/docker/todb.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/docker/todb.sh b/traffic_ops_db/docker/todb.sh
new file mode 100755
index 0000000..7a6e6e4
--- /dev/null
+++ b/traffic_ops_db/docker/todb.sh
@@ -0,0 +1,51 @@
+#!/usr/bin/env bash
+
+#
+#  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.
+#
+
+# Docker wrapper script to start/manage your Postgres container
+
+ACTION=$1
+
+PROJECT_NAME=trafficops
+CONTAINER_NAME=trafficops_db_1
+
+if [[ "$ACTION" == "setup" ]];then
+  createuser traffic_ops -U postgres -h localhost
+  createdb traffic_ops --owner traffic_ops -U postgres -h localhost 
+  psql -c "\l" -U postgres -h localhost
+  echo "Setup complete"
+
+elif [[ "$ACTION" == "run" ]];then
+  docker-compose -p $PROJECT_NAME up -d
+  echo "Started Docker container: $CONTAINER_NAME"
+
+elif [[ "$ACTION" == "stop" ]];then
+  docker-compose -p $PROJECT_NAME down -v
+  echo "Stopping Docker container: $CONTAINER_NAME"
+
+elif [[ "$ACTION" == "clean" ]];then
+  rm -rf pgdata
+  docker stop $CONTAINER_NAME
+  docker rm $CONTAINER_NAME
+  docker rmi $PROJECT_NAME
+
+elif [[ "$ACTION" == "seed" ]];then
+  docker-compose -p $PROJECT_NAME down -v
+else
+  echo "Valid actions: 'setup', 'run', 'stop', 'clean'"
+  exit 0
+fi
+
+docker ps

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/Dockerfile-convert
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/Dockerfile-convert b/traffic_ops_db/pg-migration/Dockerfile-convert
new file mode 100644
index 0000000..454f58a
--- /dev/null
+++ b/traffic_ops_db/pg-migration/Dockerfile-convert
@@ -0,0 +1,28 @@
+#
+#  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.
+#
+FROM dewrich/postgres:latest
+
+MAINTAINER Dan Kirkwood
+
+# Postgres Access
+ENV POSTGRES_HOST=$POSTGRES_HOST
+ENV POSTGRES_PORT=$POSTGRES_PORT
+ENV POSTGRES_DATABASE=$POSTGRES_DATABASE
+ENV POSTGRES_PASSWORD=$POSTGRES_PASSWORD
+
+RUN apt-get update 
+ADD pg-migration/runconvert.sh .
+ADD pg-migration/convert_bools.sql .
+
+CMD ./runconvert.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/Dockerfile-mysql
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/Dockerfile-mysql b/traffic_ops_db/pg-migration/Dockerfile-mysql
new file mode 100644
index 0000000..0b3d0df
--- /dev/null
+++ b/traffic_ops_db/pg-migration/Dockerfile-mysql
@@ -0,0 +1,26 @@
+#
+#  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.
+#
+FROM mysql:5.6
+
+MAINTAINER Dan Kirkwood
+
+# Mysql Access
+ENV MYSQL_HOST=$MYSQL_HOST
+ENV MYSQL_PORT=$MYSQL_PORT
+ENV MYSQL_PASSWORD=$MYSQL_PASSWORD
+ENV MYSQL_DATABASE=$MYSQL_DATABASE
+
+EXPOSE 3306
+ADD runmysql.sh /
+CMD /runmysql.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/Dockerfile-mysql-to-postgres
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/Dockerfile-mysql-to-postgres b/traffic_ops_db/pg-migration/Dockerfile-mysql-to-postgres
new file mode 100644
index 0000000..b1da689
--- /dev/null
+++ b/traffic_ops_db/pg-migration/Dockerfile-mysql-to-postgres
@@ -0,0 +1,38 @@
+#
+#  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.
+#
+FROM dimitri/pgloader:latest
+MAINTAINER Dan Kirkwood <da...@apache.org>
+
+# Traffic Ops Access
+ENV TO_SERVER=$TO_SERVER
+ENV TO_USER=$TO_USER
+ENV TO_PASSWORD=$TO_PASSWORD
+
+# Mysql Access
+ENV MYSQL_HOST=$MYSQL_HOST
+ENV MYSQL_PORT=$MYSQL_PORT
+ENV MYSQL_PASSWORD=$MYSQL_PASSWORD
+ENV MYSQL_DATABASE=$MYSQL_DATABASE
+
+# Postgres Access
+ENV POSTGRES_HOST=$POSTGRES_HOST
+ENV POSTGRES_PORT=$POSTGRES_PORT
+ENV POSTGRES_DATABASE=$POSTGRES_DATABASE
+ENV POSTGRES_PASSWORD=$POSTGRES_PASSWORD
+
+# install the tools for getting data
+RUN apt-get -y update && apt-get -y install curl mysql-client
+
+ADD mysql-to-postgres.sh .
+CMD ./mysql-to-postgres.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/Dockerfile-pgloader
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/Dockerfile-pgloader b/traffic_ops_db/pg-migration/Dockerfile-pgloader
new file mode 100644
index 0000000..fec7f97
--- /dev/null
+++ b/traffic_ops_db/pg-migration/Dockerfile-pgloader
@@ -0,0 +1,19 @@
+#
+#  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.
+#
+FROM dimitri/pgloader:latest
+MAINTAINER Dan Kirkwood <da...@apache.org>
+
+ADD pg-migration/runpgloader.sh .
+ADD create_tables.sql .
+CMD ./runpgloader.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/Dockerfile-postgres
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/Dockerfile-postgres b/traffic_ops_db/pg-migration/Dockerfile-postgres
new file mode 100644
index 0000000..6f3c634
--- /dev/null
+++ b/traffic_ops_db/pg-migration/Dockerfile-postgres
@@ -0,0 +1,29 @@
+#
+#  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.
+#
+FROM dewrich/postgres:latest
+
+MAINTAINER Dan Kirkwood
+
+# Postgres Access
+ENV POSTGRES_HOST=$POSTGRES_HOST
+ENV POSTGRES_PORT=$POSTGRES_PORT
+ENV POSTGRES_DATABASE=$POSTGRES_DATABASE
+ENV POSTGRES_PASSWORD=$POSTGRES_PASSWORD
+
+# Adjust PostgreSQL configuration so that remote connections to the
+# database are possible.
+RUN echo "host all  all    0.0.0.0/0  md5" >> $PGDATA/pg_hba.conf
+RUN echo "listen_addresses='*'" >> $PGDATA/postgresql.conf
+
+EXPOSE "5432:5432"

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/Dockerfile-waiter
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/Dockerfile-waiter b/traffic_ops_db/pg-migration/Dockerfile-waiter
new file mode 100644
index 0000000..0531c71
--- /dev/null
+++ b/traffic_ops_db/pg-migration/Dockerfile-waiter
@@ -0,0 +1,24 @@
+#
+#  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.
+#
+FROM dimitri/pgloader:latest
+
+MAINTAINER Dewayne Richardson
+
+RUN apt-get -y update && apt-get -y install netcat
+
+ENV WAITER_HOST=$WAITER_HOST
+ENV WAITER_PORT=$WAITER_PORT
+
+ADD pg-migration/runwaiter.sh .
+CMD ./runwaiter.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/README.md
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/README.md b/traffic_ops_db/pg-migration/README.md
new file mode 100644
index 0000000..005e6e5
--- /dev/null
+++ b/traffic_ops_db/pg-migration/README.md
@@ -0,0 +1,16 @@
+# Converts existing mysql `traffic_ops` database to postgres
+
+* Requires a fairly recent ( 17.05.0-ce ) version of `docker-engine` and `docker-compose`.
+
+* Modify the mysql-to-postgres.env file for the parameters in your Traffic Ops environment
+
+* Ensure that your new Postgres service is running (local or remote)
+
+* A sample Postgres Docker container has been provided for testing
+  1. `cd ../docker`
+  2. `$ sh todb.sh run` - to download/start your Postgres Test Docker container
+  3. `$ sh todb.sh setup` - to create your new 'traffic_ops' role and 'traffic_ops' database
+
+* Run the Mysql to Postgres Migration Docker flow
+  1. `$ cd ../pg-migration`
+  2. `$ sh migrate.sh`

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/convert.yml
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/convert.yml b/traffic_ops_db/pg-migration/convert.yml
new file mode 100644
index 0000000..fb130e9
--- /dev/null
+++ b/traffic_ops_db/pg-migration/convert.yml
@@ -0,0 +1,23 @@
+#
+#  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.
+#
+version: '2'
+
+services:
+  # convert runs necessary post-import conversion(s) in postgres
+  convert:
+    build:
+      context: ..
+      dockerfile: pg-migration/Dockerfile-convert
+    env_file:
+      - mysql-to-postgres.env

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/convert_bools.sql
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/convert_bools.sql b/traffic_ops_db/pg-migration/convert_bools.sql
new file mode 100755
index 0000000..5835e6c
--- /dev/null
+++ b/traffic_ops_db/pg-migration/convert_bools.sql
@@ -0,0 +1,112 @@
+-- Licensed to the Apache Software Foundation (ASF) under one
+-- or more contributor license agreements.  See the NOTICE file
+-- distributed with this work for additional information
+-- regarding copyright ownership.  The ASF licenses this file
+-- to you 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.
+
+ALTER TABLE cdn
+  ALTER COLUMN dnssec_enabled DROP DEFAULT,
+	ALTER COLUMN dnssec_enabled TYPE boolean
+		USING CASE WHEN dnssec_enabled = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN dnssec_enabled SET DEFAULT FALSE;
+
+ALTER TABLE deliveryservice
+  ALTER COLUMN active DROP DEFAULT,
+	ALTER COLUMN active TYPE boolean
+		USING CASE WHEN active = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN active SET DEFAULT FALSE;
+
+ALTER TABLE deliveryservice
+  ALTER COLUMN signed DROP DEFAULT,
+	ALTER COLUMN signed TYPE boolean
+		USING CASE WHEN signed = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN signed SET DEFAULT FALSE;
+
+ALTER TABLE deliveryservice
+  ALTER COLUMN ipv6_routing_enabled DROP DEFAULT,
+	ALTER COLUMN ipv6_routing_enabled TYPE boolean
+		USING CASE WHEN ipv6_routing_enabled = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN ipv6_routing_enabled SET DEFAULT FALSE;
+
+ALTER TABLE deliveryservice
+  ALTER COLUMN multi_site_origin DROP DEFAULT,
+	ALTER COLUMN multi_site_origin TYPE boolean
+		USING CASE WHEN multi_site_origin = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN multi_site_origin SET DEFAULT FALSE;
+
+ALTER TABLE deliveryservice
+  ALTER COLUMN regional_geo_blocking DROP DEFAULT,
+	ALTER COLUMN regional_geo_blocking TYPE boolean
+		USING CASE WHEN regional_geo_blocking = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN regional_geo_blocking SET DEFAULT FALSE;
+
+ALTER TABLE deliveryservice
+  ALTER COLUMN logs_enabled DROP DEFAULT,
+	ALTER COLUMN logs_enabled TYPE boolean
+		USING CASE WHEN logs_enabled = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN logs_enabled SET DEFAULT FALSE;
+
+  ALTER TABLE goose_db_version
+  ALTER COLUMN is_applied DROP DEFAULT,
+	ALTER COLUMN is_applied TYPE boolean
+		USING CASE WHEN is_applied = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN is_applied SET DEFAULT FALSE;
+
+ALTER TABLE parameter
+  ALTER COLUMN secure DROP DEFAULT,
+	ALTER COLUMN secure TYPE boolean
+		USING CASE WHEN secure = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN secure SET DEFAULT FALSE;
+
+ALTER TABLE server
+  ALTER COLUMN upd_pending DROP DEFAULT,
+	ALTER COLUMN upd_pending TYPE boolean
+		USING CASE WHEN upd_pending = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN upd_pending SET DEFAULT FALSE;
+
+ALTER TABLE tm_user
+  ALTER COLUMN new_user DROP DEFAULT,
+	ALTER COLUMN new_user TYPE boolean
+		USING CASE WHEN new_user = 1 THEN TRUE
+			ELSE FALSE
+			END,
+  ALTER COLUMN new_user SET DEFAULT FALSE;
+
+ALTER TABLE to_extension
+  ALTER COLUMN isactive DROP DEFAULT,
+	ALTER COLUMN isactive TYPE boolean
+		USING CASE WHEN isactive = 1 THEN TRUE
+			ELSE FALSE
+			END,
+    ALTER COLUMN isactive SET DEFAULT FALSE;

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/migrate.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/migrate.sh b/traffic_ops_db/pg-migration/migrate.sh
new file mode 100755
index 0000000..f5b4388
--- /dev/null
+++ b/traffic_ops_db/pg-migration/migrate.sh
@@ -0,0 +1,120 @@
+#!/bin/bash 
+#
+#  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.
+#
+
+. mysql-to-postgres.env
+
+#Traffic Ops Settings
+# The following configs should be configured to point to the 
+# Traffic Ops instances that is connected to the MySQL that 
+# you want to convert
+separator="---------------------------------------"
+docker_project="pgmigration"
+
+function display_env() {
+
+  echo "TO_SERVER: $TO_SERVER"
+  echo "TO_USER: $TO_USER"
+  echo "TO_PASSWORD: $TO_PASSWORD"
+  echo "MYSQL_HOST: $MYSQL_HOST"
+  echo "MYSQL_PORT: $MYSQL_PORT"
+  echo "MYSQL_DATABASE: $MYSQL_DATABASE"
+  echo "MYSQL_USER: $MYSQL_USER"
+  echo "MYSQL_PASSWORD: $MYSQL_PASSWORD"
+
+  echo "POSTGRES_HOST: $POSTGRES_HOST"
+  echo "POSTGRES_PORT: $POSTGRES_PORT"
+  echo "POSTGRES_DATABASE: $POSTGRES_DATABASE"
+  echo "POSTGRES_USER: $POSTGRES_USER"
+  echo "POSTGRES_PASSOWRD: $POSTGRES_PASSWORD"
+  echo "PGDATA: $PGDATA"
+  echo "PGDATA_VOLUME: $PGDATA_VOLUME"
+  echo "PGLOGS_VOLUME: $PGLOGS_VOLUME"
+
+}
+
+
+function start_staging_mysql_server() {
+
+  docker-compose -p $docker_project -f mysql_host.yml down --remove-orphans
+  docker-compose -p $docker_project -f mysql_host.yml up --build -d
+
+  #Wait for MySQL to come up
+  export WAITER_HOST=$MYSQL_HOST
+  export WAITER_PORT=$MYSQL_PORT
+  docker-compose -p $docker_project -f waiter.yml up --build
+  echo $separator
+  echo "Mysql Host is started..."
+  echo $separator
+
+  #Ensure the Postgres instance is up
+  export WAITER_HOST=$POSTGRES_HOST
+  export WAITER_PORT=$POSTGRES_PORT
+  docker-compose -p $docker_project -f waiter.yml up --build
+  echo $separator
+  echo "Postgres Host is started..."
+  echo $separator
+
+}
+
+function migrate_data_from_mysql_to_postgres() {
+
+  echo $separator
+  echo "Starting Mysql to Postgres Migration..."
+  echo $separator
+  docker-compose -p $docker_project -f mysql-to-postgres.yml down
+  docker-compose -p $docker_project -f mysql-to-postgres.yml up --build
+}
+
+
+function run_postgres_datatypes_conversion() {
+  echo $separator
+  echo "Starting Mysql to Postgres Datatype Conversion..."
+  echo $separator
+  docker-compose -p $docker_project -f convert.yml up --build
+}
+
+
+function clean() {
+  echo $separator
+  echo "Cleaning up..."
+  echo $separator
+
+  # Powerdown the containers (to remove them)
+  docker-compose -p $docker_project -f mysql-to-postgres.yml down --remove-orphans
+  docker-compose -p $docker_project -f convert.yml down --remove-orphans
+
+  # Cleanup any temporary images
+  IMAGE=$docker_project"_mysql-to-postgres"
+  echo "IMAGE: $IMAGE"
+  docker rmi $IMAGE
+  IMAGE=$docker_project"_convert"
+  docker rmi $IMAGE
+  docker rmi mysql:5.6 
+  docker rmi dimitri/pgloader:latest
+  IMAGE=$docker_project"_mysql_host"
+  docker rmi $IMAGE --force
+  IMAGE=$docker_project"_waiter"
+  docker rmi $IMAGE --force
+
+  # Cleanup any dangling volumes
+  docker volume rm $(docker volume ls -qf dangling=true)
+}
+
+clean
+start_staging_mysql_server
+#display_env
+migrate_data_from_mysql_to_postgres
+run_postgres_datatypes_conversion
+clean

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/mysql-to-postgres.env
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/mysql-to-postgres.env b/traffic_ops_db/pg-migration/mysql-to-postgres.env
new file mode 100644
index 0000000..086e68e
--- /dev/null
+++ b/traffic_ops_db/pg-migration/mysql-to-postgres.env
@@ -0,0 +1,43 @@
+#!/bin/bash
+#
+#  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 Ops Settings
+# The following configs should be configured to point to the 
+# Traffic Ops instances that is connected to the MySQL that 
+# you want to convert
+TO_SERVER=to_url
+TO_USER=(your_user)
+TO_PASSWORD=(your_password)
+
+# Staging Mysql 
+# These variables are for the "staging" Docker MySQL instance that is used
+# to load the Traffic Ops "dbdump" into.  ONLY change the MYSQL_HOST variable
+# Leave the other variables.
+MYSQL_HOST=( the_ip_address_running_this_migration )
+MYSQL_PORT=3306
+MYSQL_DATABASE=traffic_ops_db
+MYSQL_USER=to_user
+MYSQL_PASSWORD=twelve
+MYSQL_RANDOM_ROOT_PASSWORD=yes
+
+# New production Postgres Settings, these variables should be changed for the Postgres 
+# instance that will contain the existing MySQL data converted
+POSTGRES_HOST=( the_ip_address_running_this_migration )
+POSTGRES_PORT=5432
+# NOTE: The new database name for Traffic Ops
+POSTGRES_DATABASE=traffic_ops
+POSTGRES_USER=traffic_ops
+POSTGRES_PASSWORD=( your_new_postgres_password )
+PGDATA=/opt/postgresql/data/pgdata

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/mysql-to-postgres.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/mysql-to-postgres.sh b/traffic_ops_db/pg-migration/mysql-to-postgres.sh
new file mode 100755
index 0000000..7ab7013
--- /dev/null
+++ b/traffic_ops_db/pg-migration/mysql-to-postgres.sh
@@ -0,0 +1,65 @@
+#!/bin/bash
+#
+#  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.
+#
+# ------------------------------------------------------
+
+echo "Dumping Data from Traffic Ops Instance: $TO_SERVER" 
+output=/tmp/trafficops_init.sql
+[[ -n $output ]] && output="-o $output"
+
+cookiejar=/tmp/cookiejar
+cred=/tmp/cred.json
+
+echo "----------------------------------------"
+echo "Migrating Mysql data from:"
+echo "----------------------------------------"
+echo "MYSQL_HOST: $MYSQL_HOST"
+echo "MYSQL_USER: $MYSQL_USER"
+echo "MYSQL_DATABASE: $MYSQL_DATABASE"
+echo "----------------------------------------"
+
+echo "----------------------------------------"
+echo "To Postgres..."
+echo "----------------------------------------"
+echo "POSTGRES_HOST: $POSTGRES_HOST"
+echo "POSTGRES_USER: $POSTGRES_USER"
+echo "POSTGRES_DATABASE: $POSTGRES_DATABASE"
+echo "----------------------------------------"
+
+cat >$cred <<-CREDS
+	{ "u" : "$TO_USER", "p" : "$TO_PASSWORD" }
+CREDS
+
+curl -f -k -H "Accept: application/json" --cookie "$cookiejar" --cookie-jar "$cookiejar" -X POST --data @"$cred" "$TO_SERVER/api/1.2/user/login"  || exit 1
+curl $output -f -k -s --cookie "$cookiejar" -X GET "$TO_SERVER/dbdump"  || exit 1
+
+echo  "[client]" > /root/.my.cnf
+echo  "user=$MYSQL_USER" >> /root/.my.cnf 
+echo  "password=$MYSQL_PASSWORD" >> /root/.my.cnf 
+chmod 0600 /root/.my.cnf
+mysql -h $MYSQL_HOST $MYSQL_DATABASE < /tmp/trafficops_init.sql
+
+pgloader -v \
+	--cast 'type tinyint to smallint drop typemod' \
+	--cast 'type varchar to text drop typemod' \
+	--cast 'type double to numeric drop typemod' \
+	mysql://$MYSQL_USER:$MYSQL_PASSWORD@$MYSQL_HOST/$MYSQL_DATABASE \
+	postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST/$POSTGRES_DATABASE
+
+# For debugging
+#while true; do
+#    echo "Waiting.."
+#    sleep 3
+#done
+

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/mysql-to-postgres.yml
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/mysql-to-postgres.yml b/traffic_ops_db/pg-migration/mysql-to-postgres.yml
new file mode 100644
index 0000000..b5c99df
--- /dev/null
+++ b/traffic_ops_db/pg-migration/mysql-to-postgres.yml
@@ -0,0 +1,24 @@
+#
+#  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.
+#
+version: '2'
+
+services:
+  # dataimport reads data from an existing traffic_ops server running mysql thru the API
+  mysql-to-postgres:
+    build:
+        context: .
+        dockerfile: Dockerfile-mysql-to-postgres
+    restart: "no"
+    env_file:
+      - mysql-to-postgres.env

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/mysql/conf.d/mysql.cnf
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/mysql/conf.d/mysql.cnf b/traffic_ops_db/pg-migration/mysql/conf.d/mysql.cnf
new file mode 100755
index 0000000..c2c94fe
--- /dev/null
+++ b/traffic_ops_db/pg-migration/mysql/conf.d/mysql.cnf
@@ -0,0 +1,21 @@
+#
+#  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.
+#
+# This is custom config file attached from docker host
+
+[mysql]
+default_character_set = utf8
+
+[mysqld]
+character_set_server = utf8          # If you prefer utf8
+collation_server = utf8_general_ci

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/mysql_host.yml
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/mysql_host.yml b/traffic_ops_db/pg-migration/mysql_host.yml
new file mode 100644
index 0000000..fb02e3b
--- /dev/null
+++ b/traffic_ops_db/pg-migration/mysql_host.yml
@@ -0,0 +1,24 @@
+#
+#  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.
+#
+version: '2'
+
+services:
+  mysql_host:
+    build:
+      context: .
+      dockerfile: Dockerfile-mysql
+    env_file:
+      - mysql-to-postgres.env
+    ports:
+      - "3306:3306"

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/pgloader.yml
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/pgloader.yml b/traffic_ops_db/pg-migration/pgloader.yml
new file mode 100644
index 0000000..d9e3149
--- /dev/null
+++ b/traffic_ops_db/pg-migration/pgloader.yml
@@ -0,0 +1,23 @@
+#
+#  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.
+#
+version: '2'
+
+services:
+  # pgloader converts the data from mysql to postgres
+  pgloader:
+    build:
+      context: ..
+      dockerfile: pg-migration/Dockerfile-pgloader
+    env_file:
+      - mysql-to-postgres.env

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/postgres.yml
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/postgres.yml b/traffic_ops_db/pg-migration/postgres.yml
new file mode 100644
index 0000000..72a765e
--- /dev/null
+++ b/traffic_ops_db/pg-migration/postgres.yml
@@ -0,0 +1,34 @@
+#
+#  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.
+#
+version: '2'
+
+services:
+  db:
+    build:
+      context: ..
+      dockerfile: pg-migration/Dockerfile-postgres
+    env_file:
+      - mysql-to-postgres.env
+    ports:
+      - 5432:5432
+    volumes:
+      - ./pgdata:/opt/postgresql/data/pgdata
+      - ./postgres_logs:/var/log/postgresql
+    networks:
+      - default
+
+networks:
+  default:
+     driver: bridge
+

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/runconvert.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/runconvert.sh b/traffic_ops_db/pg-migration/runconvert.sh
new file mode 100755
index 0000000..59b1afb
--- /dev/null
+++ b/traffic_ops_db/pg-migration/runconvert.sh
@@ -0,0 +1,15 @@
+#!/bin/bash -x
+#
+#  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.
+# Load required conversion of booleans
+psql postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST/$POSTGRES_DATABASE < ./convert_bools.sql

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/runmysql.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/runmysql.sh b/traffic_ops_db/pg-migration/runmysql.sh
new file mode 100755
index 0000000..0c29dee
--- /dev/null
+++ b/traffic_ops_db/pg-migration/runmysql.sh
@@ -0,0 +1,16 @@
+#!/bin/bash -x
+#
+#  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.
+#
+
+docker-entrypoint.sh mysqld

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/runpgloader.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/runpgloader.sh b/traffic_ops_db/pg-migration/runpgloader.sh
new file mode 100755
index 0000000..f6a7d7d
--- /dev/null
+++ b/traffic_ops_db/pg-migration/runpgloader.sh
@@ -0,0 +1,24 @@
+#!/bin/bash -x
+#
+#  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.
+#
+
+pgloader -v \
+	--before create_tables.sql \
+	--cast 'type tinyint to smallint drop typemod' \
+	--cast 'type varchar to text drop typemod' \
+	--cast 'type double to numeric drop typemod' \
+        --with truncate \
+	mysql://$MYSQL_USER:$MYSQL_PASSWORD@$MYSQL_HOST/traffic_ops_db \
+	postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST/$POSTGRES_DATABASE
+exit 0

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/runwaiter.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/runwaiter.sh b/traffic_ops_db/pg-migration/runwaiter.sh
new file mode 100755
index 0000000..7cf2222
--- /dev/null
+++ b/traffic_ops_db/pg-migration/runwaiter.sh
@@ -0,0 +1,13 @@
+#!/bin/bash
+
+
+echo "WAITER_HOST: $WAITER_HOST"
+echo "WAITER_PORT: $WAITER_PORT"
+
+for c in "$WAITER_HOST $WAITER_PORT" ; do
+  while true; do
+     echo "Waiting 3 seconds for Host and Port: $c "
+     sleep 3
+     nc -z $c && break
+  done
+done

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/d20484de/traffic_ops_db/pg-migration/waiter.yml
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/waiter.yml b/traffic_ops_db/pg-migration/waiter.yml
new file mode 100644
index 0000000..2796737
--- /dev/null
+++ b/traffic_ops_db/pg-migration/waiter.yml
@@ -0,0 +1,24 @@
+#
+#  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.
+#
+version: '2'
+
+services:
+  # waits for a port to be available
+  waiter:
+    build:
+      context: ..
+      dockerfile: pg-migration/Dockerfile-waiter
+    environment:
+      - WAITER_HOST
+      - WAITER_PORT



[5/9] incubator-trafficcontrol git commit: added cleanup for the waiter container

Posted by fr...@apache.org.
added cleanup for the waiter container

(cherry picked from commit 72ca7cfce02b068068df5ee72e8d5bcb834c2d60)


Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/commit/5ccf06f6
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/tree/5ccf06f6
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/diff/5ccf06f6

Branch: refs/heads/2.0.x
Commit: 5ccf06f6389eb94b94eca8f64c25787c73565310
Parents: e0e5041
Author: Dewayne Richardson <de...@apache.org>
Authored: Sun May 14 08:09:24 2017 -0600
Committer: Eric Friedrich <fr...@apache.org>
Committed: Wed Jun 14 15:35:59 2017 -0400

----------------------------------------------------------------------
 traffic_ops_db/pg-migration/migrate.sh | 2 ++
 1 file changed, 2 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/5ccf06f6/traffic_ops_db/pg-migration/migrate.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/pg-migration/migrate.sh b/traffic_ops_db/pg-migration/migrate.sh
index f5b4388..3cb029d 100755
--- a/traffic_ops_db/pg-migration/migrate.sh
+++ b/traffic_ops_db/pg-migration/migrate.sh
@@ -107,6 +107,8 @@ function clean() {
   docker rmi $IMAGE --force
   IMAGE=$docker_project"_waiter"
   docker rmi $IMAGE --force
+  IMAGE=$IMAGE"_1"
+  docker rm $IMAGE
 
   # Cleanup any dangling volumes
   docker volume rm $(docker volume ls -qf dangling=true)


[7/9] incubator-trafficcontrol git commit: added installer for the Postgres Docker service-a

Posted by fr...@apache.org.
added installer for the Postgres Docker service-a

(cherry picked from commit e4872fdf24ab0dd464933e5866bd04848dabbf11)


Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/commit/5f6d364d
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/tree/5f6d364d
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/diff/5f6d364d

Branch: refs/heads/2.0.x
Commit: 5f6d364d1d2a953f3ceb32af49ec4a21063a6671
Parents: d20484d
Author: Dewayne Richardson <de...@apache.org>
Authored: Thu May 11 15:11:47 2017 -0600
Committer: Eric Friedrich <fr...@apache.org>
Committed: Wed Jun 14 15:35:59 2017 -0400

----------------------------------------------------------------------
 traffic_ops_db/bin/install_systemd_unit.sh    |  4 +++
 traffic_ops_db/systemd/traffic_ops_db.service | 30 ++++++++++++++++++++++
 2 files changed, 34 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/5f6d364d/traffic_ops_db/bin/install_systemd_unit.sh
----------------------------------------------------------------------
diff --git a/traffic_ops_db/bin/install_systemd_unit.sh b/traffic_ops_db/bin/install_systemd_unit.sh
index 321a101..454b3e2 100644
--- a/traffic_ops_db/bin/install_systemd_unit.sh
+++ b/traffic_ops_db/bin/install_systemd_unit.sh
@@ -14,3 +14,7 @@
 #  limitations under the License.
 #
 
+systemctl enable traffic_ops_db.service
+
+printf "\nNow you can start manually start the traffic_ops service with the command:\n"
+printf "systemctl start traffic_ops_db\n"

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/5f6d364d/traffic_ops_db/systemd/traffic_ops_db.service
----------------------------------------------------------------------
diff --git a/traffic_ops_db/systemd/traffic_ops_db.service b/traffic_ops_db/systemd/traffic_ops_db.service
new file mode 100644
index 0000000..31110e3
--- /dev/null
+++ b/traffic_ops_db/systemd/traffic_ops_db.service
@@ -0,0 +1,30 @@
+
+#
+#  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.
+#
+#-----------------------------------------
+# {{ ansible_managed }}
+#-----------------------------------------
+#
+[Unit]
+Description=Traffic Ops Postgres Docker Container
+Requires=docker.service
+After=docker.service
+
+[Service]
+Restart=always
+ExecStart=/usr/bin/docker-compose -p trafficops -f /opt/traffic_ops_db/docker/docker-compose.yml up
+ExecStop=/usr/bin/docker-compose -p trafficops -f /opt/traffic_ops_db/docker/docker-compose.yml stop
+
+[Install]
+WantedBy=default.target


[8/9] incubator-trafficcontrol git commit: added installer for the Postgres Docker service

Posted by fr...@apache.org.
added installer for the Postgres Docker service

(cherry picked from commit c0157f5374488cb194666e89e70819f09c537f5e)


Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/commit/e0e50416
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/tree/e0e50416
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/diff/e0e50416

Branch: refs/heads/2.0.x
Commit: e0e504165c26241f8e2ba17659d0738b9b5915d9
Parents: 5f6d364
Author: Dewayne Richardson <de...@apache.org>
Authored: Thu May 11 15:11:48 2017 -0600
Committer: Eric Friedrich <fr...@apache.org>
Committed: Wed Jun 14 15:35:59 2017 -0400

----------------------------------------------------------------------
 traffic_ops/app/db/convert_bools.sql            | 112 -----------------
 .../app/db/pg-migration/Dockerfile-convert      |  28 -----
 .../app/db/pg-migration/Dockerfile-mysql        |  26 ----
 .../pg-migration/Dockerfile-mysql-to-postgres   |  38 ------
 .../app/db/pg-migration/Dockerfile-pgloader     |  19 ---
 .../app/db/pg-migration/Dockerfile-postgres     |  29 -----
 .../app/db/pg-migration/Dockerfile-waiter       |  24 ----
 traffic_ops/app/db/pg-migration/README.md       |  16 ---
 traffic_ops/app/db/pg-migration/convert.yml     |  23 ----
 traffic_ops/app/db/pg-migration/migrate.sh      | 121 -------------------
 .../app/db/pg-migration/mysql-to-postgres.env   |  43 -------
 .../app/db/pg-migration/mysql-to-postgres.sh    |  65 ----------
 .../app/db/pg-migration/mysql-to-postgres.yml   |  24 ----
 .../app/db/pg-migration/mysql/conf.d/mysql.cnf  |  21 ----
 traffic_ops/app/db/pg-migration/mysql_host.yml  |  24 ----
 traffic_ops/app/db/pg-migration/pgloader.yml    |  23 ----
 traffic_ops/app/db/pg-migration/postgres.yml    |  34 ------
 traffic_ops/app/db/pg-migration/runconvert.sh   |  15 ---
 traffic_ops/app/db/pg-migration/runmysql.sh     |  16 ---
 traffic_ops/app/db/pg-migration/runpgloader.sh  |  24 ----
 traffic_ops/app/db/pg-migration/runwaiter.sh    |  29 -----
 .../app/db/pg-migration/start_postgres.sh       |  54 ---------
 traffic_ops/app/db/pg-migration/waiter.yml      |  24 ----
 traffic_ops/app/db/reset.sh                     |  16 ---
 traffic_ops/app/db/setup_migrations.sql         |  17 ---
 25 files changed, 865 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/convert_bools.sql
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/convert_bools.sql b/traffic_ops/app/db/convert_bools.sql
deleted file mode 100644
index 5835e6c..0000000
--- a/traffic_ops/app/db/convert_bools.sql
+++ /dev/null
@@ -1,112 +0,0 @@
--- Licensed to the Apache Software Foundation (ASF) under one
--- or more contributor license agreements.  See the NOTICE file
--- distributed with this work for additional information
--- regarding copyright ownership.  The ASF licenses this file
--- to you 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.
-
-ALTER TABLE cdn
-  ALTER COLUMN dnssec_enabled DROP DEFAULT,
-	ALTER COLUMN dnssec_enabled TYPE boolean
-		USING CASE WHEN dnssec_enabled = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN dnssec_enabled SET DEFAULT FALSE;
-
-ALTER TABLE deliveryservice
-  ALTER COLUMN active DROP DEFAULT,
-	ALTER COLUMN active TYPE boolean
-		USING CASE WHEN active = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN active SET DEFAULT FALSE;
-
-ALTER TABLE deliveryservice
-  ALTER COLUMN signed DROP DEFAULT,
-	ALTER COLUMN signed TYPE boolean
-		USING CASE WHEN signed = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN signed SET DEFAULT FALSE;
-
-ALTER TABLE deliveryservice
-  ALTER COLUMN ipv6_routing_enabled DROP DEFAULT,
-	ALTER COLUMN ipv6_routing_enabled TYPE boolean
-		USING CASE WHEN ipv6_routing_enabled = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN ipv6_routing_enabled SET DEFAULT FALSE;
-
-ALTER TABLE deliveryservice
-  ALTER COLUMN multi_site_origin DROP DEFAULT,
-	ALTER COLUMN multi_site_origin TYPE boolean
-		USING CASE WHEN multi_site_origin = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN multi_site_origin SET DEFAULT FALSE;
-
-ALTER TABLE deliveryservice
-  ALTER COLUMN regional_geo_blocking DROP DEFAULT,
-	ALTER COLUMN regional_geo_blocking TYPE boolean
-		USING CASE WHEN regional_geo_blocking = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN regional_geo_blocking SET DEFAULT FALSE;
-
-ALTER TABLE deliveryservice
-  ALTER COLUMN logs_enabled DROP DEFAULT,
-	ALTER COLUMN logs_enabled TYPE boolean
-		USING CASE WHEN logs_enabled = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN logs_enabled SET DEFAULT FALSE;
-
-  ALTER TABLE goose_db_version
-  ALTER COLUMN is_applied DROP DEFAULT,
-	ALTER COLUMN is_applied TYPE boolean
-		USING CASE WHEN is_applied = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN is_applied SET DEFAULT FALSE;
-
-ALTER TABLE parameter
-  ALTER COLUMN secure DROP DEFAULT,
-	ALTER COLUMN secure TYPE boolean
-		USING CASE WHEN secure = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN secure SET DEFAULT FALSE;
-
-ALTER TABLE server
-  ALTER COLUMN upd_pending DROP DEFAULT,
-	ALTER COLUMN upd_pending TYPE boolean
-		USING CASE WHEN upd_pending = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN upd_pending SET DEFAULT FALSE;
-
-ALTER TABLE tm_user
-  ALTER COLUMN new_user DROP DEFAULT,
-	ALTER COLUMN new_user TYPE boolean
-		USING CASE WHEN new_user = 1 THEN TRUE
-			ELSE FALSE
-			END,
-  ALTER COLUMN new_user SET DEFAULT FALSE;
-
-ALTER TABLE to_extension
-  ALTER COLUMN isactive DROP DEFAULT,
-	ALTER COLUMN isactive TYPE boolean
-		USING CASE WHEN isactive = 1 THEN TRUE
-			ELSE FALSE
-			END,
-    ALTER COLUMN isactive SET DEFAULT FALSE;

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/Dockerfile-convert
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/Dockerfile-convert b/traffic_ops/app/db/pg-migration/Dockerfile-convert
deleted file mode 100644
index 941912f..0000000
--- a/traffic_ops/app/db/pg-migration/Dockerfile-convert
+++ /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.
-#
-FROM dewrich/postgres:latest
-
-MAINTAINER Dan Kirkwood
-
-# Postgres Access
-ENV POSTGRES_HOST=$POSTGRES_HOST
-ENV POSTGRES_PORT=$POSTGRES_PORT
-ENV POSTGRES_DATABASE=$POSTGRES_DATABASE
-ENV POSTGRES_PASSWORD=$POSTGRES_PASSWORD
-
-RUN apt-get update 
-ADD pg-migration/runconvert.sh .
-ADD convert_bools.sql .
-
-CMD ./runconvert.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/Dockerfile-mysql
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/Dockerfile-mysql b/traffic_ops/app/db/pg-migration/Dockerfile-mysql
deleted file mode 100644
index 0b3d0df..0000000
--- a/traffic_ops/app/db/pg-migration/Dockerfile-mysql
+++ /dev/null
@@ -1,26 +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.
-#
-FROM mysql:5.6
-
-MAINTAINER Dan Kirkwood
-
-# Mysql Access
-ENV MYSQL_HOST=$MYSQL_HOST
-ENV MYSQL_PORT=$MYSQL_PORT
-ENV MYSQL_PASSWORD=$MYSQL_PASSWORD
-ENV MYSQL_DATABASE=$MYSQL_DATABASE
-
-EXPOSE 3306
-ADD runmysql.sh /
-CMD /runmysql.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/Dockerfile-mysql-to-postgres
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/Dockerfile-mysql-to-postgres b/traffic_ops/app/db/pg-migration/Dockerfile-mysql-to-postgres
deleted file mode 100644
index b1da689..0000000
--- a/traffic_ops/app/db/pg-migration/Dockerfile-mysql-to-postgres
+++ /dev/null
@@ -1,38 +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.
-#
-FROM dimitri/pgloader:latest
-MAINTAINER Dan Kirkwood <da...@apache.org>
-
-# Traffic Ops Access
-ENV TO_SERVER=$TO_SERVER
-ENV TO_USER=$TO_USER
-ENV TO_PASSWORD=$TO_PASSWORD
-
-# Mysql Access
-ENV MYSQL_HOST=$MYSQL_HOST
-ENV MYSQL_PORT=$MYSQL_PORT
-ENV MYSQL_PASSWORD=$MYSQL_PASSWORD
-ENV MYSQL_DATABASE=$MYSQL_DATABASE
-
-# Postgres Access
-ENV POSTGRES_HOST=$POSTGRES_HOST
-ENV POSTGRES_PORT=$POSTGRES_PORT
-ENV POSTGRES_DATABASE=$POSTGRES_DATABASE
-ENV POSTGRES_PASSWORD=$POSTGRES_PASSWORD
-
-# install the tools for getting data
-RUN apt-get -y update && apt-get -y install curl mysql-client
-
-ADD mysql-to-postgres.sh .
-CMD ./mysql-to-postgres.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/Dockerfile-pgloader
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/Dockerfile-pgloader b/traffic_ops/app/db/pg-migration/Dockerfile-pgloader
deleted file mode 100644
index fec7f97..0000000
--- a/traffic_ops/app/db/pg-migration/Dockerfile-pgloader
+++ /dev/null
@@ -1,19 +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.
-#
-FROM dimitri/pgloader:latest
-MAINTAINER Dan Kirkwood <da...@apache.org>
-
-ADD pg-migration/runpgloader.sh .
-ADD create_tables.sql .
-CMD ./runpgloader.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/Dockerfile-postgres
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/Dockerfile-postgres b/traffic_ops/app/db/pg-migration/Dockerfile-postgres
deleted file mode 100644
index 6f3c634..0000000
--- a/traffic_ops/app/db/pg-migration/Dockerfile-postgres
+++ /dev/null
@@ -1,29 +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.
-#
-FROM dewrich/postgres:latest
-
-MAINTAINER Dan Kirkwood
-
-# Postgres Access
-ENV POSTGRES_HOST=$POSTGRES_HOST
-ENV POSTGRES_PORT=$POSTGRES_PORT
-ENV POSTGRES_DATABASE=$POSTGRES_DATABASE
-ENV POSTGRES_PASSWORD=$POSTGRES_PASSWORD
-
-# Adjust PostgreSQL configuration so that remote connections to the
-# database are possible.
-RUN echo "host all  all    0.0.0.0/0  md5" >> $PGDATA/pg_hba.conf
-RUN echo "listen_addresses='*'" >> $PGDATA/postgresql.conf
-
-EXPOSE "5432:5432"

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/Dockerfile-waiter
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/Dockerfile-waiter b/traffic_ops/app/db/pg-migration/Dockerfile-waiter
deleted file mode 100644
index 0531c71..0000000
--- a/traffic_ops/app/db/pg-migration/Dockerfile-waiter
+++ /dev/null
@@ -1,24 +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.
-#
-FROM dimitri/pgloader:latest
-
-MAINTAINER Dewayne Richardson
-
-RUN apt-get -y update && apt-get -y install netcat
-
-ENV WAITER_HOST=$WAITER_HOST
-ENV WAITER_PORT=$WAITER_PORT
-
-ADD pg-migration/runwaiter.sh .
-CMD ./runwaiter.sh

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/README.md
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/README.md b/traffic_ops/app/db/pg-migration/README.md
deleted file mode 100644
index 8ff9d67..0000000
--- a/traffic_ops/app/db/pg-migration/README.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# Converts existing mysql `traffic_ops` database to postgres
-
-* Requires a recent ( 1.12 ) version of `docker-engine` and `docker-compose`.
-
-* Modify the mysql-to-postgres.env file for the parameters in your Migration 
-
-* Ensure that your new Postgres service is running (local or remote)
-
-* Run your Postgres Instance and configure mysql-to-postgres.env accordingly
-
-* A sample Postgres Docker container has been provided for testing
-  * `sh start_postgres.sh`
-  
-
-* Run the Mysql to Postgres Migration Docker flow
-  * `sh migrate.sh`

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/convert.yml
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/convert.yml b/traffic_ops/app/db/pg-migration/convert.yml
deleted file mode 100644
index fb130e9..0000000
--- a/traffic_ops/app/db/pg-migration/convert.yml
+++ /dev/null
@@ -1,23 +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.
-#
-version: '2'
-
-services:
-  # convert runs necessary post-import conversion(s) in postgres
-  convert:
-    build:
-      context: ..
-      dockerfile: pg-migration/Dockerfile-convert
-    env_file:
-      - mysql-to-postgres.env

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/migrate.sh
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/migrate.sh b/traffic_ops/app/db/pg-migration/migrate.sh
deleted file mode 100755
index 46ce9a1..0000000
--- a/traffic_ops/app/db/pg-migration/migrate.sh
+++ /dev/null
@@ -1,121 +0,0 @@
-#!/bin/bash 
-#
-#  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.
-#
-
-. mysql-to-postgres.env
-
-#Traffic Ops Settings
-# The following configs should be configured to point to the 
-# Traffic Ops instances that is connected to the MySQL that 
-# you want to convert
-separator="---------------------------------------"
-docker_project="pgmigration"
-
-function display_env() {
-
-  echo "TO_SERVER: $TO_SERVER"
-  echo "TO_USER: $TO_USER"
-  echo "TO_PASSWORD: $TO_PASSWORD"
-  echo "MYSQL_HOST: $MYSQL_HOST"
-  echo "MYSQL_PORT: $MYSQL_PORT"
-  echo "MYSQL_DATABASE: $MYSQL_DATABASE"
-  echo "MYSQL_USER: $MYSQL_USER"
-  echo "MYSQL_PASSWORD: $MYSQL_PASSWORD"
-
-  echo "POSTGRES_HOST: $POSTGRES_HOST"
-  echo "POSTGRES_PORT: $POSTGRES_PORT"
-  echo "POSTGRES_DATABASE: $POSTGRES_DATABASE"
-  echo "POSTGRES_USER: $POSTGRES_USER"
-  echo "POSTGRES_PASSOWRD: $POSTGRES_PASSWORD"
-  echo "PGDATA: $PGDATA"
-  echo "PGDATA_VOLUME: $PGDATA_VOLUME"
-  echo "PGLOGS_VOLUME: $PGLOGS_VOLUME"
-
-}
-
-
-function start_staging_mysql_server() {
-
-  docker-compose -p $docker_project -f mysql_host.yml down --remove-orphans
-  docker-compose -p $docker_project -f mysql_host.yml up --build -d
-
-  #Wait for MySQL to come up
-  export WAITER_HOST=$MYSQL_HOST
-  export WAITER_PORT=$MYSQL_PORT
-  docker-compose -p $docker_project -f waiter.yml up --build
-  echo $separator
-  echo "Mysql Host is started..."
-  echo $separator
-
-  #Ensure the Postgres instance is up
-  export WAITER_HOST=$POSTGRES_HOST
-  export WAITER_PORT=$POSTGRES_PORT
-  docker-compose -p $docker_project -f waiter.yml up --build
-  echo $separator
-  echo "Postgres Host is started..."
-  echo $separator
-
-}
-
-function migrate_data_from_mysql_to_postgres() {
-
-  echo $separator
-  echo "Starting Mysql to Postgres Migration..."
-  echo $separator
-  docker-compose -p $docker_project -f mysql-to-postgres.yml down
-  docker-compose -p $docker_project -f mysql-to-postgres.yml up --build
-}
-
-
-function run_postgres_datatypes_conversion() {
-  echo $separator
-  echo "Starting Mysql to Postgres Datatype Conversion..."
-  echo $separator
-  docker-compose -p $docker_project -f convert.yml up --build
-}
-
-
-function clean() {
-  echo $separator
-  echo "Cleaning up..."
-  echo $separator
-
-  # Powerdown the containers (to remove them)
-  docker-compose -p $docker_project -f waiter.yml down --remove-orphans
-  docker-compose -p $docker_project -f mysql-to-postgres.yml down --remove-orphans
-  docker-compose -p $docker_project -f convert.yml down --remove-orphans
-
-  # Cleanup any temporary images
-  IMAGE=$docker_project"_mysql-to-postgres"
-  echo "IMAGE: $IMAGE"
-  docker rmi $IMAGE
-  IMAGE=$docker_project"_convert"
-  docker rmi $IMAGE
-  docker rmi mysql:5.6 
-  docker rmi dimitri/pgloader:latest
-  IMAGE=$docker_project"_mysql_host"
-  docker rmi $IMAGE --force
-  IMAGE=$docker_project"_waiter"
-  docker rmi $IMAGE --force
-
-  # Cleanup any dangling volumes
-  docker volume rm $(docker volume ls -qf dangling=true)
-}
-
-clean
-start_staging_mysql_server
-#display_env
-migrate_data_from_mysql_to_postgres
-run_postgres_datatypes_conversion
-clean

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/mysql-to-postgres.env
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/mysql-to-postgres.env b/traffic_ops/app/db/pg-migration/mysql-to-postgres.env
deleted file mode 100644
index 086e68e..0000000
--- a/traffic_ops/app/db/pg-migration/mysql-to-postgres.env
+++ /dev/null
@@ -1,43 +0,0 @@
-#!/bin/bash
-#
-#  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 Ops Settings
-# The following configs should be configured to point to the 
-# Traffic Ops instances that is connected to the MySQL that 
-# you want to convert
-TO_SERVER=to_url
-TO_USER=(your_user)
-TO_PASSWORD=(your_password)
-
-# Staging Mysql 
-# These variables are for the "staging" Docker MySQL instance that is used
-# to load the Traffic Ops "dbdump" into.  ONLY change the MYSQL_HOST variable
-# Leave the other variables.
-MYSQL_HOST=( the_ip_address_running_this_migration )
-MYSQL_PORT=3306
-MYSQL_DATABASE=traffic_ops_db
-MYSQL_USER=to_user
-MYSQL_PASSWORD=twelve
-MYSQL_RANDOM_ROOT_PASSWORD=yes
-
-# New production Postgres Settings, these variables should be changed for the Postgres 
-# instance that will contain the existing MySQL data converted
-POSTGRES_HOST=( the_ip_address_running_this_migration )
-POSTGRES_PORT=5432
-# NOTE: The new database name for Traffic Ops
-POSTGRES_DATABASE=traffic_ops
-POSTGRES_USER=traffic_ops
-POSTGRES_PASSWORD=( your_new_postgres_password )
-PGDATA=/opt/postgresql/data/pgdata

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/mysql-to-postgres.sh
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/mysql-to-postgres.sh b/traffic_ops/app/db/pg-migration/mysql-to-postgres.sh
deleted file mode 100755
index 7ab7013..0000000
--- a/traffic_ops/app/db/pg-migration/mysql-to-postgres.sh
+++ /dev/null
@@ -1,65 +0,0 @@
-#!/bin/bash
-#
-#  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.
-#
-# ------------------------------------------------------
-
-echo "Dumping Data from Traffic Ops Instance: $TO_SERVER" 
-output=/tmp/trafficops_init.sql
-[[ -n $output ]] && output="-o $output"
-
-cookiejar=/tmp/cookiejar
-cred=/tmp/cred.json
-
-echo "----------------------------------------"
-echo "Migrating Mysql data from:"
-echo "----------------------------------------"
-echo "MYSQL_HOST: $MYSQL_HOST"
-echo "MYSQL_USER: $MYSQL_USER"
-echo "MYSQL_DATABASE: $MYSQL_DATABASE"
-echo "----------------------------------------"
-
-echo "----------------------------------------"
-echo "To Postgres..."
-echo "----------------------------------------"
-echo "POSTGRES_HOST: $POSTGRES_HOST"
-echo "POSTGRES_USER: $POSTGRES_USER"
-echo "POSTGRES_DATABASE: $POSTGRES_DATABASE"
-echo "----------------------------------------"
-
-cat >$cred <<-CREDS
-	{ "u" : "$TO_USER", "p" : "$TO_PASSWORD" }
-CREDS
-
-curl -f -k -H "Accept: application/json" --cookie "$cookiejar" --cookie-jar "$cookiejar" -X POST --data @"$cred" "$TO_SERVER/api/1.2/user/login"  || exit 1
-curl $output -f -k -s --cookie "$cookiejar" -X GET "$TO_SERVER/dbdump"  || exit 1
-
-echo  "[client]" > /root/.my.cnf
-echo  "user=$MYSQL_USER" >> /root/.my.cnf 
-echo  "password=$MYSQL_PASSWORD" >> /root/.my.cnf 
-chmod 0600 /root/.my.cnf
-mysql -h $MYSQL_HOST $MYSQL_DATABASE < /tmp/trafficops_init.sql
-
-pgloader -v \
-	--cast 'type tinyint to smallint drop typemod' \
-	--cast 'type varchar to text drop typemod' \
-	--cast 'type double to numeric drop typemod' \
-	mysql://$MYSQL_USER:$MYSQL_PASSWORD@$MYSQL_HOST/$MYSQL_DATABASE \
-	postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST/$POSTGRES_DATABASE
-
-# For debugging
-#while true; do
-#    echo "Waiting.."
-#    sleep 3
-#done
-

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/mysql-to-postgres.yml
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/mysql-to-postgres.yml b/traffic_ops/app/db/pg-migration/mysql-to-postgres.yml
deleted file mode 100644
index b5c99df..0000000
--- a/traffic_ops/app/db/pg-migration/mysql-to-postgres.yml
+++ /dev/null
@@ -1,24 +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.
-#
-version: '2'
-
-services:
-  # dataimport reads data from an existing traffic_ops server running mysql thru the API
-  mysql-to-postgres:
-    build:
-        context: .
-        dockerfile: Dockerfile-mysql-to-postgres
-    restart: "no"
-    env_file:
-      - mysql-to-postgres.env

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/mysql/conf.d/mysql.cnf
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/mysql/conf.d/mysql.cnf b/traffic_ops/app/db/pg-migration/mysql/conf.d/mysql.cnf
deleted file mode 100755
index c2c94fe..0000000
--- a/traffic_ops/app/db/pg-migration/mysql/conf.d/mysql.cnf
+++ /dev/null
@@ -1,21 +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.
-#
-# This is custom config file attached from docker host
-
-[mysql]
-default_character_set = utf8
-
-[mysqld]
-character_set_server = utf8          # If you prefer utf8
-collation_server = utf8_general_ci

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/mysql_host.yml
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/mysql_host.yml b/traffic_ops/app/db/pg-migration/mysql_host.yml
deleted file mode 100644
index fb02e3b..0000000
--- a/traffic_ops/app/db/pg-migration/mysql_host.yml
+++ /dev/null
@@ -1,24 +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.
-#
-version: '2'
-
-services:
-  mysql_host:
-    build:
-      context: .
-      dockerfile: Dockerfile-mysql
-    env_file:
-      - mysql-to-postgres.env
-    ports:
-      - "3306:3306"

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/pgloader.yml
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/pgloader.yml b/traffic_ops/app/db/pg-migration/pgloader.yml
deleted file mode 100644
index d9e3149..0000000
--- a/traffic_ops/app/db/pg-migration/pgloader.yml
+++ /dev/null
@@ -1,23 +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.
-#
-version: '2'
-
-services:
-  # pgloader converts the data from mysql to postgres
-  pgloader:
-    build:
-      context: ..
-      dockerfile: pg-migration/Dockerfile-pgloader
-    env_file:
-      - mysql-to-postgres.env

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/postgres.yml
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/postgres.yml b/traffic_ops/app/db/pg-migration/postgres.yml
deleted file mode 100644
index 72a765e..0000000
--- a/traffic_ops/app/db/pg-migration/postgres.yml
+++ /dev/null
@@ -1,34 +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.
-#
-version: '2'
-
-services:
-  db:
-    build:
-      context: ..
-      dockerfile: pg-migration/Dockerfile-postgres
-    env_file:
-      - mysql-to-postgres.env
-    ports:
-      - 5432:5432
-    volumes:
-      - ./pgdata:/opt/postgresql/data/pgdata
-      - ./postgres_logs:/var/log/postgresql
-    networks:
-      - default
-
-networks:
-  default:
-     driver: bridge
-

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/runconvert.sh
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/runconvert.sh b/traffic_ops/app/db/pg-migration/runconvert.sh
deleted file mode 100755
index 59b1afb..0000000
--- a/traffic_ops/app/db/pg-migration/runconvert.sh
+++ /dev/null
@@ -1,15 +0,0 @@
-#!/bin/bash -x
-#
-#  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.
-# Load required conversion of booleans
-psql postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST/$POSTGRES_DATABASE < ./convert_bools.sql

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/runmysql.sh
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/runmysql.sh b/traffic_ops/app/db/pg-migration/runmysql.sh
deleted file mode 100755
index 0c29dee..0000000
--- a/traffic_ops/app/db/pg-migration/runmysql.sh
+++ /dev/null
@@ -1,16 +0,0 @@
-#!/bin/bash -x
-#
-#  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.
-#
-
-docker-entrypoint.sh mysqld

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/runpgloader.sh
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/runpgloader.sh b/traffic_ops/app/db/pg-migration/runpgloader.sh
deleted file mode 100755
index f6a7d7d..0000000
--- a/traffic_ops/app/db/pg-migration/runpgloader.sh
+++ /dev/null
@@ -1,24 +0,0 @@
-#!/bin/bash -x
-#
-#  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.
-#
-
-pgloader -v \
-	--before create_tables.sql \
-	--cast 'type tinyint to smallint drop typemod' \
-	--cast 'type varchar to text drop typemod' \
-	--cast 'type double to numeric drop typemod' \
-        --with truncate \
-	mysql://$MYSQL_USER:$MYSQL_PASSWORD@$MYSQL_HOST/traffic_ops_db \
-	postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST/$POSTGRES_DATABASE
-exit 0

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/runwaiter.sh
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/runwaiter.sh b/traffic_ops/app/db/pg-migration/runwaiter.sh
deleted file mode 100644
index f5609c9..0000000
--- a/traffic_ops/app/db/pg-migration/runwaiter.sh
+++ /dev/null
@@ -1,29 +0,0 @@
-#!/bin/bash
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership.  The ASF licenses this file
-# to you 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.
-
-
-echo "WAITER_HOST: $WAITER_HOST"
-echo "WAITER_PORT: $WAITER_PORT"
-
-for c in "$WAITER_HOST $WAITER_PORT" ; do
-  while true; do
-     echo "Waiting 3 seconds for Host and Port: $c "
-     sleep 3
-     nc -z $c && break
-  done
-done

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/start_postgres.sh
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/start_postgres.sh b/traffic_ops/app/db/pg-migration/start_postgres.sh
deleted file mode 100755
index f89d1f4..0000000
--- a/traffic_ops/app/db/pg-migration/start_postgres.sh
+++ /dev/null
@@ -1,54 +0,0 @@
-#!/bin/bash 
-#
-#  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.
-#
-
-. mysql-to-postgres.env
-
-#Traffic Ops Settings
-# The following configs should be configured to point to the 
-# Traffic Ops instances that is connected to the MySQL that 
-# you want to convert
-separator="---------------------------------------"
-
-function display_env() {
-
-  echo "TO_SERVER: $TO_SERVER"
-  echo "TO_USER: $TO_USER"
-  echo "TO_PASSWORD: $TO_PASSWORD"
-  echo "MYSQL_HOST: $MYSQL_HOST"
-  echo "MYSQL_PORT: $MYSQL_PORT"
-  echo "MYSQL_DATABASE: $MYSQL_DATABASE"
-  echo "MYSQL_USER: $MYSQL_USER"
-  echo "MYSQL_PASSWORD: $MYSQL_PASSWORD"
-
-  echo "POSTGRES_HOST: $POSTGRES_HOST"
-  echo "POSTGRES_PORT: $POSTGRES_PORT"
-  echo "POSTGRES_DATABASE: $POSTGRES_DATABASE"
-  echo "POSTGRES_USER: $POSTGRES_USER"
-  echo "POSTGRES_PASSOWRD: $POSTGRES_PASSWORD"
-  echo "PGDATA: $PGDATA"
-  echo "PGDATA_VOLUME: $PGDATA_VOLUME"
-  echo "PGLOGS_VOLUME: $PGLOGS_VOLUME"
-
-}
-
-function start_staging_postgres_server() {
-
-  docker-compose -v -p trafficops -f postgres.yml down
-
-  docker-compose -p trafficops -f postgres.yml up  -d --build
-
-}
-
-start_staging_postgres_server

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/pg-migration/waiter.yml
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/pg-migration/waiter.yml b/traffic_ops/app/db/pg-migration/waiter.yml
deleted file mode 100644
index 2796737..0000000
--- a/traffic_ops/app/db/pg-migration/waiter.yml
+++ /dev/null
@@ -1,24 +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.
-#
-version: '2'
-
-services:
-  # waits for a port to be available
-  waiter:
-    build:
-      context: ..
-      dockerfile: pg-migration/Dockerfile-waiter
-    environment:
-      - WAITER_HOST
-      - WAITER_PORT

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/reset.sh
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/reset.sh b/traffic_ops/app/db/reset.sh
deleted file mode 100644
index 751fad7..0000000
--- a/traffic_ops/app/db/reset.sh
+++ /dev/null
@@ -1,16 +0,0 @@
-mysql twelve_monkeys_test -utwelve_monkeys -ptwelve -e 'drop database twelve_monkeys_test; create database twelve_monkeys_test;';
-#
-#
-# 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.
-#
-mysql twelve_monkeys_test -utwelve_monkeys -ptwelve < create_tables.sql

http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/e0e50416/traffic_ops/app/db/setup_migrations.sql
----------------------------------------------------------------------
diff --git a/traffic_ops/app/db/setup_migrations.sql b/traffic_ops/app/db/setup_migrations.sql
deleted file mode 100644
index 84ff88d..0000000
--- a/traffic_ops/app/db/setup_migrations.sql
+++ /dev/null
@@ -1,17 +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.
-*/
-
-insert ignore into role (name, description, priv_level) values ('migrations','Migrations User', 20);
-insert ignore into tm_user (username,role,full_name) values ('migration',(select id from role where name='migrations'),'migrations user - DO NOT REMOVE');