add 1.8.0 docs
diff --git a/docs/1.8.0/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png b/docs/1.8.0/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png
new file mode 100644
index 0000000..9998e81
--- /dev/null
+++ b/docs/1.8.0/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png
Binary files differ
diff --git a/docs/1.8.0/_images/12m.png b/docs/1.8.0/_images/12m.png
new file mode 100644
index 0000000..36ce934
--- /dev/null
+++ b/docs/1.8.0/_images/12m.png
Binary files differ
diff --git a/docs/1.8.0/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png b/docs/1.8.0/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png
new file mode 100644
index 0000000..1a6ad24
--- /dev/null
+++ b/docs/1.8.0/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png
Binary files differ
diff --git a/docs/1.8.0/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png b/docs/1.8.0/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png
new file mode 100644
index 0000000..96fddab
--- /dev/null
+++ b/docs/1.8.0/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png
Binary files differ
diff --git a/docs/1.8.0/_images/D22DCAA3-18CC-48F4-965B-5312993F9820.png b/docs/1.8.0/_images/D22DCAA3-18CC-48F4-965B-5312993F9820.png
new file mode 100644
index 0000000..59d5b8e
--- /dev/null
+++ b/docs/1.8.0/_images/D22DCAA3-18CC-48F4-965B-5312993F9820.png
Binary files differ
diff --git a/docs/1.8.0/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png b/docs/1.8.0/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png
new file mode 100644
index 0000000..6d05b19
--- /dev/null
+++ b/docs/1.8.0/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png
Binary files differ
diff --git a/docs/1.8.0/_images/bad.png b/docs/1.8.0/_images/bad.png
new file mode 100644
index 0000000..485e3da
--- /dev/null
+++ b/docs/1.8.0/_images/bad.png
Binary files differ
diff --git a/docs/1.8.0/_images/bad1.png b/docs/1.8.0/_images/bad1.png
new file mode 100644
index 0000000..485e3da
--- /dev/null
+++ b/docs/1.8.0/_images/bad1.png
Binary files differ
diff --git a/docs/1.8.0/_images/cache_groups_1.png b/docs/1.8.0/_images/cache_groups_1.png
new file mode 100644
index 0000000..d03d320
--- /dev/null
+++ b/docs/1.8.0/_images/cache_groups_1.png
Binary files differ
diff --git a/docs/1.8.0/_images/clock-black.png b/docs/1.8.0/_images/clock-black.png
new file mode 100644
index 0000000..4783c01
--- /dev/null
+++ b/docs/1.8.0/_images/clock-black.png
Binary files differ
diff --git a/docs/1.8.0/_images/dnssec01.png b/docs/1.8.0/_images/dnssec01.png
new file mode 100644
index 0000000..044538f
--- /dev/null
+++ b/docs/1.8.0/_images/dnssec01.png
Binary files differ
diff --git a/docs/1.8.0/_images/dnssec02.png b/docs/1.8.0/_images/dnssec02.png
new file mode 100644
index 0000000..82fa75a
--- /dev/null
+++ b/docs/1.8.0/_images/dnssec02.png
Binary files differ
diff --git a/docs/1.8.0/_images/dnssec03.png b/docs/1.8.0/_images/dnssec03.png
new file mode 100644
index 0000000..1fc3cce
--- /dev/null
+++ b/docs/1.8.0/_images/dnssec03.png
Binary files differ
diff --git a/docs/1.8.0/_images/dnssec04.png b/docs/1.8.0/_images/dnssec04.png
new file mode 100644
index 0000000..f9b8d32
--- /dev/null
+++ b/docs/1.8.0/_images/dnssec04.png
Binary files differ
diff --git a/docs/1.8.0/_images/federation01.png b/docs/1.8.0/_images/federation01.png
new file mode 100644
index 0000000..bbbd924
--- /dev/null
+++ b/docs/1.8.0/_images/federation01.png
Binary files differ
diff --git a/docs/1.8.0/_images/federation02.png b/docs/1.8.0/_images/federation02.png
new file mode 100644
index 0000000..9db970e
--- /dev/null
+++ b/docs/1.8.0/_images/federation02.png
Binary files differ
diff --git a/docs/1.8.0/_images/federation03.png b/docs/1.8.0/_images/federation03.png
new file mode 100644
index 0000000..abd52d2
--- /dev/null
+++ b/docs/1.8.0/_images/federation03.png
Binary files differ
diff --git a/docs/1.8.0/_images/federation04.png b/docs/1.8.0/_images/federation04.png
new file mode 100644
index 0000000..dd5a812
--- /dev/null
+++ b/docs/1.8.0/_images/federation04.png
Binary files differ
diff --git a/docs/1.8.0/_images/fwda.png b/docs/1.8.0/_images/fwda.png
new file mode 100644
index 0000000..ba63bee
--- /dev/null
+++ b/docs/1.8.0/_images/fwda.png
Binary files differ
diff --git a/docs/1.8.0/_images/fwda1.png b/docs/1.8.0/_images/fwda1.png
new file mode 100644
index 0000000..ba63bee
--- /dev/null
+++ b/docs/1.8.0/_images/fwda1.png
Binary files differ
diff --git a/docs/1.8.0/_images/good.png b/docs/1.8.0/_images/good.png
new file mode 100644
index 0000000..84d96cd
--- /dev/null
+++ b/docs/1.8.0/_images/good.png
Binary files differ
diff --git a/docs/1.8.0/_images/good1.png b/docs/1.8.0/_images/good1.png
new file mode 100644
index 0000000..84d96cd
--- /dev/null
+++ b/docs/1.8.0/_images/good1.png
Binary files differ
diff --git a/docs/1.8.0/_images/graph.png b/docs/1.8.0/_images/graph.png
new file mode 100644
index 0000000..ea0b4c5
--- /dev/null
+++ b/docs/1.8.0/_images/graph.png
Binary files differ
diff --git a/docs/1.8.0/_images/info.png b/docs/1.8.0/_images/info.png
new file mode 100644
index 0000000..5680f06
--- /dev/null
+++ b/docs/1.8.0/_images/info.png
Binary files differ
diff --git a/docs/1.8.0/_images/mso-enable.png b/docs/1.8.0/_images/mso-enable.png
new file mode 100644
index 0000000..9932de1
--- /dev/null
+++ b/docs/1.8.0/_images/mso-enable.png
Binary files differ
diff --git a/docs/1.8.0/_images/mso-rank.png b/docs/1.8.0/_images/mso-rank.png
new file mode 100644
index 0000000..de80ac5
--- /dev/null
+++ b/docs/1.8.0/_images/mso-rank.png
Binary files differ
diff --git a/docs/1.8.0/_images/regionalgeo01.png b/docs/1.8.0/_images/regionalgeo01.png
new file mode 100644
index 0000000..0443a17
--- /dev/null
+++ b/docs/1.8.0/_images/regionalgeo01.png
Binary files differ
diff --git a/docs/1.8.0/_images/regionalgeo02.png b/docs/1.8.0/_images/regionalgeo02.png
new file mode 100644
index 0000000..5530920
--- /dev/null
+++ b/docs/1.8.0/_images/regionalgeo02.png
Binary files differ
diff --git a/docs/1.8.0/_images/regionalgeo03.png b/docs/1.8.0/_images/regionalgeo03.png
new file mode 100644
index 0000000..ce2676b
--- /dev/null
+++ b/docs/1.8.0/_images/regionalgeo03.png
Binary files differ
diff --git a/docs/1.8.0/_images/steering01.png b/docs/1.8.0/_images/steering01.png
new file mode 100644
index 0000000..1515011
--- /dev/null
+++ b/docs/1.8.0/_images/steering01.png
Binary files differ
diff --git a/docs/1.8.0/_images/steering02.png b/docs/1.8.0/_images/steering02.png
new file mode 100644
index 0000000..c2fc22c
--- /dev/null
+++ b/docs/1.8.0/_images/steering02.png
Binary files differ
diff --git a/docs/1.8.0/_images/steering03.png b/docs/1.8.0/_images/steering03.png
new file mode 100644
index 0000000..f4b110d
--- /dev/null
+++ b/docs/1.8.0/_images/steering03.png
Binary files differ
diff --git a/docs/1.8.0/_images/steering04.png b/docs/1.8.0/_images/steering04.png
new file mode 100644
index 0000000..0ab962b
--- /dev/null
+++ b/docs/1.8.0/_images/steering04.png
Binary files differ
diff --git a/docs/1.8.0/_images/traffic_control_overview_3.png b/docs/1.8.0/_images/traffic_control_overview_3.png
new file mode 100644
index 0000000..594983b
--- /dev/null
+++ b/docs/1.8.0/_images/traffic_control_overview_3.png
Binary files differ
diff --git a/docs/1.8.0/_sources/admin/index.txt b/docs/1.8.0/_sources/admin/index.txt
new file mode 100644
index 0000000..e92f5e2
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/index.txt
@@ -0,0 +1,48 @@
+.. 
+.. 
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+.. 
+..     http://www.apache.org/licenses/LICENSE-2.0
+.. 
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+.. 
+
+Administrator's Guide
+*********************
+
+Traffic Control is distributed in source form for the developer, but also as a binary package. This guide details how to install and configure a Traffic Control CDN using the binary packages, as well as how to perform common operations running a CDN.
+
+When installing a complete CDN from scratch, a sample recommended order is:
+
+1. Traffic Ops
+2. Traffic Vault (Riak)
+3. Apache Traffic Server Mid-Tier Caches
+4. Apache Traffic Server Edge Caches
+5. Traffic Monitor
+6. Traffic Router
+7. Traffic Stats
+8. Traffic Portal
+
+Once everything is installed, you will need to configure the servers to talk to each other. You will also need Origin server(s), which the Mid-Tier Cache(s) get content from. An Origin server is simply an HTTP(S) server which serves the content you wish to cache on the CDN.
+
+.. toctree::
+  :maxdepth: 3
+
+  traffic_ops_install.rst
+  traffic_ops_config.rst
+  traffic_ops_using.rst
+  traffic_ops_extensions.rst
+  traffic_portal.rst
+  traffic_monitor.rst
+  traffic_router.rst
+  traffic_stats.rst
+  traffic_server.rst
+  traffic_vault.rst
+  quick_howto/index.rst
+
diff --git a/docs/1.8.0/_sources/admin/quick_howto/dnssec.txt b/docs/1.8.0/_sources/admin/quick_howto/dnssec.txt
new file mode 100644
index 0000000..d336057
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/quick_howto/dnssec.txt
@@ -0,0 +1,72 @@
+.. 
+.. 
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+.. 
+..     http://www.apache.org/licenses/LICENSE-2.0
+.. 
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+.. 
+
+.. _rl-dnssec-qht:
+
+****************
+Configure DNSSEC
+****************
+
+.. Note:: In order for Traffic Ops to successfully store keys in Traffic Vault, at least one Riak Server needs to be configured in Traffic Ops. See the `Traffic Vault admin page <../traffic_vault.html>`_ for more information.
+
+.. Note:: Currently DNSSEC is only supported for DNS delivery services.
+
+1)  Go to Tools->Manage DNSSEC Keys choose a CDN and click Manage DNSSEC Keys
+
+.. image:: dnssec01.png
+	:scale: 100%
+	:align: center
+
+2)	Generate keys for a CDN by clicking Generate Keys then entering the following information: 
+	
+		-  Expiration in days for the Zone Signing Key (ZSK)
+		-  Expiration in days for the Key Signing Key (KSK)
+		-  Effective Date
+
+	Once the required information has been entered click on the 'Generate Keys' button.  
+
+	Depending upon the number of Delivery Services in the CDN, generating DNSSEC keys may take serveral seconds.
+
+.. image:: dnssec02.png
+	:scale: 100%
+	:align: center
+
+3)	In order for DNSSEC to work properly, the DS Record information needs to be added to the parent zone of the CDN's domain (e.g. If 	the CDN's domain is 'cdn.kabletown.net' the parent zone is 'kabletown.net'). 
+
+	If you control your parent zone you can enter this information yourself, otherwise you will need to work with your DNS team to get the DS Record added to the parent zone.
+
+.. image:: dnssec03.png
+	:scale: 70%
+	:align: center
+
+4)	Once DS Record information has been added to the parent zone, DNSSEC needs to be activated for the CDN so that Traffic Router will sign responses.  
+	
+	Click on Tools -> Manage DNSSEC Keys -> Choose your CDN -> On the Manage DNSSEC Keys page click the activate DNSSEC Keys button.  
+
+	This will add a 'dnssec.enabled = "true"' entry to CRConfig for the chosen CDN. 
+
+.. image:: dnssec04.png
+	:scale: 70%
+	:align: center
+
+5) DNSSEC should now be active on your CDN and Traffic Router should be signing responses.  
+	
+	A dig command with +dnssec added should show you the signed responses.  
+
+	``dig edge.cdn.kabletown.net. +dnssec``
+
+6)	When KSK expiration is approaching (default 365 days), it is necessary to manually generate a new KSK for the TLD (Top Level Domain) and add the DS Record to the parent zone.  In order to avoid signing errors, it is suggested that an effective date is chosen which allows time for the DS Record to be added to the parent zone before the new KSK becomes active.  
+
+	A new KSK can be generated by clicking the 'Regenerate KSK' button on the Manage DNSSEC Keys screen (see screenshot above). 
diff --git a/docs/1.8.0/_sources/admin/quick_howto/federations.txt b/docs/1.8.0/_sources/admin/quick_howto/federations.txt
new file mode 100644
index 0000000..a17122c
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/quick_howto/federations.txt
@@ -0,0 +1,135 @@
+.. 
+.. 
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+.. 
+..     http://www.apache.org/licenses/LICENSE-2.0
+.. 
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+.. 
+
+.. _rl-federations-qht:
+
+*********************
+Configure Federations
+*********************
+
+1)  Create a user with a federations role (Misc -> Users -> Add User).  This user will have the ability to perform the following actions: 
+		
+		- Edit the federation
+		- Delete the federation
+		- Add IPV4 resolvers
+		- Add IPV6 resolvers
+
+.. image:: federation01.png
+	:scale: 100%
+	:align: center
+
+2) 	As a user with admin priveleges, create a Federation Mapping by going to Delivery Services -> Federations and then clicking 'Add Federation Mapping'
+
+3)	Choose the Delivery Service for the federation to be mapped to and assign it to the Federation User; click Add.
+
+.. image:: federation02.png
+	:scale: 100%
+	:align: center
+
+4) 	After the Federation is added, Traffic Ops will display the Federation.  
+
+	Changes can be made at this time or the Federation can be deleted.  Notice that no resolvers have been added to the fedeation yet.  This can only be done by the federation user created in step 1. 
+
+	If no further action is necessary, the Close button will close the window and display the list of all Federations. 
+
+.. image:: federation03.png
+	:scale: 100%
+	:align: center
+
+	
+**The Federation user can now add resolvers to the Federation Mapping in Traffic Ops.**
+
+5)	The federation user logs to traffic ops and stores the mojolicious cookie.  The mojolicious cookie can be obtained manually using the debug tools on a web browser or via curl.
+
+	Example::
+
+		$ curl -i -XPOST "http://localhost:3000/api/1.1/user/login" -H "Content-Type: application/json" -d '{ "u": "federation_user1", "p": "password" }'
+
+		HTTP/1.1 200 OK
+		Date: Wed, 02 Dec 2015 21:12:06 GMT
+		Content-Length: 65
+		Access-Control-Allow-Credentials: true
+		Content-Type: application/json
+		Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
+		Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1MTI2LCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---06b4f870d809d82a91433e92eae8320875c3e8b0; expires=Thu, 03 Dec 2015 01:12:06 GMT; path=/; HttpOnly
+		Server: Mojolicious (Perl)
+		Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
+		Cache-Control: no-cache, no-store, max-age=0, must-revalidate
+		Connection: keep-alive
+		Access-Control-Allow-Origin: http://localhost:8080
+
+		{"alerts":[{"level":"success","text":"Successfully logged in."}]}
+
+6) The federation user sends a request to Traffic Ops to add IPV4 and/or IPV6 resolvers
+	
+
+	Example::
+
+		$ curl -ki -H "Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1MTI2LCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---06b4f870d809d82a91433e92eae8320875c3e8b0;" -XPUT 'http://localhost:3000/api/1.2/federations' -d '
+			{"federations": [ 
+				{   "deliveryService": "images-c1", 
+					"mappings": 
+						{ "resolve4": [ "8.8.8.8/32", "8.8.4.4/32" ],
+						  "resolve6": ["2001:4860:4860::8888/128", "2001:4860:4860::8844"]
+						} 
+				} 
+			  ] 
+			}'
+
+		HTTP/1.1 200 OK
+		Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1OTQyLCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---b42be0749415cefd1d14e1a91bb214845b4de556; expires=Thu, 03 Dec 2015 01:25:42 GMT; path=/; HttpOnly
+		Server: Mojolicious (Perl)
+		Date: Wed, 02 Dec 2015 21:25:42 GMT
+		Content-Length: 74
+		Access-Control-Allow-Credentials: true
+		Content-Type: application/json
+		Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
+		Cache-Control: no-cache, no-store, max-age=0, must-revalidate
+		Access-Control-Allow-Origin: http://localhost:8080
+		Connection: keep-alive
+		Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
+
+		{"response":"federation_user1 successfully created federation resolvers."}
+
+7) The resolvers added by the federation user will now visible in Traffic Ops.
+
+.. image:: federation04.png
+	:scale: 100%
+	:align: center
+
+8) Any requests made from a client that resolves to one of the federation resolvers will now be given a CNAME from Traffic Router.
+
+	Example::
+
+		$ dig @tr.kabletown.net edge.images-c1.kabletown.net
+
+		; <<>> DiG 9.7.3-RedHat-9.7.3-2.el6 <<>> @tr.kabletown.net edge.images-c1.kabletown.net
+		; (1 server found)
+		;; global options: +cmd
+		;; Got answer:
+		;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45110
+		;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
+		;; WARNING: recursion requested but not available
+
+		;; QUESTION SECTION:
+		;edge.images-c1.kabletown.net.	IN A
+
+		;; ANSWER SECTION:
+		edge.images-c1.kabletown.net.	30 IN CNAME img.mega-cdn.net.
+
+		;; Query time: 9 msec
+		;; SERVER: 10.10.10.10#53(10.10.10.10)
+		;; WHEN: Wed Dec  2 22:05:26 2015
+		;; MSG SIZE  rcvd: 84
\ No newline at end of file
diff --git a/docs/1.8.0/_sources/admin/quick_howto/index.txt b/docs/1.8.0/_sources/admin/quick_howto/index.txt
new file mode 100644
index 0000000..96f098f
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/quick_howto/index.txt
@@ -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.
+..
+
+Quick How To Guides
+*******************
+
+Traffic Control is a complicated system, and documenting it is not trivial. Sometimes a picture says more than a thousand words, so here are some screen shot based tutorials on how to use some of the more involved features.
+
+.. toctree::
+  :maxdepth: 3
+
+  multi_site.rst
+  dnssec.rst
+  federations.rst
+  regionalgeo.rst
+  steering.rst
diff --git a/docs/1.8.0/_sources/admin/quick_howto/multi_site.txt b/docs/1.8.0/_sources/admin/quick_howto/multi_site.txt
new file mode 100644
index 0000000..32b5436
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/quick_howto/multi_site.txt
@@ -0,0 +1,95 @@
+.. 
+.. 
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+.. 
+..     http://www.apache.org/licenses/LICENSE-2.0
+.. 
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+.. 
+
+.. _rl-multi-site-origin-qht:
+
+***************************
+Configure Multi Site Origin
+***************************
+
+1) Create "cachegroups" for the origin locations, and assign the appropriate parent-child relationship between the mid cg's and org cgs (click the image to see full size):
+
+.. image:: C5C4CD22-949A-48FD-8976-C673083E2177.png
+	:scale: 100%
+	:align: center
+
+2) Create a profile to assign to each of the origins:
+
+.. image:: 19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png
+	:scale: 100%
+	:align: center
+
+3) Create server entries for the origination vips:
+
+.. image:: D28614AA-9758-45ED-9EFD-3A284FC4218E.png
+	:scale: 100%
+	:align: center
+
+4) Check the multi-site check box in the delivery service screen and make sure that Content Routing Type is set to HTTP_LIVE_NATL:
+
+.. image:: mso-enable.png
+	:scale: 100%
+	:align: center
+
+5) Assign the org servers to the delivery service that will have the multi site feature:
+
+.. image:: 066CEF4F-C1A3-4A89-8B52-4F72B0531367.png
+	:scale: 100%
+	:align: center
+
+.. Note:: “Origin Server Base URL” uniqueness: In order to enable MID caches to distinguish delivery services by different MSO algorithms while performing parent failover, it requires that “Origin Server Base URL” (OFQDN) for each MSO enabled delivery service is unique unless the exceptions listed afterwards. This means that the OFQDN of a MSO enabled delivery service should be different with the OFQDNs of any other delivery service, regardless of whether they are MSO enabled or not. The exceptions are: 
+       1) If there are multiple CDNs created on the same Traffic Ops, delivery services across different CDNs may have the same OFQDN configured.
+       2) If several delivery services in the same CDN have the same MSO algorithm configured, they may share the same OFQDN.
+       3) If delivery services are assigned with different MID cache groups respectively, they can share the same OFQDN.
+
+6) Select an option from the "Multi Site Origin Algorithm" drop-down list. Four MSO algorithms are supported:
+
++------------------+--------------------------------------------------------------------------------------------------------------------+
+|     Option       |                                                            Description                                             |
++==================+====================================================================================================================+
+| Consistent hash  | Origin server selection is based on the consistent hash of requested URLs.                                         |
++------------------+--------------------------------------------------------------------------------------------------------------------+
+| Primary/back     | Round robin selection does not occur. The first origin server is selected unless it fails.                         |
+|                  | If the first fails, the second and other following origin servers will be tried by order.                          |
+|                  | Order is defined by 2 factors - if the origin server's cachegroup is configured as the                             |
+|                  | parent cachegroup for the mid, then this server will be used as the primary. The same rules                        |
+|                  | apply for secondary parents, in order.  Within the cachegroups, the rank parameter will sort                       |
+|                  | order further. If no parents are defined at the mid, then only rank is considered.                                 |  
++------------------+--------------------------------------------------------------------------------------------------------------------+
+| Strict           | MID caches serve requests strictly in turn. For example: origin server 1 serves the first request,                 |
+| round-robin      | origin server 2 serves the second request, and so on.                                                              |
++------------------+--------------------------------------------------------------------------------------------------------------------+
+| IP based         | MID cache goes through the origin server list in a round robin-based on the IP address of EDGE cache.              |
+| round-robin      |                                                                                                                    |
++------------------+--------------------------------------------------------------------------------------------------------------------+
+
+7) Optionally, there are two configuration options that can set the order of the origins used if "Primary/backup" is selected for "Multi Site Origin Algorithm". By creating location-based cachegroups and assigning the origin servers accordingly and defining these cachegroups as parents for specific mids, location-based primary/secondary selection can be made.   If primary/secondary selection should be the same for all mids, then a new parameter “rank” should be configured for each origin server profile. Origin servers with lower values of rank have higher ranking in the origin server list on MID caches, e.g. OS with rank of "2" precedes OS with the rank of "5". For any OS, if rank value is not defined in its profile, its rank value will default to “1”.  In the event that both location based cachegroups are used alongside rank, sorting will be by cachegroup first and rank second.  In this way it is possible to have specific backup servers for use at specific locations.
+
+.. image:: mso-rank.png
+	:scale: 60%
+	:align: center
+
+8) Assign the parent.config location parameter to the MID profile:
+
+.. image:: D22DCAA3-18CC-48F4-965B-5312993F9820.png
+	:scale: 100%
+	:align: center
+
+
+9) Configure the mid hdr_rewrite on the delivery service, example: ::
+
+	cond %{REMAP_PSEUDO_HOOK} __RETURN__ set-config proxy.config.http.parent_origin.dead_server_retry_enabled 1 __RETURN__ set-config proxy.config.http.parent_origin.simple_retry_enabled 1 __RETURN__ set-config proxy.config.http.parent_origin.simple_retry_response_codes "400,404,412" __RETURN__ set-config proxy.config.http.parent_origin.dead_server_retry_response_codes "502,503" __RETURN__ set-config proxy.config.http.connect_attempts_timeout 2 __RETURN__ set-config proxy.config.http.connect_attempts_max_retries 2 __RETURN__ set-config proxy.config.http.connect_attempts_max_retries_dead_server 1 __RETURN__ set-config proxy.config.http.transaction_active_timeout_in 5 [L] __RETURN__
+
+10) Turn on parent_proxy_routing in the MID profile.
diff --git a/docs/1.8.0/_sources/admin/quick_howto/regionalgeo.txt b/docs/1.8.0/_sources/admin/quick_howto/regionalgeo.txt
new file mode 100644
index 0000000..a903c8a
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/quick_howto/regionalgeo.txt
@@ -0,0 +1,109 @@
+..
+..
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+..
+..     http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+..
+
+.. _rl-regionalgeo-qht:
+
+**************************************
+Configure Regional Geo-blocking (RGB)
+**************************************
+
+.. Note:: RGB is only supported for HTTP delivery services.
+
+1)	Prepare RGB configuration file
+
+RGB uses a configuration file in JSON format to define regional geo-blocking rules for delivery services. The file needs to be put on an HTTP server accessible to Traffic Router. An example of the JSON is as follows::
+
+    {
+    "deliveryServices":
+        [
+            {
+                "deliveryServiceId": "hls-live",
+                "urlRegex": ".*live4\\.m3u8",
+                "geoLocation": {"includePostalCode":["N0H", "L9V", "L9W"]},
+                "redirectUrl": "http://third-party.com/blacked_out.html"
+            },
+            {
+                "deliveryServiceId": "hls-live",
+                "urlRegex": ".*live5\\.m3u8",
+                "ipWhiteList": [185.68.71.9/22","142.232.0.79/24"],
+                "geoLocation": {"excludePostalCode":["N0H", "L9V"]},
+                "redirectUrl": "/live5_low_bitrate.m3u8"
+            }
+        ]
+    }
+
+* The value of "deliveryServiceId" shall be equal to the “XML ID” field of the intended delivery service defined on Traffic Ops.
+
+* “urlRegex” is to match request URLs. The URLs matching the regex are applicable to the rule.
+
+* “geoLocation” currently supports “includePostalCode” and “excludePostalCode” attribute. When “includePostalCode” attribute is used, only the clients whose FSAs are in the “includePostalCode” list are able to view the content represented by “urlRegex”. When “excludePostalCode” is used, any client whose FSA are not in the “excludePostalCode” list are allowed to view the content. “includePostalCode” and “excludePostalCode” are mutually exclusive in one rule. (FSA: Forward Sortation Area, first three postal characters of Canadian postal codes)
+
+* “redirectUrl” is the URL that will be responded to the blocked clients. Without a domain name in the URL, the URL will still be served in the same delivery service. Thus Traffic Router will redirect the client to a chosen cache server assigned to the delivery service. If the URL includes a domain name, Traffic Router simply redirects the client to the defined URL. In the later case, the redirect URL must not match the “urlRegex” part to avoid HTTP 302 loop on Traffic Router.
+
+* “ipWhiteList” is an optional element. It includes a list of CIDR (Classless Inter-Domain Routing) blocks indicating the IPv4 subnets that are allowed by the rule. If this list exists and the value is not empty, client IP will be matched against the CIDR list, and if there is any match, the request will be allowed and no postal code matching logic is needed. If there is no match in the white list, postal code matching logic will be processed further.
+
+
+2)	Add RGB parameters on Traffic Ops
+
+The two new parameters in following table are required to be added into CRConfig.json:
+
+* "regional_geoblocking.polling.url": the HTTP URL of RGB configuration file. Traffic Router will fetch the file from this URL.
+* "regional_geoblocking.polling.interval": the interval that Traffic Router polls the RGB configuration file.
+
+.. image:: regionalgeo01.png
+	:scale: 100%
+	:align: center
+
+3)	Enable RGB for a delivery service
+
+.. image:: regionalgeo02.png
+	:scale: 100%
+	:align: center
+
+4)	Make configuration effective
+
+Go to Tools->Snapshot CRConfig, perform “Diff CRConfig” and click "Write CRConfig".
+
+.. image:: regionalgeo03.png
+	:scale: 70%
+	:align: center
+
+5)	Traffic Router access log with RGB
+
+RGB extends the field of "rtype" and adds a new field "rgb" in Traffic Router access.log to help to monitor the working of this feature.
+
+For "rtype", RGALT indicates that a request is redirected to an alternate URL by RGB; RGDENY indicates that a request is denied by RGB because there is no matching rule in JSON for this request.
+
+For "rgb", when RGB is enabled, it will be non-empty with following format::
+
+    {FSA}:{allowed/disallowed}:{include/exclude postal}:{fallback config/current config}:{allowed by whitelist/otherwise}
+
+
+* {FSA}: It is the client’s FSA part of its postal code, which is retrieved from geo-location database. If FSA is empty, dash (“-“) is filled in.
+* {allowed/disallowed}: This flag shows if a request is allowed or disallowed by RGB (1 for yes, and 0 for no).
+* {include/exclude postal}: It shows that when a rule in JSON is matched for a request, it is an include or exclude list of postal codes (i.e. FSAs). “I” for include, and “X” for exclude. If no rule matches, dash (“-“) is filled in.
+* {fallback config/current config}: when TR fails to parse an RGB JSON, TR will handle requests with latest valid JSON configuration, but will set {fallback config} flag to 1. If the new JSON is valid, then the flag is set to 0.
+* {allowed by whitelist/otherwise}: If a request is allowed by whitelist, this flag is set to 1; for all other cases, it is 0.
+
+
+Example::
+
+    1446442214.685 qtype=HTTP chi=129.100.254.79 url="http://ccr.geo2.cdn.com/live5.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=GEO rloc="-" rdtl=- rerr="-" rgb="N6G:1:X:0:0" pssc=302 ttms=3 rurl=http://cent6-44.geo2.cdn.com/live5.m3u8 rh="-"
+
+    1446442219.181 qtype=HTTP chi=184.68.71.9 url="http://ccr.geo2.cdn.com/live5.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=RGALT rloc="-" rdtl=- rerr="-" rgb="-:0:X:0:0" pssc=302 ttms=3 rurl=http://cent6-44.geo2.cdn.com/low_bitrate.m3u8 rh="-"
+
+    1446445521.677 qtype=HTTP chi=24.114.29.79 url="http://ccr.geo2.cdn.com/live51.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=RGDENY rloc="-" rdtl=- rerr="-" rgb="L4S:0:-:0:0" pssc=520 ttms=3 rurl="-" rh="-"
+
+
diff --git a/docs/1.8.0/_sources/admin/quick_howto/steering.txt b/docs/1.8.0/_sources/admin/quick_howto/steering.txt
new file mode 100644
index 0000000..1060f29
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/quick_howto/steering.txt
@@ -0,0 +1,95 @@
+..
+..
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+..
+..     http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+..
+
+.. _rl-steering-qht:
+
+***********************************
+Configure Delivery Service Steering
+***********************************
+
+1)  Create two target delivery services in Traffic Ops.  They must both be HTTP delivery services that are part of the same CDN.
+
+.. image:: steering01.png
+	:scale: 100%
+	:align: center
+
+2) Create a delivery service with type STEERING in Traffic Ops.
+
+.. image:: steering02.png
+	:scale: 100%
+	:align: center
+
+3) Click the 'Manage Steering Assignments' button on the delivery service screen to assign targets.
+
+.. image:: steering03.png
+	:scale: 100%
+	:align: center
+
+4) Create a user with the role of Steering.
+
+.. image:: steering04.png
+	:scale: 100%
+	:align: center
+
+5) As the steering user, assign weights to target delivery services.  This will require logging in to Traffic Ops first via ``http://to.kabletown.net/api/1.2/user/login`` and storing the mojolicious cookie.
+
+	Sample cURL: ``curl -H "Cookie: mojolicious=xxxyyy" -XPUT "https://to.kabletown.net/internal/api/1.2/steering/steering-ds" -d @/tmp/steering.json``
+
+	Sample JSON body:
+
+::
+
+   {
+    "targets": [
+     {
+       "weight": "1000",
+       "deliveryService": "target-deliveryservice-1"
+     },
+     {
+       "weight": "9000",
+       "deliveryService": "target-deliveryservice-2"
+     }
+    ]
+   }
+
+6) If desired, the steering user can create filters for the target delivery services.
+
+	Sample cURL: ``curl -H "Cookie: mojolicious=xxxyyy" -XPUT "https://to.kabletown.net/internal/api/1.2/steering/steering-ds" -d @/tmp/steering.json``
+
+	Sample JSON body:
+
+::
+
+   {
+    "filters": [
+     {
+       "pattern": ".*\\gototarget1\\..*",
+       "deliveryService": "target-deliveryservice-1"
+     }
+    ],
+    "targets": [
+     {
+       "weight": "1000",
+       "deliveryService": "target-deliveryservice-1"
+     },
+     {
+       "weight": "9000",
+       "deliveryService": "target-deliveryservice-2"
+     }
+    ]
+   }
+
+7) Any requests to Traffic Router for the steering delivery service should now be routed to target delivery services based on configured weight.  Example: ``curl -Lvs http://tr.steering-ds.cdn.kabletown.net/foo``
+
diff --git a/docs/1.8.0/_sources/admin/traffic_monitor.txt b/docs/1.8.0/_sources/admin/traffic_monitor.txt
new file mode 100644
index 0000000..3a06e78
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_monitor.txt
@@ -0,0 +1,142 @@
+.. 
+.. 
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+.. 
+..     http://www.apache.org/licenses/LICENSE-2.0
+.. 
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+.. 
+
+******************************
+Traffic Monitor Administration
+******************************
+Installing Traffic Monitor
+==========================
+The following are requirements to ensure an accurate set up:
+
+* CentOS 6
+* 4 vCPUs
+* 8GB RAM
+* Successful install of Traffic Ops
+* Tomcat
+* Administrative access to the Traffic Ops
+* Physical address of the site
+* perl-JSON
+* perl-WWW-Curl
+
+1. Enter the Traffic Monitor server into Traffic Ops
+2. Make sure the FQDN of the Traffic Monitor is resolvable in DNS.
+3. Install Traffic Monitor and Perl mods: ``sudo yum -y install traffic_monitor perl-JSON perl-WWW-Curl``
+4. Take the config from Traffic Ops - run : ``sudo /opt/traffic_monitor/bin/traffic_monitor_config.pl``
+ 
+	Sample output: ::
+
+		traffic_mon # /opt/traffic_monitor/bin/traffic_monitor_config.pl https://traffic-ops.cdn.kabletown.net admin:password prompt
+		DEBUG: traffic_ops selected: https://traffic-ops.cdn.kabletown.net
+		DEBUG: traffic_ops login: admin:kl0tevax
+		DEBUG: Config write mode: prompt
+		DEBUG: Found profile from traffic_ops: RASCAL_CDN
+		DEBUG: Found CDN name from traffic_ops: kabletown_cdn
+		DEBUG: Found location for rascal-config.txt from traffic_ops: /opt/traffic_monitor/conf
+		WARN: Param not in traffic_ops: allow.config.edit                        description: Allow the running configuration to be edited through the UI                                                              Using default value of: false
+		WARN: Param not in traffic_ops: default.accessControlAllowOrigin         description: The value for the header: Access-Control-Allow-Origin for published jsons... should be narrowed down to TMs              Using default value of: *
+		WARN: Param not in traffic_ops: default.connection.timeout               description: Default connection time for all queries (cache, peers, TM)                                                               Using default value of: 2000
+		WARN: Param not in traffic_ops: hack.forceSystemExit                     description: Call System.exit on shutdown                                                                                             Using default value of: false
+		WARN: Param not in traffic_ops: hack.peerOptimistic                      description: The assumption of a caches availability when unknown by peers                                                            Using default value of: true
+		WARN: Param not in traffic_ops: hack.publishDsStates                     description: If true, the delivery service states will be included in the CrStates.json                                               Using default value of: true
+		WARN: Param not in traffic_ops: health.ds.interval                       description: The polling frequency for calculating the deliveryService states                                                         Using default value of: 1000
+		WARN: Param not in traffic_ops: health.ds.leniency                       description: The amount of time before the deliveryService disregards the last update from a non-responsive cache                     Using default value of: 30000
+		WARN: Param not in traffic_ops: health.event-count                       description: The number of historical events that will be kept                                                                        Using default value of: 200
+		WARN: Param not in traffic_ops: health.polling.interval                  description: The polling frequency for getting the states from caches                                                                 Using default value of: 5000
+		WARN: Param not in traffic_ops: health.startupMinCycles                  description: The number of query cycles that must be completed before this Traffic Monitor will start reporting                       Using default value of: 2
+		WARN: Param not in traffic_ops: health.timepad                           description: A delay between each separate cache query                                                                                Using default value of: 10
+		WARN: Param not in traffic_ops: peers.polling.interval                   description: Polling frequency for getting states from peer monitors                                                                  Using default value of: 5000
+		WARN: Param not in traffic_ops: peers.polling.url                        description: The url for current, unfiltered states from peer monitors                                                                Using default value of: http://${hostname}/publish/CrStates?raw
+		WARN: Param not in traffic_ops: peers.threadPool                         description: The number of threads given to the pool for querying peers                                                               Using default value of: 1
+		WARN: Param not in traffic_ops: tm.auth.url                              description: The url for the authentication form                                                                                      Using default value of: https://${tmHostname}/login
+		WARN: Param not in traffic_ops: tm.crConfig.json.polling.url             description: Url for the cr-config (json)                                                                                             Using default value of: https://${tmHostname}/CRConfig-Snapshots/${cdnName}/CRConfig.json
+		WARN: Param not in traffic_ops: tm.healthParams.polling.url              description: The url for the heath params (json)                                                                                      Using default value of: https://${tmHostname}/health/${cdnName}
+		WARN: Param not in traffic_ops: tm.polling.interval                      description: The polling frequency for getting updates from TM                                                                        Using default value of: 10000
+		DEBUG: allow.config.edit needed in config, but does not exist in config on disk.
+		DEBUG: cdnName value on disk () does not match value needed in config (kabletown_cdn).
+		DEBUG: default.accessControlAllowOrigin needed in config, but does not exist in config on disk.
+		DEBUG: default.connection.timeout needed in config, but does not exist in config on disk.
+		DEBUG: hack.forceSystemExit needed in config, but does not exist in config on disk.
+		DEBUG: hack.peerOptimistic needed in config, but does not exist in config on disk.
+		DEBUG: hack.publishDsStates needed in config, but does not exist in config on disk.
+		DEBUG: health.ds.interval needed in config, but does not exist in config on disk.
+		DEBUG: health.ds.leniency needed in config, but does not exist in config on disk.
+		DEBUG: health.startupMinCycles needed in config, but does not exist in config on disk.
+		DEBUG: health.timepad value on disk (20) does not match value needed in config (10).
+		DEBUG: peers.polling.interval needed in config, but does not exist in config on disk.
+		DEBUG: peers.threadPool needed in config, but does not exist in config on disk.
+		DEBUG: tm.auth.password value on disk () does not match value needed in config (kl0tevax).
+		DEBUG: tm.auth.username value on disk () does not match value needed in config (admin).
+		DEBUG: tm.hostname value on disk () does not match value needed in config (traffic-ops.cdn.kabletown.net).
+		DEBUG: Proposed traffic_monitor_config:
+		{
+		   "traffic_monitor_config":{
+		      "default.accessControlAllowOrigin":"*",
+		      "health.startupMinCycles":"2",
+		      "tm.auth.password":"kl0tevax",
+		      "tm.auth.url":"https://${tmHostname}/login",
+		      "tm.healthParams.polling.url":"https://${tmHostname}/health/${cdnName}",
+		      "allow.config.edit":"false",
+		      "tm.crConfig.json.polling.url":"https://${tmHostname}/CRConfig-Snapshots/${cdnName}/CRConfig.json",
+		      "tm.auth.username":"admin",
+		      "peers.polling.url":"http://${hostname}/publish/CrStates?raw",
+		      "health.timepad":"10",
+		      "hack.publishDsStates":"true",
+		      "default.connection.timeout":"2000",
+		      "health.ds.interval":"1000",
+		      "peers.polling.interval":"5000",
+		      "hack.forceSystemExit":"false",
+		      "health.ds.leniency":"30000",
+		      "cdnName":"kabletown_cdn",
+		      "peers.threadPool":"1",
+		      "tm.polling.interval":"10000",
+		      "health.polling.interval":"5000",
+		      "health.event-count":"200",
+		      "hack.peerOptimistic":"true",
+		      "tm.hostname":"traffic-ops.cdn.kabletown.net"
+		   }
+		}
+		----------------------------------------------
+		----OK to write this config to disk? (Y/n) [n]y
+		----------------------------------------------
+		----------------------------------------------
+		----OK to write this config to disk? (Y/n) [n]Y
+		----------------------------------------------
+		DEBUG: Writing /opt/traffic_monitor/conf/traffic_monitor_config.js
+		traffic_mon # 
+
+5. Start Tomcat: ``sudo service tomcat start`` ::
+
+
+    Using CATALINA_BASE: /opt/tomcat
+    Using CATALINA_HOME: /opt/tomcat
+    Using CATALINA_TMPDIR: /opt/tomcat/temp
+    Using JRE_HOME: /usr
+    Using CLASSPATH:/opt/tomcat/bin/bootstrap.jar
+    Using CATALINA_PID:/var/run/tomcat/tomcat.pid
+    Starting tomcat [ OK ]
+
+6. Verify Traffic Monitor is running by pointing your browser to port 80 on the Traffic Monitor host.
+
+Configuring Traffic Monitor
+===========================
+
+Configuration Overview
+----------------------
+Traffic Monitor is configured using its JSON configuration file, ``traffic_monitor_config.js``. Specify the URL, username, password, and CDN name for the instance of Traffic Ops for which this Traffic Monitor is a member, and start the software.  Once started with the correct configuration, Traffic Monitor downloads its configuration from Traffic Ops and begins polling caches. Once a configurable number of polling cycles completes, health protocol state is available via RESTful JSON endpoints.
+
+
+Troubleshooting and log files
+=============================
+Traffic Monitor log files are in ``/opt/traffic_monitor/var/log/``, and tomcat log files are in ``/opt/tomcat/logs/``.
diff --git a/docs/1.8.0/_sources/admin/traffic_ops_config.txt b/docs/1.8.0/_sources/admin/traffic_ops_config.txt
new file mode 100644
index 0000000..0ca57da
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_ops_config.txt
@@ -0,0 +1,186 @@
+.. 
+.. 
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+.. 
+..     http://www.apache.org/licenses/LICENSE-2.0
+.. 
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+.. 
+
+Configuring Traffic Ops
+%%%%%%%%%%%%%%%%%%%%%%%
+
+Follow the steps below to configure the newly installed Traffic Ops Instance.
+
+Installing the SSL Cert
+=======================
+By default, Traffic Ops runs as an SSL web server, and a certificate needs to be installed.  TBD.
+
+Content Delivery Networks
+=========================
+
+.. _rl-param-prof:
+
+Profile Parameters
+======================
+Many of the settings for the different servers in a Traffic Control CDN are controlled by parameters in the parameter view of Traffic Ops. Parameters are grouped in profiles and profiles are assigned to a server. For a typical cache there are hundreds of configuration settings to apply. The Traffic Ops parameter view contains the defined settings. To make life easier, Traffic Ops allows for duplication, comparison, import and export of Profiles. Traffic Ops also has a "Global profile" - the parameters in this profile are going to be applied to all servers in the Traffic Ops instance, or apply to Traffic Ops themselves. These parameters are:
+
+
+.. index::
+  Global Profile
+
++--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
+|           Name           |  Config file  |                                                                 Value                                                                 |
++==========================+===============+=======================================================================================================================================+
+| tm.url                   | global        | The URL where this Traffic Ops instance is being served from.                                                                         |
++--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
+| tm.toolname              | global        | The name of the Traffic Ops tool. Usually "Traffic Ops". Used in the About screen and in the comments headers of the files generated. |
++--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
+| tm.infourl               | global        | This is the "for more information go here" URL, which is visible in the About page.                                                   |
++--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
+| tm.logourl               | global        | This is the URL of the logo for Traffic Ops and can be relative if the logo is under traffic_ops/app/public.                          |
++--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
+| tm.instance_name         | global        | The name of the Traffic Ops instance. Can be used when multiple instances are active. Visible in the About page.                      |
++--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
+| tm.traffic_mon_fwd_proxy | global        | When collecting stats from Traffic Monitor, Traffic Ops uses this forward proxy to pull the stats through.                            |
+|                          |               | This can be any of the MID tier caches, or a forward cache specifically deployed for this purpose. Setting                            |
+|                          |               | this variable can significantly lighten the load on the Traffic Monitor system and it is recommended to                               |
+|                          |               | set this parameter on a production system.                                                                                            |
++--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
+| geolocation.polling.url  | CRConfig.json | The location to get the GeoLiteCity database from.                                                                                    |
++--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
+| geolocation6.polling.url | CRConfig.json | The location to get the IPv6 GeoLiteCity database from.                                                                               |
++--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
+
+These parameters should be set to reflect the local environment.
+
+
+After running the postinstall script, Traffic Ops has the following profiles pre-loaded:
+
++----------+-------------------------------------------------------------------------------------------------+
+|   Name   |                                           Description                                           |
++==========+=================================================================================================+
+| EDGE1    | The profile to be applied to the latest supported version of ATS, when running as an EDGE cache |
++----------+-------------------------------------------------------------------------------------------------+
+| TR1      | The profile to be applied to the latest version of Traffic Router                               |
++----------+-------------------------------------------------------------------------------------------------+
+| TM1      | The profile to be applied to the latest version of Traffic Monitor                              |
++----------+-------------------------------------------------------------------------------------------------+
+| MID1     | The profile to be applied to the latest supported version of ATS, when running as an MID cache  |
++----------+-------------------------------------------------------------------------------------------------+
+| RIAK_ALL | Riak profile for all CDNs to be applied to the Traffic Vault servers                            |
++----------+-------------------------------------------------------------------------------------------------+
+
+.. Note:: The Traffic Server profiles contain some information that is specific to the hardware being used (most notably the disk configuration), so some parameters will have to be changed to reflect your configuration. Future releases of Traffic Control will separate the hardware and software profiles so it is easier to "mix-and-match" different hardware configurations.
+
+Below is a list of cache parameters that are likely to need changes from the default profiles shipped with Traffic Ops:
+
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+|           Name           |    Config file    |                                                       Description                                                       |
++==========================+===================+=========================================================================================================================+
+| allow_ip                 | astats.config     | This is a comma separated  list of IPv4 CIDR blocks that will have access to the astats statistics on the caches.       |
+|                          |                   | The Traffic Monitor IP addresses have to be included in this, if they are using IPv4 to monitor the caches.             |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| allow_ip6                | astats.config     | This is a comma separated  list of IPv6 CIDR blocks that will have access to the astats statistics on the caches.       |
+|                          |                   | The Traffic Monitor IP addresses have to be included in this, if they are using IPv6 to monitor the caches.             |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| Drive_Prefix             | storage.config    | JvD/Jeff to supply blurb                                                                                                |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| Drive_Letters            | storage.config    | JvD/Jeff to supply blurb                                                                                                |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| purge_allow_ip           | ip_allow.config   | The IP address range that is allowed to execute the PURGE method on the caches (not related to :ref:`rl-purge`)         |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| health.threshold.loadavg | rascal.properties | The Unix load average at which Traffic Router will stop sending traffic to this cache                                   |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+| health.threshold.\\      | rascal.properties | The amount of bandwidth that Traffic Router will try to keep available on the cache.                                    |
+| availableBandwidthInKbps |                   | For example: "">1500000" means stop sending new traffic to this cache when traffic is at 8.5Gbps on a 10Gbps interface. |
++--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
+
+Below is a list of Traffic Server plugins that need to be configured in the parameter table:
+
++------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
+|       Name       |  Config file  |                     Description                      |                                                  Details                                                   |
++==================+===============+======================================================+============================================================================================================+
+| astats_over_http | package       | The package version for the astats_over_http plugin. | `astats_over_http <http://trafficcontrol.apache.org/downloads/index.html>`_                                  |
++------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
+| trafficserver    | package       | The package version for the trafficserver plugin.    | `trafficserver <http://trafficcontrol.apache.org/downloads/index.html>`_                                     |
++------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
+| regex_revalidate | plugin.config | The config to be used for regex_revalidate.          | `regex_revalidate <https://docs.trafficserver.apache.org/en/5.3.x/reference/plugins/regex_remap.en.html>`_ |
+|                  |               | For example: --config regex_revalidate.config        |                                                                                                            |
++------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
+| remap_stats      | plugin.config | The config to be used for remap_stats.               | `remap_stats <https://github.com/apache/trafficserver/tree/master/plugins/experimental/remap_stats>`_      |
+|                  |               | Value is left blank.                                 |                                                                                                            |
++------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
+
+
+Regions, Locations and Cache Groups
+===================================
+All servers have to have a `location`, which is their physical location. Each location is part of a `region`, and each region is part of a `division`. For Example, ``Denver`` could be a location in the ``Mile High`` region and that region could be part of the ``West`` division. Enter your divisions first in  `Misc->Divisions`, then enter the regions in `Misc->Regions`, referencing the divisions entered, and finally, enter the physical locations in `Misc->Locations`, referencing the regions entered. 
+
+All servers also have to be part of a `cache group`. A cache group is a logical grouping of caches, that don't have to be in the same physical location (in fact, usually a cache group is spread across minimally 2 physical Locations for redundancy purposes), but share geo coordinates for content routing purposes. JvD to add more.
+
+
+
+Configuring Content Purge
+=========================
+Content purge using ATS is not simple; there is no file system to delete files/directories from, and in large caches it can be hard to delete a simple regular expression from the cache. This is why Traffic Control uses the `Regex Revalidate Plugin <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_revalidate.en.html>`_ to purge content from the system. We don't actually remove the content, we have a check that gets run before each request on each cache to see if this request matches a list of regular expressions, and if it does, we force a revalidation to the origin, making the original content inaccessible. The regex_revalidate plugin will monitor it's config file, and will pick up changes to it without a `traffic_line -x` signal to ATS. Changes to this file need to be distributed to the highest tier (MID) caches in the CDN before they are distributed to the lower tiers, to prevent filling the lower tiers with the content that should be purged from the higher 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>`_
+
+
+
+
diff --git a/docs/1.8.0/_sources/admin/traffic_ops_extensions.txt b/docs/1.8.0/_sources/admin/traffic_ops_extensions.txt
new file mode 100644
index 0000000..4aceebb
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_ops_extensions.txt
@@ -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
+   
diff --git a/docs/1.8.0/_sources/admin/traffic_ops_install.txt b/docs/1.8.0/_sources/admin/traffic_ops_install.txt
new file mode 100644
index 0000000..ca49461
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_ops_install.txt
@@ -0,0 +1,381 @@
+.. 
+.. 
+.. 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``
diff --git a/docs/1.8.0/_sources/admin/traffic_ops_using.txt b/docs/1.8.0/_sources/admin/traffic_ops_using.txt
new file mode 100644
index 0000000..5b8525d
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_ops_using.txt
@@ -0,0 +1,1060 @@
+..
+..
+.. 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.                                |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| 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:`geolimit-failure-redirect-feature`                                                       |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| 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 bot 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]_        |
++--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| 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, ut 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_NATIONAL, 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 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.                                                                                                                                    |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.ttls.SOA                            | CRConfig.json          | The TTL the Traffic Router DNS Server will respond with on SOA records.                                                                                                                                   |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.ttls.AAAA                           | CRConfig.json          | The Time To Live (TTL) the Traffic Router DNS Server will respond with on AAAA records.                                                                                                                   |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.ttls.A                              | CRConfig.json          | The TTL the Traffic Router DNS Server will respond with on A records.                                                                                                                                     |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.ttls.DNSKEY                         | CRConfig.json          | The TTL the Traffic Router DNS Server will respond with on DNSKEY records.                                                                                                                                |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| tld.ttls.DS                             | CRConfig.json          | The TTL the Traffic Router DNS Server will respond with on DS records.                                                                                                                                    |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| api.port                                | server.xml             | The TCP port Traffic Router listens on for API (REST) access.                                                                                                                                             |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| api.cache-control.max-age               | CRConfig.json          | The value of the ``Cache-Control: max-age=`` header in the API responses of Traffic Router.                                                                                                               |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| api.auth.url                            | CRConfig.json          | The API authentication URL (https://${tmHostname}/api/1.1/user/login); ${tmHostname} is a search and replace token used by Traffic Router to construct the correct URL)                                   |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| consistent.dns.routing                  | CRConfig.json          | Control whether DNS Delivery Services use consistent hashing on the edge FQDN to select caches for answers. May improve performance if set to true; defaults to false                                     |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| dnssec.enabled                          | CRConfig.json          | Whether DNSSEC is enabled; this parameter is updated via the DNSSEC administration user interface.                                                                                                        |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| dnssec.allow.expired.keys               | CRConfig.json          | Allow Traffic Router to use expired DNSSEC keys to sign zones; default is true. This helps prevent DNSSEC related outages due to failed Traffic Control components or connectivity issues.                |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| dynamic.cache.primer.enabled            | CRConfig.json          | Allow Traffic Router to attempt to prime the dynamic zone cache; defaults to true                                                                                                                         |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| dynamic.cache.primer.limit              | CRConfig.json          | Limit the number of permutations to prime when dynamic zone cache priming is enabled; defaults to 500                                                                                                     |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| keystore.maintenance.interval           | CRConfig.json          | The interval in seconds which Traffic Router will check the keystore API for new DNSSEC keys                                                                                                              |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| keystore.api.url                        | CRConfig.json          | The keystore API URL (https://${tmHostname}/api/1.1/cdns/name/${cdnName}/dnsseckeys.json; ${tmHostname} and ${cdnName} are search and replace tokens used by Traffic Router to construct the correct URL) |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| keystore.fetch.timeout                  | CRConfig.json          | The timeout in milliseconds for requests to the keystore API                                                                                                                                              |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| keystore.fetch.retries                  | CRConfig.json          | The number of times Traffic Router will attempt to load keys before giving up; defaults to 5                                                                                                              |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| keystore.fetch.wait                     | CRConfig.json          | The number of milliseconds Traffic Router will wait before a retry                                                                                                                                        |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| signaturemanager.expiration.multiplier  | CRConfig.json          | Multiplier used in conjunction with a zone's maximum TTL to calculate DNSSEC signature durations; defaults to 5                                                                                           |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| zonemanager.threadpool.scale            | CRConfig.json          | Multiplier used to determine the number of cores to use for zone signing operations; defaults to 0.75                                                                                                     |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| zonemanager.cache.maintenance.interval  | CRConfig.json          | The interval in seconds which Traffic Router will check for zones that need to be resigned or if dynamic zones need to be expired from cache                                                              |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| zonemanager.dynamic.response.expiration | CRConfig.json          | A string (e.g.: 300s) that defines how long a dynamic zone                                                                                                                                                |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| DNSKEY.generation.multiplier            | CRConfig.json          | Used to deteremine when new keys need to be regenerated. Keys are regenerated if expiration is less than the generation multiplier * the TTL.  If the parameter does not exist, the default is 10.        |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| DNSKEY.effective.multiplier             | CRConfig.json          | Used when creating an effective date for a new key set.  New keys are generated with an effective date of old key expiration - (effective multiplier * TTL).  Default is 2.                               |
++-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+
+
+..   index::
+  HOST_REGEXP
+  PATH_REGEXP
+  HEADER_REGEXP
+  Delivery Service regexp
+
+.. _rl-ds-regexp:
+
+Delivery Service Regexp
++++++++++++++++++++++++
+This table defines how requests are matched to the delivery service. There are 3 type of entries possible here:
+
++---------------+----------------------------------------------------------------------+--------------+-----------+
+|      Name     |                             Description                              |   DS Type    |   Status  |
++===============+======================================================================+==============+===========+
+| HOST_REGEXP   | This is the regular expresion to match the host part of the URL.     | DNS and HTTP | Supported |
++---------------+----------------------------------------------------------------------+--------------+-----------+
+| PATH_REGEXP   | This is the regular expresion to match the path part of the URL.     | HTTP         | Beta      |
++---------------+----------------------------------------------------------------------+--------------+-----------+
+| HEADER_REGEXP | This is the regular expresion to match on any header in the request. | HTTP         | Beta      |
++---------------+----------------------------------------------------------------------+--------------+-----------+
+
+The **Order** entry defines the order in which the regular expressions get evaluated. To support ``CNAMES`` from domains outside of the Traffic Control top level DNS domain, enter multiple ``HOST_REGEXP`` lines.
+
+Example:
+  Example foo.
+
+.. Note:: In most cases is is sufficient to have just one entry in this table that has a ``HOST_REGEXP`` Type, and Order ``0``. For the *movies* delivery service in the Kabletown CDN, the entry is simply single ``HOST_REGEXP`` set to ``.*\.movies\..*``. This will match every url that has a hostname that ends with ``movies.cdn1.kabletown.net``, since ``cdn1.kabletown.net`` is the Kabletown CDN's DNS domain.
+
+.. index::
+  Static DNS Entries
+
+.. _rl-static-dns:
+
+Static DNS Entries
+++++++++++++++++++
+Static DNS entries allow you to create other names *under* the delivery service domain. You can enter any valid hostname, and create a CNAME, A or AAAA record for it by clicking the **Static DNS** button at the bottom of the delivery service details screen.
+
+.. index::
+  Server Assignments
+
+.. _rl-assign-edges:
+
+Server Assignments
+++++++++++++++++++
+Click the **Server Assignments** button at the bottom of the screen to assign servers to this delivery service.  Servers can be selected by drilling down in a tree, starting at the profile, then the cache group, and then the individual servers. Traffic Router will only route traffic for this delivery service to servers that are assigned to it.
+
+
+.. _rl-asn-czf:
+
+The Coverage Zone File and ASN Table
+++++++++++++++++++++++++++++++++++++
+The Coverage Zone File (CZF) should contain a cachegroup name to network prefix mapping in the form: ::
+
+  {
+    "coverageZones": {
+      "cache-group-01": {
+        "network6": [
+          "1234:5678::\/64",
+          "1234:5679::\/64"
+        ],
+        "network": [
+          "192.168.8.0\/24",
+          "192.168.9.0\/24"
+        ]
+      }
+      "cache-group-02": {
+        "network6": [
+          "1234:567a::\/64",
+          "1234:567b::\/64"
+        ],
+        "network": [
+          "192.168.4.0\/24",
+          "192.168.5.0\/24"
+        ]
+      }
+    }
+  }
+
+The CZF is an input to the Traffic Control CDN, and as such does not get generated by Traffic Ops, but rather, it gets consumed by Traffic Router. Some popular IP management systems output a very similar file to the CZF but in stead of a cachegroup an ASN will be listed. Traffic Ops has the "Networks (ASNs)" view to aid with the conversion of files like that to a Traffic Control CZF file; this table is not used anywhere in Traffic Ops, but can be used to script the conversion using the API.
+
+The script that generates the CZF file is not part of Traffic Control, since it is different for each situation.
+
+.. _rl-working-with-profiles:
+
+Parameters and Profiles
+=======================
+Parameters are shared between profiles if the set of ``{ name, config_file, value }`` is the same. To change a value in one profile but not in others, the parameter has to be removed from the profile you want to change it in, and a new parameter entry has to be created (**Add Parameter** button at the bottom of the Parameters view), and assigned to that profile. It is easy to create new profiles from the **Misc > Profiles** view - just use the **Add/Copy Profile** button at the bottom of the profile view to copy an existing profile to a new one. Profiles can be exported from one system and imported to another using the profile view as well. It makes no sense for a parameter to not be assigned to a single profile - in that case it really has no function. To find parameters like that use the **Parameters > Orphaned Parameters** view. It is easy to create orphaned parameters by removing all profiles, or not assigning a profile directly after creating the parameter.
+
+.. seealso:: :ref:`rl-param-prof` in the *Configuring Traffic Ops* section.
+
+
+
+Tools
+=====
+
+.. index::
+  ISO
+  Generate ISO
+
+.. _rl-generate-iso:
+
+Generate ISO
+++++++++++++
+
+Generate ISO is a tool for building custom ISOs for building caches on remote hosts. Currently it only supports Centos 6, but if you're brave and pure of heart you MIGHT be able to get it to work with other unix-like OS's.
+
+The interface is *mostly* self explainatory as it's got hints.
+
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| Field                         |  Explaination                                                                                                                   |
++===============================+=================================================================================================================================+
+|Choose a server from list:     | This option gets all the server names currently in the Traffic Ops database and will autofill known values.                     |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| OS Version:                   | There needs to be an _osversions.cfg_ file in the ISO directory that maps the name of a directory to a name that shows up here. |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| Hostname:                     | This is the FQDN of the server to be installed. It is required.                                                                 |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| Root password:                | If you don't put anything here it will default to the salted MD5 of "Fred". Whatever put is MD5 hashed and writte to disk.      |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| DHCP:                         | if yes, other IP settings will be ignored                                                                                       |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| IP Address:                   | Required if DHCP=no                                                                                                             |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| Netmask:                      | Required if DHCP=no                                                                                                             |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| Gateway:                      | Required if DHCP=no                                                                                                             |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| IPV6 Address:                 | Optional. /64 is assumed if prefix is omitted                                                                                   |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| IPV6 Gateway:                 | Ignored if an IPV4 gateway is specified                                                                                         |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| Network Device:               | Optional. Typical values are bond0, eth4, etc. Note: if you enter bond0, a LACP bonding config will be written                  |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| MTU:                          | If unsure, set to 1500                                                                                                          |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+| Specify disk for OS install:  | Optional. Typical values are "sda".                                                                                             |
++-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
+
+
+When you click the **Download ISO** button the folling occurs (all paths relative to the top level of the directory specified in _osversions.cfg_):
+
+#. Reads /etc/resolv.conf to get a list of nameservers. This is a rather ugly hack that is in place until we get a way of configuring it in the interface.
+#. Writes a file in the ks_scripts/state.out that contains directory from _osversions.cfg_ and the mkisofs string that we'll call later.
+#. Writes a file in the ks_scripts/network.cfg that is a bunch of key=value pairs that set up networking.
+#. Creates an MD5 hash of the password you specify and writes it to ks_scripts/password.cfg. Note that if you do not specify a password "Fred" is used. Also note that we have experienced some issues with webbrowsers autofilling that field.
+#. Writes out a disk configuration file to ks_scripts/disk.cfg.
+#. mkisofs is called against the directory configured in _osversions.cfg_ and an ISO is generated in memory and delivered to your webbrowser.
+
+You now have a customized ISO that can be used to install Red Hat and derivative Linux installations with some modifications to your ks.cfg file.
+
+Kickstart/Anaconda will mount the ISO at /mnt/stage2 during the install process (at least with 6).
+
+You can directly include the password file anywhere in your ks.cfg file (usually in the top) by doing %include /mnt/stage2/ks_scripts/password.cfg
+
+What we currently do is have 2 scripts, one to do hard drive configuration and one to do network configuration. Both are relatively specific to the environment they were created in, and both are *probably* wrong for other organizations, however they are currently living in the "misc" directory as examples of how to do things.
+
+We trigger those in a %pre section in ks.cfg and they will write config files to /tmp. We will then include those files in the appropriate places using  %pre.
+
+For example this is a section of our ks.cfg file: ::
+
+  %include /mnt/stage2/ks_scripts/packages.txt
+
+  %pre
+    python /mnt/stage2/ks_scripts/create_network_line.py
+    bash /mnt/stage2/ks_scripts/drive_config.sh
+  %end
+
+These two scripts will then run _before_ anaconda sets up it's internal structures, then a bit further up in the ks.cfg file (outside of the %pre %end block) we do an ::
+
+    %include /mnt/stage2/ks_scripts/password.cfg
+    ...
+    %include /tmp/network_line
+
+    %include /tmp/drive_config
+    ...
+
+This snarfs up the contents and inlines them.
+
+If you only have one kind of hardware on your CDN it is probably best to just put the drive config right in the ks.cfg.
+
+If you have simple networking needs (we use bonded interfaces in most, but not all locations and we have several types of hardware meaning different ethernet interface names at the OS level etc.) then something like this: ::
+
+  #!/bin/bash
+  source /mnt/stage2/ks_scripts/network.cfg
+  echo "network --bootproto=static --activate --ipv6=$IPV6ADDR --ip=$IPADDR --netmask=$NETMASK --gateway=$GATEWAY --ipv6gateway=$GATEWAY --nameserver=$NAMESERVER --mtu=$MTU --hostname=$HOSTNAME" >> /tmp/network.cfg
+  # Note that this is an example and may not work at all.
+
+
+You could also put this in the %pre section. Lots of ways to solve it.
+
+We have included the two scripts we use in the "misc" directory of the git repo:
+
+* kickstart_create_network_line.py
+* kickstart_drive_config.sh
+
+These scripts were written to support a very narrow set of expectations and environment and are almost certainly not suitable to just drop in, but they might provide a good starting point.
+
+.. _rl-queue-updates:
+
+Queue Updates and Snapshot CRConfig
++++++++++++++++++++++++++++++++++++
+When changing delivery services special care has to be taken so that Traffic Router will not send traffic to caches for delivery services that the cache doesn't know about yet. In general, when adding delivery services, or adding servers to a delivery service, it is best to update the caches before updating Traffic Router and Traffic Monitor. When deleting delivery services, or deleting server assignments to delivery services, it is best to update Traffic Router and Traffic Monitor first and then the caches. Updating the cache configuration is done through the *Queue Updates* menu, and updating Traffic Monitor and  Traffic Router config is done through the *Snapshot CRConfig* menu.
+
+.. index::
+  Cache Updates
+  Queue Updates
+
+Queue Updates
+^^^^^^^^^^^^^
+Every 15 minutes the caches will run a *syncds* to get all changes needed from Traffic Ops. The files that will be updated by the syncds job are:
+
+- records.config
+- remap.config
+- parent.config
+- cache.config
+- hosting.config
+- url\_sig\_(.*)\.config
+- hdr\_rw\_(.*)\.config
+- regex_revalidate.config
+- ip_allow.config
+
+A cache will only get updated when the update flag is set for it. To set the update flag, use the *Queue Updates* menu - here you can schedule updates for a whole CDN or a cache group:
+
+  #. Click **Tools > Queue Updates**.
+  #. Select the CDN to queueu uodates for, or All.
+  #. Select the cache group to queue updates for, or All
+  #. Click the **Queue Updates** button.
+  #. When the Queue Updates for this Server? (all) window opens, click **OK**.
+
+To schedule updates for just one cache, use the "Server Checks" page, and click the |checkmark| in the *UPD* column. The UPD column of Server Checks page will change show a |clock| when updates are pending for that cache.
+
+
+.. index::
+  Snapshot CRConfig
+
+.. _rl-snapshot-crconfig:
+
+Snapshot CRConfig
+^^^^^^^^^^^^^^^^^
+
+Every 60 seconds Traffic Monitor will check with Traffic Ops to see if a new CRConfig snapshot exists; Traffic Monitor polls Traffic Ops for a new CRConfig, and Traffic Router polls Traffic Monitor for the same file. This is necessary to ensure that Traffic Monitor sees configuration changes first, which helps to ensure that the health and state of caches and delivery services propagates properly to Traffic Router. See :ref:`rl-ccr-profile` for more information on the CRConfig file.
+
+To create a new snapshot, use the *Tools > Snapshot CRConfig* menu:
+
+  #. Click **Tools > Snapshot CRConfig**.
+  #. Verify the selection of the correct CDN from the Choose CDN drop down and click **Diff CRConfig**.
+     On initial selection of this, the CRConfig Diff window says the following:
+
+     There is no existing CRConfig for [cdn] to diff against... Is this the first snapshot???
+     If you are not sure why you are getting this message, please do not proceed!
+     To proceed writing the snapshot anyway click the 'Write CRConfig' button below.
+
+     If there is an older version of the CRConfig, a window will pop up showing the differences
+     between the active CRConfig and the CRConfig about to be written.
+
+  #. Click **Write CRConfig**.
+  #. When the This will push out a new CRConfig.json. Are you sure? window opens, click **OK**.
+  #. The Successfully wrote CRConfig.json! window opens, click **OK**.
+
+
+.. index::
+  Invalidate Content
+  Purge
+
+.. _rl-purge:
+
+Invalidate Content
+==================
+Invalidating content on the CDN is sometimes necessary when the origin was mis-configured and something is cached in the CDN  that needs to be removed. Given the size of a typical Traffic Control CDN and the amount of content that can be cached in it, removing the content from all the caches may take a long time. To speed up content invalidation, Traffic Ops will not try to remove the content from the caches, but it makes the content inaccessible using the *regex_revalidate* ATS plugin. This forces a *revalidation* of the content, rather than a new get.
+
+.. Note:: This method forces a HTTP *revalidation* of the content, and not a new *GET* - the origin needs to support revalidation according to the HTTP/1.1 specification, and send a ``200 OK`` or ``304 Not Modified`` as applicable.
+
+To invalidate content:
+
+  1. Click **Tools > Invalidate Content**
+  2. Fill out the form fields:
+
+    - Select the **Delivery Service**
+    - Enter the **Path Regex** - this should be a `PCRE <http://www.pcre.org/>`_ compatible regular expression for the path to match for forcing the revalidation. Be careful to only match on the content you need to remove - revalidation is an expensive operation for many origins, and a simple ``/.*`` can cause an overload condition of the origin.
+    - Enter the **Time To Live** - this is how long the revalidation rule will be active for. It usually makes sense to make this the same as the ``Cache-Control`` header from the origin which sets the object time to live in cache (by ``max-age`` or ``Expires``). Entering a longer TTL here will make the caches do unnecessary work.
+    - Enter the **Start Time** - this is the start time when the revalidation rule will be made active. It is pre-populated with the current time, leave as is to schedule ASAP.
+
+  3. Click the **Submit** button.
+
+
+Manage DNSSEC Keys
+====================
+
+In order to support `DNSSEC <https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions>`_ in Traffic Router, Traffic Ops provides some actions for managing DNSSEC keys for a CDN and associated Delivery Services.  DNSSEC Keys consist of a Key Signing Keys (KSK) which are used to sign other DNSKEY records as well as Zone Signing Keys (ZSK) which are used to sign other records.  DNSSEC Keys are stored in `Traffic Vault <../overview/traffic_vault.html>`_ and should only be accessible to Traffic Ops.  Other applications needing access to this data, such as Traffic Router, must use the Traffic Ops `DNSSEC APIs <../development/traffic_ops_api/v12/cdn.html#dnssec-keys>`_ to retrieve this information.
+
+To Manage DNSSEC Keys:
+  1. Click **Tools -> Manage DNSSEC Keys**
+  2. Choose a CDN and click **Manage DNSSEC Keys**
+
+    - If keys have not yet been generated for a CDN, this screen will be mostly blank with just the **CDN** and **DNSSEC Active?** fields being populated.
+    - If keys have been generated for the CDN, the Manage DNSSEC Keys screen will show the TTL and Top Level Domain (TLD) KSK Expiration for the CDN as well as DS Record information which will need to be added to the parent zone of the TLD in order for DNSSEC to work.
+
+The Manage DNSSEC Keys screen also allows a user to perform the following actions:
+
+**Activate/Deactivate DNSSEC for a CDN**
+
+Fairly straight forward, this button set the **dnssec.enabled** param to either **true** or **false** on the Traffic Router profile for the CDN.  The Activate/Deactivate option is only available if DNSSEC keys exist for CDN.  In order to active DNSSEC for a CDN a user must first generate keys and then click the **Active DNSSEC** button.
+
+**Generate Keys**
+
+Generate Keys will generate DNSSEC keys for the CDN TLD as well as for each Delivery Service in the CDN.  It is important to note that this button will create a new KSK for the TLD and, therefore, a new DS Record.  Any time a new DS Record is created, it will need to be added to the parent zone of the TLD in order for DNSSEC to work properly.  When a user clicks the **Generate Keys** button, they will be presented with a screen with the following fields:
+
+  - **CDN:** This is not editable and displays the CDN for which keys will be generated
+  - **ZSK Expiration (Days):**  Sets how long (in days) the Zone Signing Key will be valid for the CDN and associated Delivery Services. The default is 30 days.
+  - **KSK Expiration (Days):**  Sets how long (in days) the Key Signing Key will be valid for the CDN and associated Delivery Services. The default is 365 days.
+  - **Effective Date (GMT):** The time from which the new keys will be active.  Traffic Router will use this value to determine when to start signing with the new keys and stop signing with the old keys.
+
+Once these fields have been correctly entered, a user can click Generate Keys.  The user will be presented with a confirmation screen to help them understand the impact of generating the keys.  If a user confirms, the keys will be generated and stored in Traffic Vault.
+
+**Regenerate KSK**
+
+Regenerate KSK will create a new Key Signing Key for the CDN TLD. A new DS Record will also be generated and need to be put into the parent zone in order for DNSSEC to work correctly. The **Regenerate KSK** button is only available if keys have already been generated for a CDN.  The intent of the button is to provide a mechanism for generating a new KSK when a previous one expires or if necessary for other reasons such as a security breach.  When a user goes to generate a new KSK they are presented with a screen with the following options:
+
+  - **CDN:** This is not editable and displays the CDN for which keys will be generated
+  - **KSK Expiration (Days):**  Sets how long (in days) the Key Signing Key will be valid for the CDN and associated Delivery Services. The default is 365 days.
+  - **Effective Date (GMT):** The time from which the new KSK and DS Record will be active.  Since generating a new KSK will generate a new DS Record that needs to be added to the parent zone, it is very important to make sure that an effective date is chosen that allows for time to get the DS Record into the parent zone.  Failure to get the new DS Record into the parent zone in time could result in DNSSEC errors when Traffic Router tries to sign responses.
+
+Once these fields have been correctly entered, a user can click Generate KSK.  The user will be presented with a confirmation screen to help them understand the impact of generating the KSK.  If a user confirms, the KSK will be generated and stored in Traffic Vault.
+
+Additionally, Traffic Ops also performs some systematic management of DNSSEC keys.  This management is necessary to help keep keys in sync for Delivery Services in a CDN as well as to make sure keys do not expire without human intervention.
+
+**Generation of keys for new Delivery Services**
+
+If a new Delivery Service is created and added to a CDN that has DNSSEC enabled, Traffic Ops will create DNSSEC keys for the Delivery Service and store them in Traffic Vault.
+
+**Regeneration of expiring keys for a Delivery Service**
+
+Traffic Ops has a process, controlled by cron, to check for expired or expiring keys and re-generate them.  The process runs at 5 minute intervals to check and see if keys are expired or close to expiring (withing 10 minutes by default).  If keys are expired for a Delivery Service, traffic ops will regenerate new keys and store them in Traffic Vault.  This process is the same for the CDN TLD ZSK, however Traffic Ops will not re-generate the CDN TLD KSK systematically.  The reason is that when a KSK is regenerated for the CDN TLD then a new DS Record will also be created.  The new DS Record needs to be added to the parent zone before Traffic Router attempts to sign with the new KSK in order for DNSSEC to work correctly.  Therefore, management of the KSK needs to be a manual process.
+
+
+
+
+
diff --git a/docs/1.8.0/_sources/admin/traffic_portal.txt b/docs/1.8.0/_sources/admin/traffic_portal.txt
new file mode 100644
index 0000000..9e761b8
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_portal.txt
@@ -0,0 +1,53 @@
+..
+..
+.. 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 Portal Administration
+*****************************
+The following are requirements to ensure an accurate set up:
+
+* CentOS 6.7 or 7
+* Node.js 6.0.x or above
+
+**Installing Traffic Portal**
+
+	- Download the Traffic Portal RPM from the traffic control `downloads <https://trafficcontrol.apache.org/downloads/index.html>`_ page or build from `source <https://github.com/apache/incubator-trafficcontrol/traffic_portal/build>`_.
+	- Copy the Traffic Portal RPM to your server
+	- curl --silent --location https://rpm.nodesource.com/setup_6.x | sudo bash -
+	- sudo yum install -y nodejs
+	- sudo yum install -y <traffic_portal rpm>
+
+**Configuring Traffic Portal**
+
+	- cd /etc/traffic_portal/conf
+	- sudo cp config-template.js config.js
+	- sudo vi config.js (read the inline comments)
+	- [OPTIONAL] sudo vi /opt/traffic_portal/public/traffic_portal_properties.json (to customize traffic portal content)
+	- [OPTIONAL] sudo vi /opt/traffic_portal/public/resources/assets/css/custom.css (to customize traffic portal skin)
+
+**Starting Traffic Portal**
+
+	- sudo service traffic_portal start
+
+**Stopping Traffic Portal**
+
+	- sudo service traffic_portal stop
+
+
+
+
+
+
+
diff --git a/docs/1.8.0/_sources/admin/traffic_router.txt b/docs/1.8.0/_sources/admin/traffic_router.txt
new file mode 100644
index 0000000..01ab6b3
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_router.txt
@@ -0,0 +1,494 @@
+..
+..
+.. 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 Router Administration
+*****************************
+.. contents::
+  :depth: 2
+  :backlinks: top
+
+Installing Traffic Router
+==========================
+The following are requirements to ensure an accurate set up:
+
+* CentOS 6
+* 4 vCPUs
+* 8GB RAM
+* Successful install of Traffic Ops
+* Successful install of Traffic Monitor
+* Administrative access to Traffic Ops
+
+.. Note:: Hardware requirements are generally doubled if DNSSEC is enabled
+
+1. If no suitable profile exists, create a new profile for Traffic Router.
+
+2. Enter the Traffic Router server into Traffic Ops, assign it to a Traffic Router profile, and ensure that its status is set to ``ONLINE``.
+3. Ensure the FQDN of the Traffic Monitor is resolvable in DNS. This FQDN must be resolvable by the clients expected to use this CDN.
+4. Install a traffic router: ``sudo yum install traffic_router``.
+5. Edit ``/opt/traffic_router/conf/traffic_monitor.properties`` and specify the correct online Traffic Monitor(s) for your CDN. See :ref:`rl-tr-config-files`
+	# traffic_monitor.properties: url that should normally point to this file
+	traffic_monitor.properties=file:/opt/traffic_router/conf/traffic_monitor.properties
+
+	# Frequency for reloading this file
+	# traffic_monitor.properties.reload.period=60000
+
+
+6. Start Tomcat: ``sudo service tomcat start``, and test lookups with dig and curl against that server.
+7. Snapshot CRConfig; See :ref:`rl-snapshot-crconfig`
+
+..  Note:: Once the CRConfig is snapshotted, live traffic will be sent to the new Traffic Routers provided that their status is set to ``ONLINE``.
+
+8. Ensure that the parent domain (e.g.: kabletown.net) for the CDN's top level domain (e.g.: cdn.kabletown.net) contains a delegation (NS records) for the new Traffic Router, and that the value specified matches the FQDN used in step 3.
+
+Configuring Traffic Router
+==========================
+
+.. Note:: Starting with Traffic Router 1.5, many of the configuration files under ``/opt/traffic_router/conf`` are only needed to override the default configuration values for Traffic Router. Most of the given default values will work well for any CDN. Critical values that must be changed are hostnames and credentials for communicating with other Traffic Control components such as Traffic Ops and Traffic Monitor.
+
+.. Note:: Pre-existing installations having configuration files in ``/opt/traffic_router/conf`` will still be used and honored for Traffic Router 1.5 and onward.
+
+For the most part, the configuration files and parameters that follow are used to get Traffic Router online and communicating with various Traffic Control components. Once Traffic Router is successfully communicating with Traffic Control, configuration is mostly performed in Traffic Ops, and is distributed throughout Traffic Control via the CRConfig snapshot process. See :ref:`rl-snapshot-crconfig` for more information. Please see the parameter documentation for Traffic Router in the Using Traffic Ops guide documented under :ref:`rl-ccr-profile` for parameters that influence the behavior of Traffic Router via the CRConfig.
+
+.. _rl-tr-config-files:
+
+Configuration files
+-------------------
+
++----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|         File name          |                 Parameter                 |                                             Description                                             |                   Default Value                   |
++============================+===========================================+=====================================================================================================+===================================================+
+| traffic_monitor.properties | traffic_monitor.bootstrap.hosts           | Traffic Monitor FQDNs and port if necessary, separated by a semicolon (;)                           | N/A                                               |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | traffic_monitor.bootstrap.local           | Use only the Traffic Monitors specified in config file                                              | false                                             |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | traffic_monitor.properties                | Path to the traffic_monitor.properties file; used internally to monitor the file for changes        | /opt/traffic_router/traffic_monitor.properties    |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | traffic_monitor.properties.reload.period  | The interval in milliseconds which Traffic Router will reload this configuration file               | 60000                                             |
++----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+| dns.properties             | dns.tcp.port                              | TCP port that Traffic Router will use for incoming DNS requests                                     | 53                                                |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | dns.tcp.backlog                           | Maximum length of the queue for incoming TCP connection requests                                    | 0                                                 |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | dns.udp.port                              | UDP port that Traffic Router will use for incoming DNS requests                                     | 53                                                |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | dns.max-threads                           | Maximum number of threads used to process incoming DNS requests                                     | 1000                                              |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | dns.zones.dir                             | Path to auto generated zone files for reference                                                     | /opt/traffic_router/var/auto-zones                |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | dns.routing.name                          | The label (A/AAAA) Traffic Router will use for the entry point for a DNS delivery service           | edge (e.g.: edge.mydeliveryservice.kabletown.net) |
++----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+| traffic_ops.properties     | traffic_ops.username                      | Username to access the APIs in Traffic Ops (must be in the admin role)                              | admin                                             |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | traffic_ops.password                      | Password for the user specified in traffic_ops.username                                             | N/A                                               |
++----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+| http.properties            | http.routing.name                         | The label (A/AAAA) Traffic Router will use for the entry point for an HTTP delivery service         | tr (e.g.: tr.mydeliveryservice.kabletown.net)     |
++----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+| cache.properties           | cache.geolocation.database                | Full path to the local copy of the MaxMind geolocation binary database file                         | /opt/traffic_router/db/GeoIP2-City.mmdb           |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | cache.geolocation.database.refresh.period | The interval in milliseconds which Traffic Router will poll for a new geolocation database          | 604800000                                         |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | cache.czmap.database                      | Full path to the local copy of the coverage zone file                                               | /opt/traffic_router/db/czmap.json                 |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | cache.czmap.database.refresh.period       | The interval in milliseconds which Traffic Router will poll for a new coverage zone file            | 10800000                                          |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | cache.health.json                         | Full path to the local copy of the health state                                                     | /opt/traffic_router/db/health.json                |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | cache.health.json.refresh.period          | The interval in milliseconds which Traffic Router will poll for a new health state file             | 1000                                              |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | cache.config.json                         | Full path to the local copy of the CRConfig                                                         | /opt/traffic_router/db/cr-config.json             |
+|                            +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+|                            | cache.config.json.refresh.period          | The interval in milliseconds which Traffic Router will poll for a new CRConfig                      | 60000                                             |
++----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+| log4j.properties           | various parameters                        | Configuration of log4j is documented on their site; adjust as necessary based on needs              | N/A                                               |
++----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
+
+.. _rl-tr-dnssec:
+
+DNSSEC
+======
+
+Overview
+--------
+Domain Name System Security Extensions (DNSSEC) is a set of extensions to DNS that provides a cryptographic mechanism for resolvers to verify the authenticity of responses served by an authoritative DNS server.
+
+Several RFCs (4033, 4044, 4045) describe the low level details and define the extensions, RFC 7129 provides clarification around authenticated denial of existence of records, and finally RFC 6781 describes operational best practices for administering an authoritative DNSSEC enabled DNS server. The authenticated denial of existence RFC describes how an authoritative DNS server responds in NXDOMAIN and NODATA scenarios when DNSSEC is enabled.
+
+Traffic Router currently supports DNSSEC with NSEC, however, NSEC3 and more configurable options will be provided in the future.
+
+Operation
+---------
+Upon startup or a configuration change, Traffic Router obtains keys from the keystore API in Traffic Ops which returns key signing keys (KSK) and zone signing keys (ZSK) for each delivery service that is a subdomain off the CDN's top level domain (TLD), in addition to the keys for the CDN TLD itself. Each key has timing information that allows Traffic Router to determine key validity (expiration, inception, and effective dates) in addition to the appropriate TTL to use for the DNSKEY record(s).  All TTLs are configurable parameters; see the :ref:`rl-ccr-profile` documentation for more information.
+
+Once Traffic Router obtains the key data from the API, it converts each public key into the appropriate record types (DNSKEY, DS) to place in zones and uses the private key to sign zones. DNSKEY records are added to each delivery service's zone (e.g.: mydeliveryservice.cdn.kabletown.net) for every valid key that exists, in addition to the CDN TLD's zone. A DS record is generated from each zone's KSK and is placed in the CDN TLD's zone (e.g.: cdn.kabletown.net); the DS record for the CDN TLD must be placed in its parent zone, which is not managed by Traffic Control.
+
+The DNSKEY to DS record relationship allows resolvers to validate signatures across zone delegation points; with Traffic Control, we control all delegation points below the CDN's TLD, **however, the DS record for the CDN TLD must be placed in the parent zone (e.g.: kabletown.net), which is not managed by Traffic Control**. As such, the DS record (available in the Traffic Ops DNSSEC administration UI) must be placed in the parent zone prior to enabling DNSSEC, and prior to generating a new CDN KSK. Based on your deployment's DNS configuration, this might be a manual process or it might be automated; either way, extreme care and diligence must be taken and knowledge of the management of the upstream zone is imperative for a successful DNSSEC deployment.
+
+Rolling Zone Signing Keys
+-------------------------
+Traffic Router currently follows the zone signing key pre-publishing operational best practice described in `section 4.1.1.1 of RFC 6781`_. Once DNSSEC is enabled for a CDN in Traffic Ops, key rolls are triggered via Traffic Ops via the automated key generation process, and Traffic Router selects the active zone signing keys based on the expiration information returned from the keystore API in Traffic Ops.
+
+.. _section 4.1.1.1 of RFC 6781: https://tools.ietf.org/html/rfc6781#section-4.1.1.1
+
+Troubleshooting and log files
+=============================
+Traffic Router log files are in ``/opt/traffic_router/var/log``, and Tomcat log files are in ``/opt/tomcat/logs``. Application related logging is in ``/opt/traffic_router/var/log/traffic_router.log``, while access logs are written to ``/opt/traffic_router/var/log/access.log``.
+
+Event Log File Format
+=====================
+
+Summary
+-------
+
+All access events to Traffic Router are logged to the file ``/opt/traffic_router/var/log/access.log``
+This file grows up to 200Mb and gets rolled into older log files, 10 log files total are kept (total of up to 2Gb of logged events per traffic router)
+
+Traffic Router logs access events in a format that largely following `ATS event logging format
+<https://docs.trafficserver.apache.org/en/6.0.x/admin/event-logging-formats.en.html>`_
+
+--------------
+
+Sample Message
+--------------
+
+Items within brackets below are detailed under the HTTP and DNS sections
+::
+
+  144140678.000 qtype=DNS chi=192.168.10.11 ttms=789 [Fields Specific to the DNS request] rtype=CZ rloc="40.252611,58.439389" rdtl=- rerr="-" [Fields Specific to the DNS result]
+  144140678.000 qtype=HTTP chi=192.168.10.11 ttms=789 [Fields Specific to the HTTP request] rtype=GEO rloc="40.252611,58.439389" rdtl=- rerr="-" [Fields Specific to the HTTP result]
+
+.. Note:: The above message samples contain fields that are always present for every single access event to Traffic Router
+
+**Message Format**
+- Each event that is logged is a series of space separated key value pairs except for the first item.
+- The first item is always the epoch in seconds with a decimal field precision of up to milliseconds
+- Each key value pair is in the form of unquoted string, equals character, optionally quoted string
+- Values that are quoted strings may contain space characters
+- Values that are not quoted should not contains any space characters
+
+.. Note:: Any value that is a single dash character or a dash character enclosed in quotes represents an empty value
+
+--------
+
+Fields Always Present
+---------------------
+
++------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------+
+|Name  |Description                                                                      |Data                                                                       |
++======+=================================================================================+===========================================================================+
+|qtype |Whether the request was for DNS or HTTP                                          |Always DNS or HTTP                                                         |
++------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------+
+|chi   |The IP address of the requester                                                  |Depends on whether this was a DNS or HTTP request, see below sections      |
++------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------+
+|ttms  |The amount of time in milliseconds it took Traffic Router to process the request |A number greater than or equal to zero                                     |
++------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------+
+|rtype |Routing Result Type                                                              |One of ERROR, CZ, GEO, MISS, STATIC_ROUTE, DS_REDIRECT, DS_MISS, INIT, FED |
++------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------+
+|rloc  |GeoLocation of result                                                            |Latitude and Longitude in Decimal Degrees                                  |
++------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------+
+|rdtl  |Result Details Associated with unusual conditions                                |One of DS_NOT_FOUND, DS_NO_BYPASS, DS_BYPASS, DS_CZ_ONLY                   |
++------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------+
+|rerr  |Message about internal Traffic Router Error                                      |String                                                                     |
++------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------+
+
+**rtype meanings**
+
++-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|Name         |Meaning                                                                                                                                                                 |
++=============+========================================================================================================================================================================+
+|ERROR        |An internal error occurred within Traffic Router, more details may be found in the rerr field                                                                           |
++-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|CZ           |The result was derived from Coverage Zone data based on the address in the chi field                                                                                    |
++-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|GEO          |The result was derived from geolocation service based on the address in the chi field                                                                                   |
++-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|MISS         |Traffic Router was unable to resolve a DNS request or find a cache for the requested resource                                                                           |
++-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|STATIC_ROUTE |_*DNS Only*_ No DNS Delivery Service supports the hostname portion of the requested url                                                                                 |
++-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|DS_MISS      |_*HTTP Only*_ No HTTP Delivery Service supports either this request's URL path or headers                                                                               |
++-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|DS_REDIRECT  |The result is using the Bypass Destination configured for the matched Delivery Service when that Delivery Service is unavailable or does not have the requested resource|
++-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|FED          |_*DNS Only*_ The result was obtained through federated coverage zone data outside of any delivery service                                                               |
++-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+
+**rdtl meanings**
+
++--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
+|Name                      |Meaning                                                                                                                                     |
++==========================+============================================================================================================================================+
+|DS_NOT_FOUND              |Always goes with rtypes STATIC_ROUTE and DS_MISS                                                                                            |
++--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
+|DS_BYPASS                 |Used Bypass Destination for Redirect of Delivery Service                                                                                    |
++--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
+|DS_NO_BYPASS              |No valid Bypass Destination is configured for the matched Delivery Service and the delivery service does not have the requested resource    |
++--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
+|DS_CZ_ONLY                |The selected Delivery Service only supports resource lookup based on Coverage Zone data                                                     |
++--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
+|DS_CLIENT_GEO_UNSUPPORTED |Traffic Router did not find a resource supported by coverage zone data and was unable to determine the geolocation of the requesting client |
++--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
+|GEO_NO_CACHE_FOUND        |Traffic Router could not find a resource via geolocation data based on the requesting client's geolocation                                  |
++--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
+
+---------------
+
+HTTP Specifics
+--------------
+
+Sample Message
+::
+
+  1452197640.936 qtype=HTTP chi=69.241.53.218 url="http://ccr.mm-test.jenkins.cdnlab.comcast.net/some/asset.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=GEO rloc="40.252611,58.439389" rdtl=- rerr="-" pssc=302 ttms=0 rurl="http://odol-atsec-sim-114.mm-test.jenkins.cdnlab.comcast.net:8090/some/asset.m3u8" rh="Accept: */*" rh="myheader: asdasdasdasfasg"
+
+**Request Fields**
+
++-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
+|Name |Description                                                                                                                              |Data                                       |
++=====+=========================================================================================================================================+===========================================+
+|url  |Requested URL with query string                                                                                                          |String                                     |
++-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
+|cqhm |Http Method                                                                                                                              |e.g GET, POST                              |
++-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
+|cqhv |Http Protocol Version                                                                                                                    |e.g. HTTP/1.1                              |
++-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
+|rh   |One or more of these key value pairs may exist in a logged event and are controlled by the configuration of the matched Delivery Service |Key value pair of the format "name: value" |
++-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
+
+**Response Fields**
+
++-----+----------------------------------------------------------+------------+
+|Name |Description                                               |Data        |
++=====+==========================================================+============+
+|rurl |The resulting url of the resource requested by the client |A URL String|
++-----+----------------------------------------------------------+------------+
+
+------------
+
+DNS Specifics
+-------------
+
+Sample Message
+::
+
+  144140678.000 qtype=DNS chi=192.168.10.11 ttms=123 xn=65535 fqdn=www.example.com. type=A class=IN ttl=12345 rcode=NOERROR rtype=CZ rloc="40.252611,58.439389" rdtl=- rerr="-" ans="192.168.1.2 192.168.3.4 0:0:0:0:0:ffff:c0a8:102 0:0:0:0:0:ffff:c0a8:304"
+
+**Request Fields**
+
+.. _qname: http://www.zytrax.com/books/dns/ch15/#qname
+
+.. _qtype: http://www.zytrax.com/books/dns/ch15/#qtype
+
++------+------------------------------------------------------------------+--------------------------------------------------------+
+|Name  |Description                                                       |Data                                                    |
++======+==================================================================+========================================================+
+|xn    |The ID from the client DNS request header                         |a number from 0 to 65535                                |
++------+------------------------------------------------------------------+--------------------------------------------------------+
+|fqdn  |The qname field from the client DNS request message (i.e. The     |A series of DNS labels/domains separated by '.'         |
+|      |fully qualified domain name the client is requesting be resolved) |characters and ending with a '.' character (see qname_) |
++------+------------------------------------------------------------------+--------------------------------------------------------+
+|type  |The qtype field from the client DNS request message (i.e.         |Examples are A (IpV4), AAAA (IpV6), NS (Name Service),  |
+|      |the type of resolution that's requested such as IPv4, IPv6)       |  SOA (Start of Authority), and CNAME, (see qtype_)     |
++------+------------------------------------------------------------------+--------------------------------------------------------+
+|class |The qclass field from the client DNS request message (i.e. The    |Either IN (Internet resource) or ANY (Traffic router    |
+|      |class of resource being requested)                                |  rejects requests with any other value of class)       |
++------+------------------------------------------------------------------+--------------------------------------------------------+
+
+**Response Fields**
+
++------+---------------------------------------------------------------------+-----------------------------------------------------+
+|Name  | Description                                                         | Data                                                |
++======+=====================================================================+=====================================================+
+|ttl   | The 'time to live' in seconds for the answer provided by Traffic    |A number from 0 to 4294967295                        |
+|      | Router (clients can reliably use this answer for this long without  |                                                     |
+|      | re-querying traffic router)                                         |                                                     |
++------+---------------------------------------------------------------------+-----------------------------------------------------+
+|rcode | The result code for the DNS answer provided by Traffic Router       | One of NOERROR (success), NOTIMP (request is not    |
+|      |                                                                     | NOTIMP (request is not  supported),                 |
+|      |                                                                     | REFUSED (request is refused to be answered), or     |
+|      |                                                                     | NXDOMAIN (the domain/name requested does not exist) |
++------+---------------------------------------------------------------------+-----------------------------------------------------+
+
+.. _rl-tr-ngb:
+
+GeoLimit Failure Redirect feature
+=================================
+
+Overview
+--------
+This feature is also called 'National GeoBlock' feature which is short for 'NGB' feature. In this section, the acronym 'NGB' will be used for this feature.
+
+In the past, if the Geolimit check fails (for example, the client ip is not in the 'US' region but the geolimit is set to 'CZF + US'), the router will return 503 response; but with this feature, when the check fails, it will return 302 if the redirect url is set in the delivery service.
+
+The Geolimit check failure has such scenarios:
+1) When the GeoLimit is set to 'CZF + only', if the client ip is not in the the CZ file, the check fails
+2) When the GeoLimit is set to any region, like 'CZF + US', if the client ip is not in such region, and the client ip is not in the CZ file, the check fails
+
+
+Configuration
+-------------
+To enable the NGB feature, the DS must be configured with the proper redirect url. And the setting lays at 'Delivery Services'->Edit->'GeoLimit Redirect URL'. If no url is put in this field, the feature is disabled.
+
+The URL has 3 kinds of formats, which have different meanings:
+
+1. URL with no domain. If no domain is in the URL (like 'vod/dance.mp4'), the router will try to find a proper cache server within the delivery service and return the redirect url with the format like 'http://<cache server name>.<delivery service's FQDN>/<configured relative path>'
+
+2. URL with domain that matches with the delivery service. For this URL, the router will also try to find a proper cache server within the delivery service and return the same format url as point 1.
+
+3. URL with domain that doesn't match with the delivery service. For this URL, the router will return the configured url directly to the client.
+
+.. _rl-tr-steering:
+
+Steering feature
+================
+
+Overview
+--------
+A Steering delivery service is a delivery service that is used to "steer" traffic to other delivery services. A Steering delivery service will have target delivery services configured for it with weights assigned to them.  Traffic Router uses the weights to make a consistent hash ring which it then uses to make sure that requests are routed to a target based on the configured weights.  This consistent hash ring is separate from the consistent hash ring used in cache selection.
+
+Special regular expressions called Filters can also be configured for target delivery services to pin traffic to a specific delivery service.  For example, if a filter called .*/news/.* for a target called target-ds-1 is created, any requests to traffic router with 'news' in them will be routed to target-ds-1.  This will happen regardless of the configured weights.
+
+A client can bypass the steering functionality by providing a header called X-TC-Steering-Option with the xml_id of the target delivery service to route to.  When Traffic Router receives this header it will route to the requested target delivery service regardless of weight configuration.
+
+Some other points of interest:
+- Steering is currently only available for HTTP delivery services that are a part of the same CDN.
+- A new role called STEERING has been added to the traffic ops database.  Only users with Admin or Steering privileges can modify steering assignments for a Delivery Service.
+- A new API has been created in Traffic Ops under /internal.  This API is used by a Steering user to add filters and modify assignments.  (Filters can only be added via the API).
+- Traffic Router uses the steering API in Traffic Ops to poll for steering assignments, the assignments are then used when routing traffic.
+
+A couple simple use cases for steering are:
+
+#. Migrating traffic from one delivery service to another over time.
+#. Trying out new functionality for a subset of traffic with an experimental delivery service.
+#. Load balancing between delivery services.
+
+
+
+Configuration
+-------------
+
+The following needs to be completed for Steering to work correctly:
+
+#. Two target delivery services are created in Traffic Ops.  They must both be HTTP delivery services part of the same CDN.
+#. A delivery service with type STEERING is created in Traffic Ops.
+#. Target delivery services are assigned to the steering delivery service using Traffic Ops.
+#. A user with the role of Steering is created.
+#. Using the API, the steering user assigns weights to the target delivery services.
+#. If desired, the steering user can create filters for the target delivery services.
+
+For more information see the `steering how-to guide <quick_howto/steering.html>`_.
+
+HTTPS for Http Type Delivery Services
+=====================================
+
+Starting with version 1.7 Traffic Router added the ability to allow https traffic between itself and clients on a per http type delivery service basis.
+
+.. Warning::
+  The establishing of an HTTPS connection is much more computationally demanding than an HTTP connection.
+  Since each client will in turn get redirected to ATS, Traffic Router is most always creating a new HTTPS connection for all HTTPS traffic.
+  It is likely to mean that an existing Traffic Router will have some decrease in performance depending on the amount of https traffic you want to support
+  As noted for DNSSEC, you may need to plan to scale Traffic Router vertically and/or horizontally to handle the new load
+
+The summary for setting up https is to:
+
+#. Select one of 'https', 'http and https', or 'http to https' for the delivery service 
+#. Generate private keys for the delivery service using a wildcard domain such as ``*.my-delivery-service.my-cdn.example.com``
+#. Obtain and import signed certificate chain
+#. Snapshot CR Config
+
+Clients may make HTTPS requests delivery services only after Traffic Router receives the certificate chain from Traffic Ops and the new CR Config.
+
+Protocol Options
+----------------
+
+*https only*
+  Traffic Router will only redirect (send a 302) to clients communicating with a secure connection, all other clients will receive a 503
+*http and https*
+  Traffic Router will redirect both secure and non-secure clients
+*http to https*
+  Traffic Router will redirect non-secure clients with a 302 and a location that is secure (i.e. starting with 'https' instead of 'http'), secure clients will remain on https
+*http*
+  Any secure client will get an SSL handshake error. Non-secure clients will experience the same behavior as prior to 1.7
+
+Certificate Retrieval
+---------------------
+
+.. Warning::
+  If you have https delivery services in your CDN, Traffic Router will not accept **any** connections until it is able to
+  fetch certificates from Traffic Ops and load them into memory. Traffic Router does not persist certificates to the java keystore or anywhere else.
+
+Traffic Router fetches certificates into memory:
+
+* At startup time
+* When it receives a new CR Config
+* Once an hour from whenever the most recent of the last of the above occurred
+
+.. Note::
+  To adjust the frequency when Traffic Router fetches certificates add the parameter 'certificates.polling.interval' to CR Config and 
+  setting it to the desired time in milliseconds.
+
+.. Note::
+  Taking a snapshot of CR Config may be used at times to avoid waiting the entire polling cycle for a new set of certificates.
+
+.. Warning::
+  If a snapshot of CR Config is made that involves a delivery service missing its certificates, Traffic Router will ignore **ALL** changes in that CR-Config
+  until one of the following occurs:
+  * It receives certificates for that delivery service 
+  * Another snapshot of CR Config is created and the delivery service without certificates is changed so it's HTTP protocol is set to 'http'
+
+Certificate Chain Ordering
+--------------------------
+
+The ordering of certificates within the certificate bundle matters. It must be:
+
+#. Primary Certificate (e.g. the one created for ``*.my-delivery-service.my-cdn.example.com``)
+#. Intermediate Certificate(s)
+#. Root Certificate from CA (optional)
+
+.. Warning::
+  If something is wrong with the certificate chain (e.g. the order of the certificates is backwards or for the wrong domain) the
+  client will get an SSL handshake.  Inspection of /opt/tomcat/logs/catalina.out is likely to yield information to reveal this.
+
+To see the ordering of certificates you may have to manually split up your certificate chain and use openssl on each individual certificate
+
+Suggested Way of Setting up an HTTPS Delivery Service
+-----------------------------------------------------
+
+Do the following in Traffic Ops:
+
+#. Select one of 'https', 'http and https', or 'http to https' for the protocol field of a delivery service and click 'Save'.
+#. Click 'Manage SSL Keys'.
+#. Click 'Generate New Keys'.
+#. Copy the contents of the Certificate Signing Request field and save it locally.
+#. Click 'Load Keys'.
+#. Select 'http' for the protocol field of the delivery service and click 'Save' (to avoid preventing other CR Config updates from being blocked by Traffic Router)
+#. Follow your standard procedure for obtaining your signed certificate chain from a CA.
+#. After receiving your certificate chain import it into Traffic Ops.
+#. Edit the delivery service.
+#. Restore your original choice for the protocol field and click save.
+#. Click 'Manage SSL Keys'.
+#. Click 'Paste Existing Keys'.
+#. Paste the certificate chain into the CRT field.
+#. Click 'Load Keys'.
+#. Take a new snapshot of CR Config.
+
+Once this is done you should be able to test you are getting correctly redirected by Traffic Router using curl commands to https destinations on your delivery service.
+
+A new testing tool was created for load testing traffic router, it allows you to generate requests from your local box to multiple delivery services of a single cdn.
+You can control which cdn, delivery services, how many transactions per delivery service, and how many concurrent requests.
+During the test it will provide feedback about request latency and transactions per second.
+
+While it is running it is suggested that you monitor your Traffic Router nodes for memory and CPU utilization.
+
diff --git a/docs/1.8.0/_sources/admin/traffic_server.txt b/docs/1.8.0/_sources/admin/traffic_server.txt
new file mode 100644
index 0000000..1b99ce0
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_server.txt
@@ -0,0 +1,71 @@
+.. 
+.. 
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+.. 
+..     http://www.apache.org/licenses/LICENSE-2.0
+.. 
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+.. 
+
+*****************************
+Traffic Server Administration
+*****************************
+Installing Traffic Server
+=========================
+1. Select **Servers** in the Traffic Ops web interface.
+2. Scroll to the bottom of the page and click **Add Server**.
+3. Complete the *Required Info*: section.
+4. Click **Submit**.
+5. Click **Save**.
+
+.. 6. Click **Online Server**.
+.. 7. From the Set status of this machine to ONLINE? screen, click **OK**.
+
+.. _reference-traffic-ops-ort:
+
+Configuring Traffic Server
+==========================
+All of the Traffic Server application configuration files are generated by Traffic Ops and installed by way of the traffic_ops_ort.pl script. 
+
+
+**traffic_ops_ort.pl**
+  The traffic_ops_ort.pl should be installed on all caches (by puppet or other non Traffic Ops means), usually in /opt/ort. It is used to do initial install of the config files when the cache is being deployed, and to keep the config files up to date when the cache is already in service.  The usage message of the script is shown below: ::
+
+    $ sudo ./traffic_ops_ort.pl syncds warn https://to.cdn.kabletown.net
+    Thu May 26 15:52:11 UTC 2016
+    ====-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-====
+    Usage: ./traffic_ops_ort.pl <Mode> <Log_Level> <Traffic_Ops_URL> <Traffic_Ops_Login> [optional flags]
+      <Mode> = interactive - asks questions during config process.
+      <Mode> = report - prints config differences and exits.
+      <Mode> = badass - attempts to fix all config differences that it can.
+      <Mode> = syncds - syncs delivery services with what is configured in Traffic Ops.
+
+      <Log_Level> => ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, NONE
+
+      <Traffic_Ops_URL> = URL to Traffic Ops host. Example: https://trafficops.company.net
+
+      <Traffic_Ops_Login> => Example: 'username:password'
+
+      [optional flags]:
+        dispersion=<time>      => wait a random number between 0 and <time> before starting. Default = 300.
+        retries=<number>       => retry connection to Traffic Ops URL <number> times. Default = 3.
+        wait_for_parents=<0|1> => do not update if parent_pending = 1 in the update json. Default = 1, wait for parents.
+    ====-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-====
+    $
+
+
+  For initial configuration or when major changes (like a Profile change) need to be made, run the script in "badass mode". All required rpm packages will be installed, all Traffic Server config files will be fetched and installed, and (if needed) the Traffic Server application will be restarted.  Example run below: ::
+
+    run here 
+
+  For "every day changes" such as adding deliveryservices or changing records.config parameters caches should run the script in "syncds" mode out of cron. Example crontab entry: :: 
+
+  		*/15 * * * * /opt/ort/traffic_ops_ort.pl syncds warn https://traffops.kabletown.net admin:password > /tmp/ort/syncds.log 2>&1
+
+  .. Note:: <disclaimer on what is "hot changeable" here>
diff --git a/docs/1.8.0/_sources/admin/traffic_stats.txt b/docs/1.8.0/_sources/admin/traffic_stats.txt
new file mode 100644
index 0000000..ae9d91b
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_stats.txt
@@ -0,0 +1,187 @@
+..
+..
+.. 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 Stats Administration
+****************************
+
+Traffic Stats consists of three seperate components:  Traffic Stats, InfluxDB, and Grafana.  See below for information on installing and configuring each component as well as configuring the integration between the three and Traffic Ops.
+
+Installation
+========================
+
+**Installing Traffic Stats:**
+
+	- Download the Traffic Stats RPM from the traffic control `downloads <https://trafficcontrol.apache.org/downloads/index.html>`_ page.
+	- Copy the Traffic Stats RPM to your server
+	- sudo rpm -ivh <traffic_stats rpm>
+
+**Installing InfluxDB:**
+
+	**As of Traffic Stats 1.8.0, InfluxDb 1.0.0 or higher is required.  For InfluxDb versions less than 1.0.0 use Traffic Stats 1.7.x**
+
+	In order to store traffic stats data you will need to install `InfluxDB <https://docs.influxdata.com/influxdb/latest/introduction/installation/>`_.  While not required, it is recommended to use some sort of high availability option like `Influx enterprise <https://portal.influxdata.com/>`_, `Influxdb Relay <https://github.com/influxdata/influxdb-relay>`_, or another `high availability option <https://www.influxdata.com/high-availability/>`_.
+
+
+**Installing Grafana:**
+
+	Grafana is used to display Traffic Stats/InfluxDB data in Traffic Ops.  Grafana is typically run on the same server as Traffic Stats but this is not a requirement.  Grafana can be installed on any server that can access InfluxDB and can be accessed by Traffic Ops.  Documentation on installing Grafana can be found on the `Grafana website <http://docs.grafana.org/installation/>`_.
+
+Configuration
+=========================
+
+**Configuring Traffic Stats:**
+
+	Traffic Stats' configuration file can be found in /opt/traffic_stats/conf/traffic_stats.cfg.
+	The following values need to be configured:
+
+	     - *toUser:* The user used to connect to Traffic Ops
+	     - *toPasswd:*  The password to use when connecting to Traffic Ops
+	     - *toUrl:*  The URL of the Traffic Ops server used by Traffic Stats
+	     - *influxUser:*  The user to use when connecting to InfluxDB (if configured on InfluxDB, else leave default)
+	     - *influxPassword:*  That password to use when connecting to InfluxDB (if configured, else leave blank)
+	     - *pollingInterval:*  The interval at which Traffic Monitor is polled and stats are stored in InfluxDB
+	     - *statusToMon:*  The status of Traffic Monitor to poll (poll ONLINE or OFFLINE traffic monitors)
+	     - *seelogConfig:*  The absolute path of the seelong config file
+	     - *dailySummaryPollingInterval:* The interval, in seconds, at which Traffic Stats checks to see if daily stats need to be computed and stored.
+	     - *cacheRetentionPolicy:* The default retention policy for cache stats
+	     - *dsRetentionPolicy:* The default retention policy for deliveryservice stats
+	     - *dailySummaryRetentionPolicy:* The retention policy to be used for the daily stats
+	     - *influxUrls:* An array of influxdb hosts for Traffic Stats to write stats to.
+
+**Configuring InfluxDB:**
+
+	As mentioned above, it is recommended that InfluxDb be running in some sort of high availability configuration.  There are several ways to achieve high availabilty so it is best to consult the high availability options on the `InfuxDB website <https://www.influxdata.com/high-availability/>`_.
+
+	Once InfluxDB is installed and configured, databases and retention policies need to be created.  Traffic Stats writes to three different databases: cache_stats, deliveryservice_stats, and daily_stats.  More information about the databases and what data is stored in each can be found on the `overview <../overview/traffic_stats.html>`_ page.
+
+	To easily create databases, retention policies, and continuous queries, run create_ts_databases from the /opt/traffic_stats/influxdb_tools directory on your Traffic Stats server.  See the `InfluxDb Tools <traffic_stats.html#influxdb-tools>`_ section below for more information.
+
+**Configuring Grafana:**
+
+		In Traffic Ops the Health -> Graph View tab can be configured to display grafana graphs using influxDb data.  In order for this to work correctly, you will need two things 1) a parameter added to traffic ops with the graph URL (more information below) and 2) the graphs created in grafana.  See below for how to create some simple graphs in grafana.  These instructions assume that InfluxDB has been configured and that data has been written to it.  If this is not true, you will not see any graphs.
+
+		- Login to grafana as an admin user http://grafana_url:3000/login
+		- Choose Data Sources and then Add New
+		- Enter the necessary information to configure your data source
+		- Click on the 'Home' dropdown at the top of the screen and choose New at the bottom
+		- Click on the green menu bar (with 3 lines) at the top and choose Add Panel -> Graph
+		- Where it says 'No Title (click here)' click and choose edit
+		- Choose your data source at the bottom
+		- You can have grafana help you create a query, or you can create your own.  Here is a sample query:
+
+			``SELECT sum(value)*1000 FROM "monthly"."bandwidth.cdn.1min" WHERE $timeFilter GROUP BY time(60s), cdn``
+		- Once you have the graph the way you want it, click the 'Save Dashboard' button at the top
+		- You should now have a new saved graph
+
+	In order for Traffic Ops users to see Grafana graphs, Grafana will need to allow anonymous access.  Information on how to configure anonymous access can be found on the configuration page of the `Grafana Website  <http://docs.grafana.org/installation/configuration/#authanonymous>`_.
+
+	Traffic Ops uses custom dashboards to display information about individual delivery services or cache groups.  In order for the custom graphs to display correctly, the `traffic_ops_*.js <https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_stats/grafana/>`_ files need to be in the ``/usr/share/grafana/public/dashboards/`` directory on the grafana server.  If your Grafana server is the same as your Traffic Stats server the RPM install process will take care of putting the files in place.  If your grafana server is different from your Traffic Stats server, you will need to manually copy the files to the correct directory.
+
+	More information on custom scripted graphs can be found in the `scripted dashboards <http://docs.grafana.org/reference/scripting/>`_ section of the Grafana documentation.
+
+**Configuring Traffic Ops for Traffic Stats:**
+
+	- The influxDb servers need to be added to Traffic Ops with profile = InfluxDB.  Make sure to use port 8086 in the configuration.
+	- The traffic stats server should be added to Traffic Ops with profile = Traffic Stats.
+	- Parameters for which stats will be collected are added with the release, but any changes can be made via parameters that are assigned to the Traffic Stats profile.
+
+**Configuring Traffic Ops to use Grafana Dashboards**
+
+	To configure Traffic Ops to use Grafana Dashboards, you need to enter the following parameters and assign them to the GLOBAL profile.  This assumes you followed the above instructions to install and configure InfluxDB and Grafana.  You will need to place 'cdn-stats','deliveryservice-stats', and 'daily-summary' with the name of your dashboards.
+
+	+---------------------------+------------------------------------------------------------------------------------------------+
+	|       parameter name      |                                        parameter value                                         |
+	+===========================+================================================================================================+
+	| all_graph_url             | https://<grafana_url>/dashboard/db/deliveryservice-stats                                       |
+	+---------------------------+------------------------------------------------------------------------------------------------+
+	| cachegroup_graph_url      | https://<grafanaHost>/dashboard/script/traffic_ops_cachegroup.js?which=                        |
+	+---------------------------+------------------------------------------------------------------------------------------------+
+	| deliveryservice_graph_url | https://<grafanaHost>/dashboard/script/traffic_ops_devliveryservice.js?which=                  |
+	+---------------------------+------------------------------------------------------------------------------------------------+
+	| server_graph_url          | https://<grafanaHost>/dashboard/script/traffic_ops_server.js?which=                            |
+	+---------------------------+------------------------------------------------------------------------------------------------+
+	| visual_status_panel_1     | https://<grafanaHost>/dashboard-solo/db/cdn-stats?panelId=2&fullscreen&from=now-24h&to=now-60s |
+	+---------------------------+------------------------------------------------------------------------------------------------+
+	| visual_status_panel_2     | https://<grafanaHost>/dashboard-solo/db/cdn-stats?panelId=1&fullscreen&from=now-24h&to=now-60s |
+	+---------------------------+------------------------------------------------------------------------------------------------+
+	| daily_bw_url              | https://<grafanaHost>/dashboard-solo/db/daily-summary?panelId=1&fullscreen&from=now-3y&to=now  |
+	+---------------------------+------------------------------------------------------------------------------------------------+
+	| daily_served_url          | https://<grafanaHost>/dashboard-solo/db/daily-summary?panelId=2&fullscreen&from=now-3y&to=now  |
+	+---------------------------+------------------------------------------------------------------------------------------------+
+
+InfluxDb Tools
+=========================
+
+Under the Traffic Stats source directory there is a directory called influxdb_tools.  These tools are meant to be used as one-off scripts to help a user quickly get new databases and continuous queries setup in influxdb.
+They are specific for traffic stats and are not meant to be generic to influxdb.  Below is an brief description of each script along with how to use it.
+
+**create_ts_databases**
+	This script creates all `databases <https://docs.influxdata.com/influxdb/latest/concepts/key_concepts/#database>`_, `retention policies <https://docs.influxdata.com/influxdb/latest/concepts/key_concepts/#retention-policy>`_, and `continuous queries <https://docs.influxdata.com/influxdb/v0.11/query_language/continuous_queries/>`_ required by traffic stats.
+
+	**How to use create_ts_databases:**
+
+	Pre-Requisites:
+
+		1. Go 1.4 or later
+		2. configured $GOPATH (e.g. export GOPATH=~/go)
+
+	Using create_ts_databases.go
+
+		1. go get github.com/influxdata/influxdb
+
+		2. go build create_ts_databases.go
+
+		3. Run it:
+			- ./create_ts_databases -help
+			- optional flags:
+				- influxUrl -  The influxdb url and port
+				- replication -  The number of nodes in the cluster
+				- user - The user to use
+				- password - The password to use
+			- example: ./create_ts_databases -influxUrl=localhost:8086 -replication=3 -user=joe -password=mysecret
+
+**sync_ts_databases**
+	This script is used to sync one influxdb environment to another.  Only data from continuous queries is synced as it is downsampled data and much smaller in size than syncing raw data.  Possible use cases are syncing from Production to Development or Syncing a new cluster once brought online.
+
+	**How to use sync_ts_databases:**
+
+	Pre-Requisites:
+
+		1. Go 1.4 or later
+		2. configured $GOPATH (e.g. export GOPATH=~/go)
+
+	Using sync_ts_databases.go:
+
+		1. go get github.com/influxdata/influxdb
+
+		2. go build sync_ts_databases.go
+
+		3. Run it
+			- ./sync_ts_databases -help
+			- required flags:
+				- sourceUrl - The URL of the source database
+				- targetUrl - The URL of the target database
+
+			-optional flags:
+				- database - The database to sync (default = sync all databases)
+				- days - Days in the past to sync (default = sync all data)
+				- sourceUser - The user of the source database
+				- sourcePass - The password for the source database
+				- targetUser - The user of the target database
+				- targetPass - The password for the target database
+
+			- example: ./sync_ts_databases -sourceUrl=http://influxdb-production-01.kabletown.net:8086 -targetUrl=http://influxdb-dev-01.kabletown.net:8086 -database=cache_stats -days=7 -sourceUser=joe sourcePass=mysecret
+
diff --git a/docs/1.8.0/_sources/admin/traffic_vault.txt b/docs/1.8.0/_sources/admin/traffic_vault.txt
new file mode 100644
index 0000000..35be160
--- /dev/null
+++ b/docs/1.8.0/_sources/admin/traffic_vault.txt
@@ -0,0 +1,195 @@
+..
+..
+.. 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 Vault Administration
+****************************
+Installing Traffic Vault
+========================
+In order to successfully store private keys you will need to install Riak.
+The latest version of Riak can be downloaded on the Riak `website <http://docs.basho.com/riak/latest/downloads/>`_.
+The installation instructions for Riak can be found `here <http://docs.basho.com/riak/latest/ops/building/installing/>`_.
+
+Production is currently running version 2.0.5 of Riak, but the latest version should suffice.
+
+
+Configuring Traffic Vault
+=========================
+The following steps were taken to configure Riak in our environments.
+
+Riak configuration file configuration
+-------------------------------------
+
+The following steps need to be performed on each Riak server in the cluster:
+
+* Log into riak server as root
+
+* cd to /etc/riak/
+
+* Update the following in riak.conf to reflect your IP:
+	- nodename = riak@a-host.sys.kabletown.net
+	- listener.http.internal = a-host.sys.kabletown.net:8098 (can be 80 - This endpoint will not work with sec enabled)
+	- listener.protobuf.internal = a-host.sys.kabletown.net:8087 (can be different port if you want)
+	- listener.https.internal = a-host.sys.kabletown.net:8088 (can be 443)
+
+* Updated the following conf file to point to your cert files
+	- ssl.certfile = /etc/riak/certs/server.crt
+	- ssl.keyfile = /etc/riak/certs/server.key
+	- ssl.cacertfile = /etc/pki/tls/certs/ca-bundle.crt
+
+* Add a line at the bottom of the config for tlsv1
+	- tls_protocols.tlsv1 = on
+
+* Once the config file has been updated restart riak
+	- ``/etc/init.d/riak restart``
+
+* Validate server is running by going to the following URL:
+ 	- https://<serverHostname>:8088/ping
+
+Riak-admin configuration
+-------------------------
+
+Riak-admin is a command line utility that needs to be run as root on a server in the riak cluster.
+
+Assumptions:
+	* Riak 2.0.2 or greater is installed
+	* SSL Certificates have been generated (signed or self-signed)
+	* Root access to riak servers
+
+Add admin user and riakuser to riak
+	* Admin user will be a super user
+	* Riakuser will be the application user
+
+Login to one of the riak servers in the cluster as root (any will do)
+
+	1. Enable security
+
+		``riak-admin security enable``
+
+	2. Add groups
+
+		``riak-admin security add-group admins``
+
+		``riak-admin security add-group keysusers``
+	3. Add users
+
+	 .. Note:: username and password should be stored in /opt/traffic_ops/app/conf/<environment>/riak.conf
+	 ..
+
+		``riak-admin security add-user admin password=<AdminPassword> groups=admins``
+
+		``riak-admin security add-user riakuser password=<RiakUserPassword> groups=keysusers``
+
+	4. Grant access for admin and riakuser
+
+		``riak-admin security add-source riakuser 0.0.0.0/0 password``
+
+		``riak-admin security add-source admin 0.0.0.0/0 password``
+
+	5. Grant privs to admins for everything
+
+		``riak-admin security grant riak_kv.list_buckets,riak_kv.list_keys,riak_kv.get,riak_kv.put,riak_kv.delete on any to admins``
+
+	6. Grant privs to keysuser for ssl, dnssec, and url_sig_keys buckets only
+
+		``riak-admin security grant riak_kv.get,riak_kv.put,riak_kv.delete on default ssl to keysusers``
+
+		``riak-admin security grant riak_kv.get,riak_kv.put,riak_kv.delete on default dnssec to keysusers``
+
+		``riak-admin security grant riak_kv.get,riak_kv.put,riak_kv.delete on default url_sig_keys to keysusers``
+
+.. seealso:: For more information on security in Riak, see the `Riak Security documentation <http://docs.basho.com/riak/2.0.4/ops/advanced/security/>`_.
+.. seealso:: For more information on authentication and authorization in Riak, see the `Riak Authentication and Authorization documentation <http://docs.basho.com/riak/2.0.4/ops/running/authz/>`_.
+
+
+Traffic Ops Configuration
+-------------------------
+
+There are a couple configurations that are necessary in Traffic Ops.
+
+1. Database Updates
+	* A new profile for Riak needs to be added to the profile table
+	* A new type of Riak needs to be added to the type table
+	* The servers in the Riak cluster need to be added to the server table
+
+	 .. Note:: profile and type data should be pre-loaded by seeds sql script.
+	 ..
+
+2. Configuration updates
+	* /opt/traffic_ops/app/conf/<environment>/riak.conf needs to be updated to reflect the correct username and password for accessing riak.
+
+Configuring Riak Search
+=======================
+
+In order to more effectively support retrieval of SSL certificates by Traffic Router and Traffic Ops ORT, Traffic Vault uses `Riak search <http://docs.basho.com/riak/kv/latest/using/reference/search/>`_.  Riak Search uses `Apache Solr <http://lucene.apache.org/solr>`_ for indexing and searching of records.  The following explains how to enable, configure, and validate Riak Search.
+
+Riak Configuration
+------------------
+
+On Each Riak Server:
+
+1. If java is not already installed on your Riak server, install Java
+	* To see if Java is already installed: ``java -version``
+	* To install Java: ``yum install -y jdk``
+
+2. enable search in riak.conf
+	* ``vim /etc/riak/riak.conf``
+	* look for search and change ``search = off`` to ``search = on``
+
+3. Restart Riak so search is on
+	* ``service riak restart``
+
+One time configuration:
+
+1. **On one of the Riak servers in the cluster run the following riak-admin commands**
+
+``riak-admin security grant search.admin on schema to admin``
+
+``riak-admin security grant search.admin on index to admin``
+
+``riak-admin security grant search.query on index to admin``
+
+``riak-admin security grant search.query on index sslkeys to admin``
+
+``riak-admin security grant search.query on index to riakuser``
+
+``riak-admin security grant search.query on index sslkeys to riakuser``
+
+``riak-admin security grant riak_core.set_bucket on any to admin``
+
+2. Add the search schema to Riak.  This schema is a simple Apache Solr configuration file which will index all records on cdn, hostname, and deliveryservice.
+	* Get the schema file by either cloning the project and going to `traffic_ops/app/config/misc/riak_search` or from `github <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops/app/conf/misc/riak_search>`_.
+	* Use curl to add the schema to riak: ``curl -kvs -XPUT "https://admin:pass@riakserver:8088/search/schema/sslkeys" -H 'Content-Type:application/xml'  -d @sslkeys.xml``
+
+3. Add search index to Riak
+	* run the following curl command:  ``curl -kvs -XPUT "https://admin:pass@riakserver:8088/search/index/sslkeys" -H 'Content-Type: application/json' -d '{"schema":"sslkeys"}'``
+
+4. Associate the sslkeys index to the ssl bucket in Riak
+	* run the following curl command: ``curl -kvs -XPUT "https://admin:pass@riakserver:8088/buckets/ssl/props" -H'content-type:application/json' -d'{"props":{"search_index":"sslkeys"}}'``
+
+Riak Search (using Apache Solr) will now index all NEW records that are added to the "ssl" bucket.  The cdn, deliveryservice, and hostname fields are indexed and when a search is performed riak will return the indexed fields along with the crt and key values for a ssl record.  In order to add the indexed fields to current records and to get the current records added, a standalone script needs to be run.  The following explains how to run the script.
+
+1. Get script from github either by cloning the project and going to `traffic_ops/app/script` or from `here <https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/script/update_riak_for_search.pl>`_
+2. Run the script by performing the following command ``./update_riak_for_search.pl -to_url=https://traffic-ops.kabletown.net -to_un=user -to_pw=password``
+
+Validate the search is working by querying against Riak directly:
+``curl -kvs "https://admin:password@riakserver:8088/search/query/sslkeys?wt=json&q=cdn:mycdn"``
+
+Validation can also be done by querying Traffic Ops:
+``curl -Lvs -H "Cookie: $COOKIE" https://traffic-ops.kabletown.net/api/1.2/cdns/name/mycdn/sslkeys.json``
+
+
+
+
diff --git a/docs/1.8.0/_sources/basics/cache_revalidation.txt b/docs/1.8.0/_sources/basics/cache_revalidation.txt
new file mode 100644
index 0000000..dc57346
--- /dev/null
+++ b/docs/1.8.0/_sources/basics/cache_revalidation.txt
@@ -0,0 +1,71 @@
+.. 
+.. 
+.. 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::
+	Cache Control Header
+	Revalidation
+	HTTP 304
+	
+Cache Control Headers and Revalidation
+======================================
+The `HTTP/1.1 spec <https://www.ietf.org/rfc/rfc2616.txt>`_ allows for origin servers and clients to influence how caches treat their requests and responses. By default, the Traffic Control CDN will honor cache control headers. Most commonly, origin servers will tell the downstream caches how long a response can be cached::
+
+  HTTP/1.1 200 OK
+  Date: Sun, 14 Dec 2014 23:22:44 GMT
+  Server: Apache/2.2.15 (Red Hat)
+  Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+  ETag: "1aa008f-2d-50a3559482cc0"
+  Cache-Control: max-age=86400
+  Content-Length: 45
+  Connection: close
+  Content-Type: text/html; charset=UTF-8
+
+  <html><body>This is a fun file</body></html>
+
+In the above response, the origin server tells downstream caching systems that the maximum time to cache this response for is 86400 seconds. The origin can also add a ``Expires:`` header, explicitly telling the cache the time this response is to be expired. When a response is expired it usually doesn't get deleted from the cache, but, when a request comes in that would have hit on this response if it was not expired, the cache *revalidates* the response. In stead of requesting the object again from the origin server, the cache will send a request to the origin indicating what version of the response it has, and asking if it has changed. If it changed, the server will send a ``200 OK`` response, with the new data. If it has not changed, the origin server will send back a ``304 Not Modified`` response indicating the response is still valid, and that the cache can reset the timer on the response expiration. To indicate what version the client (cache) has it will add an ``If-Not-Modified-Since:`` header, or an ``If-None-Match:`` header.  For example, in the ``If-None-Match:`` case, the origin will send and ``ETag`` header that uniquely identifies the response. The client can use that in an revalidation request like::
+
+	GET /foo/bar/fun.html HTTP/1.1
+	If-None-Match: "1aa008f-2d-50a3559482cc0"
+	Host: www.origin.com
+
+If the content has changed (meaning, the new response would not have had the same ETag) it will respond with ``200 OK``, like::
+
+  HTTP/1.1 200 OK
+  Date: Sun, 18 Dec 2014 3:22:44 GMT
+  Server: Apache/2.2.15 (Red Hat)
+  Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+  ETag: "1aa008f-2d-50aa00feadd"
+  Cache-Control: max-age=604800
+  Content-Length: 49
+  Connection: close
+  Content-Type: text/html; charset=UTF-8
+
+  <html><body>This is NOT a fun file</body></html>
+
+
+If the Content did not change (meaning, the response would have had the same ETag) it will respond with ``304 Not Modified``, like::
+
+  304 Not Modified
+  Date: Sun, 18 Dec 2014 3:22:44 GMT
+  Server: Apache/2.2.15 (Red Hat)
+  Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+  ETag: "1aa008f-2d-50a3559482cc0"
+  Cache-Control: max-age=604800
+  Content-Length: 45
+  Connection: close
+  Content-Type: text/html; charset=UTF-8
+
+Note that the 304 response only has headers, not the data.
+ 
\ No newline at end of file
diff --git a/docs/1.8.0/_sources/basics/caching_proxies.txt b/docs/1.8.0/_sources/basics/caching_proxies.txt
new file mode 100644
index 0000000..af93730
--- /dev/null
+++ b/docs/1.8.0/_sources/basics/caching_proxies.txt
@@ -0,0 +1,238 @@
+.. 
+.. 
+.. 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.
+.. 
+
+
+.. |arrow| image:: fwda.png
+
+.. _rl-caching_proxy:
+
+Caching Proxies
+===============
+The main function of a CDN is to proxy requests from clients to origin servers 
+and cache the results. 
+To proxy, in the CDN context, is to obtain content using HTTP from an origin 
+server on behalf of a client. To cache is to store the results so they can be 
+reused when other clients are requesting the same content. There are three 
+types of proxies in use on the Internet today which are described below.
+
+.. index::
+  Reverse Proxy
+
+.. _rl-rev-proxy:
+
+|arrow| Reverse Proxy
+---------------------
+  A reverse proxy acts on behalf of the origin server. The client is mostly unaware it is communicating with a proxy and not the actual origin. 
+  All EDGE caches in a Traffic Control CDN are reverse proxies. 
+  To the end user a Traffic Control based CDN appears as a reverse proxy since 
+  it retrieves content from the origin server, acting on behalf of that origin server. The client requests a URL that has 
+  a hostname which resolves to the reverse proxy's IP address and, in compliance 
+  with the HTTP 1.1 specification, the client sends a ``Host:`` header to the reverse 
+  proxy that matches the hostname in the URL. 
+  The proxy looks up this hostname in a 
+  list of mappings to find the origin hostname; if the hostname of the Host header is not found in the list, 
+  the proxy will send an error (``404 Not Found``) to the client. 
+  If the supplied hostname is found in this list of mappings, the proxy checks the cache, and when the content is not already present, connects to the 
+  origin the requested ``Host:`` maps to and requests the path of the original URL, providing the origin hostname in the ``Host`` header.  The proxy then stores the URL in cache and serves the contents to the client. When there are subsequent requests for 
+  the same URL, a caching proxy serves the content out of cache thereby reducing 
+  latency and network traffic.
+
+.. seealso:: `ATS documentation on reverse proxy <https://docs.trafficserver.apache.org/en/latest/admin/reverse-proxy-http-redirects.en.html#http-reverse-proxy>`_.
+
+To insert a reverse proxy into the previous HTTP 1.1 example, the reverse proxy requires provisioning 
+for ``www.origin.com``. By adding a remap rule to the cache, the reverse proxy then maps requests to 
+this origin. The content owner must inform the clients, by updating the URL, to receive the content 
+from the cache and not from the origin server directly. For this example, the remap rule on the 
+cache is: ``http://www-origin-cache.cdn.com http://www.origin.com``.
+
+..  Note:: In the previous example minimal headers were shown on both the request and response. In the examples that follow, the origin server response is more realistic. 
+
+::
+
+  HTTP/1.1 200 OK
+  Date: Sun, 14 Dec 2014 23:22:44 GMT
+  Server: Apache/2.2.15 (Red Hat)
+  Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+  ETag: "1aa008f-2d-50a3559482cc0"
+  Content-Length: 45
+  Connection: close
+  Content-Type: text/html; charset=UTF-8
+
+  <html><body>This is a fun file</body></html>
+
+The client is given the URL ``http://www-origin-cache.cdn.com/foo/bar/fun.html`` (note the different hostname) and when attempting to obtain that URL, the following occurs:
+
+1. The client sends a request to the LDNS server to resolve the name ``www-origin-cache.cdn.com`` to an IPv4 address.
+
+2. Similar to the previous case, the LDNS server resolves the name ``www-origin-cache.cdn.com`` to an IPv4 address, in this example, this address is 55.44.33.22.
+
+3. The client opens a TCP connection from a random port locally, to port 80 (the HTTP default) on 55.44.33.22, and sends the following: ::
+
+    GET /foo/bar/fun.html HTTP/1.1
+    Host: www-origin-cache.cdn.com
+
+4. The reverse proxy looks up ``www-origin-cache.cdn.com`` in its remap rules, and finds the origin is ``www.origin.com``.
+
+5. The proxy checks its cache to see if the response for ``http://www-origin-cache.cdn.com/foo/bar/fun.html`` is already in the cache.
+
+6a. If the response is not in the cache:
+
+  1. The proxy uses DNS to get the IPv4 address for ``www.origin.com``, connect to it on port 80, and sends: ::
+
+   	GET /foo/bar/fun.html HTTP/1.1
+   	Host: www.origin.com
+
+  2. The origin server responds with the headers and content as shown: ::
+
+      HTTP/1.1 200 OK
+      Date: Sun, 14 Dec 2014 23:22:44 GMT
+      Server: Apache/2.2.15 (Red Hat)
+      Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+      ETag: "1aa008f-2d-50a3559482cc0"
+      Content-Length: 45
+      Connection: close
+      Content-Type: text/html; charset=UTF-8
+
+      <html><body>This is a fun file</body></html>
+
+  3. The proxy sends the origin response on to the client adding a ``Via:`` header (and maybe others): ::
+
+      HTTP/1.1 200 OK
+      Date: Sun, 14 Dec 2014 23:22:44 GMT
+      Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+      ETag: "1aa008f-2d-50a3559482cc0"
+      Content-Length: 45
+      Connection: close
+      Content-Type: text/html; charset=UTF-8
+      Age: 0
+      Via: http/1.1 cache01.cdn.kabletown.net (ApacheTrafficServer/4.2.1 [uScSsSfUpSeN:t cCSi p sS])
+      Server: ATS/4.2.1
+
+    	<html><body>This is a fun file</body></html>
+
+6b. If it *is* in the cache:
+ 
+  The proxy responds to the client with the previously retrieved result: ::
+
+      HTTP/1.1 200 OK
+      Date: Sun, 14 Dec 2014 23:22:44 GMT
+      Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+      ETag: "1aa008f-2d-50a3559482cc0"
+      Content-Length: 45
+      Connection: close
+      Content-Type: text/html; charset=UTF-8
+      Age: 39711
+      Via: http/1.1 cache01.cdn.kabletown.net (ApacheTrafficServer/4.2.1 [uScSsSfUpSeN:t cCSi p sS])
+      Server: ATS/4.2.1
+
+      <html><body>This is a fun file</body></html>
+
+
+.. index::
+  Forward Proxy
+
+.. _rl-fwd-proxy:
+
+|arrow| Forward Proxy
+---------------------
+  A forward proxy acts on behalf of the client. The origin server is mostly 
+  unaware of the proxy, the client requests the proxy to retrieve content from a 
+  particular origin server. All MID caches in a Traffic Control based CDN are 
+  forward proxies. In a forward proxy scenario, the client is explicitely configured  to use the
+  the proxy's IP address and port as a forward proxy. The client always connects to the forward 
+  proxy for content. The content provider does not have to change the URL the 
+  client obtains, and is unaware of the proxy in the middle. 
+
+..  seealso:: `ATS documentation on forward proxy <https://docs.trafficserver.apache.org/en/latest/admin/forward-proxy.en.html>`_.
+
+Below is an example of the client retrieving the URL ``http://www.origin.com/foo/bar/fun.html`` through a forward proxy:
+
+1. The client requires configuration to use the proxy, as opposed to the reverse proxy example. Assume the client configuration is through preferences entries or other to use the proxy IP address 99.88.77.66 and proxy port 8080.
+
+2. To retrieve ``http://www.origin.com/foo/bar/fun.html`` URL, the client connects to 99.88.77.66 on port 8080 and sends: 
+ 
+ ::
+
+  GET http://www.origin.com/foo/bar/fun.html HTTP/1.1
+
+
+ ..  Note:: In this case, the client places the entire URL after GET, including protocol and hostname (``http://www.origin.com``),  but in the reverse proxy and direct-to-origin case it  puts only the path portion of the URL (``/foo/bar/fun.html``) after the GET. 
+
+3. The proxy verifies whether the response for ``http://www-origin-cache.cdn.com/foo/bar/fun.html`` is already in the cache.
+
+4a. If it is not in the cache:
+
+  1. The proxy uses DNS to obtain the IPv4 address for ``www.origin.com``, connects to it on port 80, and sends: ::
+
+
+      GET /foo/bar/fun.html HTTP/1.1
+      Host: www.origin.com
+
+
+  2. The origin server responds with the headers and content as shown below: ::
+
+
+      HTTP/1.1 200 OK
+      Date: Sun, 14 Dec 2014 23:22:44 GMT
+      Server: Apache/2.2.15 (Red Hat)
+      Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+      ETag: "1aa008f-2d-50a3559482cc0"
+      Content-Length: 45
+      Connection: close
+      Content-Type: text/html; charset=UTF-8
+
+      <html><body>This is a fun file</body></html>
+
+
+  3. The proxy sends this on to the client adding a ``Via:`` header (and maybe others): ::
+
+      HTTP/1.1 200 OK
+      Date: Sun, 14 Dec 2014 23:22:44 GMT
+      Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+      ETag: "1aa008f-2d-50a3559482cc0"
+      Content-Length: 45
+      Connection: close
+      Content-Type: text/html; charset=UTF-8
+      Age: 0
+      Via: http/1.1 cache01.cdn.kabletown.net (ApacheTrafficServer/4.2.1 [uScSsSfUpSeN:t cCSi p sS])
+      Server: ATS/4.2.1
+          
+      <html><body>This is a fun file</body></html>
+
+
+4b. If it *is* in the cache:
+ 
+  The proxy responds to the client with the previously retrieved result: ::
+
+    HTTP/1.1 200 OK
+    Date: Sun, 14 Dec 2014 23:22:44 GMT
+    Last-Modified: Sun, 14 Dec 2014 23:18:51 GMT
+    ETag: "1aa008f-2d-50a3559482cc0"
+    Content-Length: 45
+    Connection: close
+    Content-Type: text/html; charset=UTF-8
+    Age: 99711
+    Via: http/1.1 cache01.cdn.kabletown.net (ApacheTrafficServer/4.2.1 [uScSsSfUpSeN:t cCSi p sS])
+    Server: ATS/4.2.1
+          
+    <html><body>This is a fun file</body></html>
+
+.. index::
+  Transparent Proxy
+  
+|arrow| Transparent Proxy 
+-------------------------
+  Neither the origin nor the client are aware of the actions performed by the transparent proxies. A Traffic Control based CDN does not use transparent proxies.   If you are interested you can learn more about transparent proxies on `wikipedia <http://en.wikipedia.org/wiki/Proxy_server#Transparent_proxy>`_.
+
diff --git a/docs/1.8.0/_sources/basics/content_delivery_networks.txt b/docs/1.8.0/_sources/basics/content_delivery_networks.txt
new file mode 100644
index 0000000..872018e
--- /dev/null
+++ b/docs/1.8.0/_sources/basics/content_delivery_networks.txt
@@ -0,0 +1,40 @@
+.. 
+.. 
+.. 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::
+	Log File Analysis
+	CDN
+	Content Delivery Network 
+
+Content Delivery Networks
+=========================
+The vast majority of today's Internet traffic is media files (often video or audio) being sent from a single source (the *Content Provider*) to many thousands or even millions of destinations (the *Content Consumers*).  Content Delivery Networks are the technology that make that one-to-many distribution possible in an economical way. A Content Delivery Network (CDN) is a distributed system of servers for delivering content over HTTP. These servers are deployed in multiple locations with the goal of optimizing the delivery of content to the end users, while minimizing the traffic on the network. A CDN typically consists of the following:
+
+* **Caching Proxies**
+	The proxy (cache or caching proxy) is a server that both proxies the requests and caches the results for reusing.  
+
+* **Content Router**
+    The Content Router ensures that the end user is connected to the optimal cache for the location of the end user and content availability.
+
+* **Health Protocol** 
+    The Health Protocol monitors the usage of the caches and tenants in the CDN.
+
+* **Configuration Management System** 
+    In many cases a CDN encompasses hundreds of servers across a large geographic area. The Configuration Management System allows an operator to manage these servers.
+
+* **Log File Analysis System**
+    Every transaction in the CDN gets logged. The Log File Analysis System aggregates all of the log entries from all of the servers to a central location for analysis and troubleshooting.
+
+
diff --git a/docs/1.8.0/_sources/basics/http_11.txt b/docs/1.8.0/_sources/basics/http_11.txt
new file mode 100644
index 0000000..65d6d71
--- /dev/null
+++ b/docs/1.8.0/_sources/basics/http_11.txt
@@ -0,0 +1,48 @@
+.. 
+.. 
+.. 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::
+	http/1.1
+	HTTP
+
+HTTP 1.1
+========
+For a comprehensive look at Traffic Control, it is important to understand basic HTTP 1.1 protocol operations and how caches function. The example below illustrates the fulfillment of an HTTP 1.1 request in a situation without CDN or proxy, followed by viewing the changes after inserting different types of (caching) proxies. Several of the examples below are simplified for clarification of the essentials.
+
+For complete details on HTTP 1.1 see `RFC 2616 - Hypertext Transfer Protocol -- HTTP/1.1 <https://www.ietf.org/rfc/rfc2616.txt>`_.
+
+Below are the steps of a client retrieving the URL ``http://www.origin.com/foo/bar/fun.html`` using HTTP/1.1 without proxies:
+
+1. The client sends a request to the Local DNS (LDNS) server to resolve the name ``www.origin.com`` to an IPv4 address.
+
+2. If the LDNS does not have this name (IPv4 mapping cached), it sends DNS requests to the ., .com, and .origin.com authoritative servers until it receives a response with the address for ``www.origin.com``. Per the DNS SPEC, this response has a Time To Live (TTL), which indicates how long this mapping can be cached at the LDNS server. In the example, the IP address found by the LDNS server for www.origin.com is 44.33.22.11.
+
+  .. Note:: While longer DNS TTLs of a day (86400 seconds) or more are quite common in other use cases, in CDN use cases DNS TTLs are often below a minute.
+
+3. The client opens a TCP connection from a random port locally to port 80 (the HTTP default) on 44.33.22.11, and sends this (showing the minimum HTTP 1.1 request, typically there are additional headers): ::
+
+    GET /foo/bar/fun.html HTTP/1.1
+    Host: www.origin.com
+
+4. The server at ``www.origin.com`` looks up the Host: header to match that to a configuration section, usually referred to as a virtual host section. If the Host: header and configuration section match, the search continues for the content of the path ``/foo/bar/fun.html``, in the example, this is a file that contains ``<html><body>This is a fun file</body></html>``, so the server responds with the following: ::
+
+
+      HTTP/1.1 200 OK
+      Content-Type: text/html; charset=UTF-8
+      Content-Length: 45
+
+      <html><body>This is a fun file</body></html>
+
+ At this point, HTTP transaction is complete.
diff --git a/docs/1.8.0/_sources/basics/index.txt b/docs/1.8.0/_sources/basics/index.txt
new file mode 100644
index 0000000..23ee1da
--- /dev/null
+++ b/docs/1.8.0/_sources/basics/index.txt
@@ -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.
+.. 
+
+CDN Basics
+**********
+
+Traffic Control is a CDN control plane, see the topics below to familiarize yourself with the basic concepts of a CDN.
+
+.. toctree::
+  :maxdepth: 2
+
+  content_delivery_networks
+  http_11
+  caching_proxies
+  cache_revalidation
+
+
diff --git a/docs/1.8.0/_sources/development/index.txt b/docs/1.8.0/_sources/development/index.txt
new file mode 100644
index 0000000..851e463
--- /dev/null
+++ b/docs/1.8.0/_sources/development/index.txt
@@ -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.
+.. 
+
+Developer's Guide
+*****************
+Use this guide to start developing applications that consume the Traffic Control APIs, to create extensions to Traffic Ops, or work on Traffic Control itself.
+
+.. toctree::
+  :maxdepth: 2
+
+  traffic_ops
+  traffic_portal
+  traffic_router
+  traffic_monitor
+  traffic_stats
+  traffic_server
+
diff --git a/docs/1.8.0/_sources/development/traffic_monitor.txt b/docs/1.8.0/_sources/development/traffic_monitor.txt
new file mode 100644
index 0000000..012cbb3
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_monitor.txt
@@ -0,0 +1,112 @@
+.. 
+.. 
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+.. 
+..     http://www.apache.org/licenses/LICENSE-2.0
+.. 
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+.. 
+
+Traffic Monitor
+***************
+Introduction
+============
+Traffic Monitor is a Java Tomcat application that monitors caches, provides health state information to Traffic Router, and collects statistics for use in tools such as Traffic Ops and Traffic Stats.  The health state provided by Traffic Monitor is used by Traffic Router to control which caches are available on the CDN.
+
+Software Requirements
+=====================
+To work on Traffic Monitor you need a \*nix (MacOS and Linux are most commonly used) environment that has the following installed:
+
+* Eclipse >= Kepler SR2 (or another Java IDE)
+* Maven >= 3.3.1
+* JDK >= 6.0
+
+Traffic Monitor Project Tree Overview
+=====================================
+* ``traffic_control/traffic_monitor/`` - base directory for Traffic Monitor
+
+	* ``etc/`` - Miscellaneous simulator utilities
+	* ``src/main`` - Main source directory for the Traffic Monitor
+
+		* ``bin/`` - Configuration tools
+		* ``conf/`` - Configuration files
+		* ``java/`` - Java source code for Traffic Monitor
+		* ``opt/tomcat/conf`` - Contains Tomcat configuration file(s) pulled in during an RPM build
+		* ``resources/`` - Resources pulled in during an RPM build
+		* ``scripts/`` - Scripts used by the RPM build process
+		* ``webapp/`` - Java webapp resources
+
+	* ``src/test`` - Test source directory for Traffic Monitor
+
+		* ``java/`` - JUnit based unit tests for Traffic Monitor
+		* ``resources/conf`` - Configuration files used by unit tests
+		* ``resources/db`` - Files downloaded by unit tests
+		* ``resources/var`` - Files generated by unit tests
+
+Java Formatting Conventions 
+===========================
+None at this time.  The codebase will eventually be formatted per Java standards.
+
+Installing The Developer Environment
+====================================
+To install the Traffic Monitor Developer environment:
+
+1. Clone the traffic_control repository using Git.
+2. Change directories into ``traffic_control/traffic_monitor``.
+3. Edit the following parameters in src/test/resources/conf/traffic_monitor_config.js:
+
++-----------------+------------------------------------------------------------+
+|    Parameter    |                           Value                            |
++=================+============================================================+
+| ``tm.hostname`` | FQDN of the Traffic Ops instance (do not include http://). |
++-----------------+------------------------------------------------------------+
+| ``tm.username`` | Admin username for Traffic Ops                             |
++-----------------+------------------------------------------------------------+
+| ``tm.password`` | Password for admin user                                    |
++-----------------+------------------------------------------------------------+
+| ``cdnName``     | Name of the CDN this Traffic Monitor will monitor          |
++-----------------+------------------------------------------------------------+
+
+4. Import the existing git repo into Eclipse:
+
+	a. File -> Import -> Git -> Projects from Git; Next
+	b. Existing local repository; Next
+	c. Add -> browse to find ``traffic_control``; Add
+	d. Select ``traffic_control``; Next
+	e. Ensure "Import existing projects" is selected, expand ``traffic_control``, select ``traffic_monitor``; Next
+	f. Ensure ``traffic_monitor`` is checked; Finish
+	g. Ensure ``traffic_monitor`` has been opened by Eclipse after importing
+
+5. Run ``mvn clean verify`` from the ``traffic_monitor`` directory
+
+6. Start the embedded Jetty instance from within Eclipse
+
+	a. In the package explorer, expand ``traffic_monitor``
+	b. Expand ``src/test/java``
+	c. Expand the package ``com.comcast.cdn.traffic_control.traffic_monitor``
+	d. Open and run ``Start.java``
+
+		..  Note:: If an error is displayed in the Console, run ``mvn clean verify`` from the ``traffic_monitor`` directory
+
+	e. With a web browser, navigate to http://localhost:8080
+
+Test Cases
+==========
+Unit tests can be executed using Maven by running ``mvn test`` at the root of the ``traffic_monitor`` project.
+
+API
+===
+
+:ref:`reference-tm-api`
+
+.. toctree:: 
+  :hidden:
+  :maxdepth: 1
+
+  traffic_monitor/traffic_monitor_api
\ No newline at end of file
diff --git a/docs/1.8.0/_sources/development/traffic_monitor/traffic_monitor_api.txt b/docs/1.8.0/_sources/development/traffic_monitor/traffic_monitor_api.txt
new file mode 100644
index 0000000..0240fd4
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_monitor/traffic_monitor_api.txt
@@ -0,0 +1,178 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _reference-tm-api:
+
+Traffic Monitor APIs
+====================
+The Traffic Monitor URLs below allow certain query parameters for use in controlling the data returned. The optional query parameters are the *tabbed* in values under each URL, if they exist.
+
+|
+
+**/publish/EventLog**
+
+Log of recent events.
+
+|
+
+**/publish/CacheStats**
+
+Statistics gathered for each cache.
+
+**Query Parameters**
+
++--------------+---------+------------------------------------------------+
+|  Parameter   | Type    |                  Description                   |
++==============+=========+================================================+
+| ``hc``       | int     | The history count, number of items to display. |
++--------------+---------+------------------------------------------------+
+| ``stats``    | string  | A comma separated list of stats to display.    |
++--------------+---------+------------------------------------------------+
+| ``wildcard`` | boolean | Controls whether specified stats should be     |
+|              |         | treated as partial strings.                    |
++--------------+---------+------------------------------------------------+
+
+|
+
+**/publish/CacheStats/:cache**
+
+Statistics gathered for only this cache.
+
+**Query Parameters**
+
++--------------+---------+------------------------------------------------+
+|  Parameter   | Type    |                  Description                   |
++==============+=========+================================================+
+| ``hc``       | int     | The history count, number of items to display. |
++--------------+---------+------------------------------------------------+
+| ``stats``    | string  | A comma separated list of stats to display.    |
++--------------+---------+------------------------------------------------+
+| ``wildcard`` | boolean | Controls whether specified stats should be     |
+|              |         | treated as partial strings.                    |
++--------------+---------+------------------------------------------------+
+
+|
+
+**/publish/DsStats**
+
+Statistics gathered for delivery services.
+
+**Query Parameters**
+
++--------------+---------+------------------------------------------------+
+|  Parameter   | Type    |                  Description                   |
++==============+=========+================================================+
+| ``hc``       | int     | The history count, number of items to display. |
++--------------+---------+------------------------------------------------+
+| ``stats``    | string  | A comma separated list of stats to display.    |
++--------------+---------+------------------------------------------------+
+| ``wildcard`` | boolean | Controls whether specified stats should be     |
+|              |         | treated as partial strings.                    |
++--------------+---------+------------------------------------------------+
+
+|
+
+**/publish/DsStats/:deliveryService**
+
+Statistics gathered for this delivery service only.
+
+**Query Parameters**
+
++--------------+---------+------------------------------------------------+
+|  Parameter   | Type    |                  Description                   |
++==============+=========+================================================+
+| ``hc``       | int     | The history count, number of items to display. |
++--------------+---------+------------------------------------------------+
+| ``stats``    | string  | A comma separated list of stats to display.    |
++--------------+---------+------------------------------------------------+
+| ``wildcard`` | boolean | Controls whether specified stats should be     |
+|              |         | treated as partial strings.                    |
++--------------+---------+------------------------------------------------+
+
+|
+
+**/publish/CrStates**
+
+The current state of this CDN per the health protocol.
+
+|
+
+**raw**
+
+The current state of this CDN per this Traffic Monitor only.
+
+|
+
+**/publish/CrConfig**
+
+The CrConfig served to and consumed by Traffic Router.
+
+|
+
+**/publish/PeerStates**
+
+The health state information from all peer Traffic Monitors.
+
+**Query Parameters**
+
++--------------+---------+------------------------------------------------+
+|  Parameter   | Type    |                  Description                   |
++==============+=========+================================================+
+| ``hc``       | int     | The history count, number of items to display. |
++--------------+---------+------------------------------------------------+
+| ``stats``    | string  | A comma separated list of stats to display.    |
++--------------+---------+------------------------------------------------+
+| ``wildcard`` | boolean | Controls whether specified stats should be     |
+|              |         | treated as partial strings.                    |
++--------------+---------+------------------------------------------------+
+
+|
+
+**/publish/Stats**
+
+The general statistics about Traffic Monitor.
+
+|
+
+**/publish/StatSummary**
+
+The summary of cache statistics.
+
+**Query Parameters**
+
++---------------+---------+-----------------------------------------------------------+
+|   Parameter   |   Type  |                        Description                        |
++===============+=========+===========================================================+
+| ``startTime`` | number  | Window start. The number of milliseconds since the epoch. |
++---------------+---------+-----------------------------------------------------------+
+| ``endTime``   | number  | Window end. The number of milliseconds since the epoch.   |
++---------------+---------+-----------------------------------------------------------+
+| ``hc``        | int     | The history count, number of items to display.            |
++---------------+---------+-----------------------------------------------------------+
+| ``stats``     | string  | A comma separated list of stats to display.               |
++---------------+---------+-----------------------------------------------------------+
+| ``wildcard``  | boolean | Controls whether specified stats should be                |
+|               |         | treated as partial strings.                               |
++---------------+---------+-----------------------------------------------------------+
+| ``cache``     | string  | Summary statistics for just this cache.                   |
++---------------+---------+-----------------------------------------------------------+
+
+|
+
+**/publish/ConfigDoc**
+
+The overview of configuration options.
+
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops.txt b/docs/1.8.0/_sources/development/traffic_ops.txt
new file mode 100644
index 0000000..5ec31e4
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops.txt
@@ -0,0 +1,630 @@
+.. 
+.. 
+.. 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
+***********
+
+Introduction
+============
+Traffic Ops uses a MySql or Postgres database to store the configuration information, and the `Mojolicious framework <http://mojolicio.us/>`_ to generate the user interface and REST APIs. 
+
+Software Requirements
+=====================
+To work on Traffic Ops you need a \*nix (MacOS and Linux are most commonly used) environment that has the following installed:
+
+* `Carton 1.0.12 <http://search.cpan.org/~miyagawa/Carton-v1.0.12/lib/Carton.pm>`_
+
+  * cpan JSON
+  * cpan JSON::PP
+
+* `Go 1.4 <http://golang.org/doc/install>`_
+* Perl 5.10.1
+* Git
+* MySQL 5.1.52
+* `Goose <https://bitbucket.org/liamstask/goose/>`_
+
+Traffic Ops Project Tree Overview
+=======================================
+
+**/opt/traffic_ops/app**
+
+* bin/ - Directory for scripts, cronjobs, etc
+
+* conf/
+
+  * /development - Development (local) specific config files.
+  * /misc - Miscellaneous config files.
+  * /production - Production specific config files.
+  * /test - Test (unit test) specific config files.
+
+* db/ - Database related area.
+
+  * /migrations - Database Migration files.
+
+* lib/
+
+  * /API - Mojo Controllers for the /API area of the application.
+  * /Common - Common Code between both the API and UI areas.
+  * /Extensions      
+  * Fixtures/ - Test Case fixture data for the 'to_test' database.
+    * /Integration - Integration Tests.
+  * /MojoPlugins - Mojolicious Plugins for Common Controller Code.
+  * Schema/ - Database Schema area.
+    * /Result - DBIx ORM related files.
+  * /Test - Common Test. 
+  * /UI - Mojo Controllers for the Traffic Ops UI itself.
+  * Utils/           
+    * /Helper - Common utilities for the Traffic Ops application.
+
+* log/ - Log directory where the development and test files are written by the app.
+
+* public/
+             
+ * css/ - Stylesheets.
+ * images/ - Images.
+ * js/ - Javascripts
+
+* script/ - Mojo Bootstrap scripts.
+   
+* t/ - Unit Tests for the UI.
+
+ * api/ - Unit Tests for the API.
+
+* t_integration/ - High level tests for Integration level testing.
+
+* templates/ - Mojo Embedded Perl (.ep) files for the UI.
+
+
+
+Perl Formatting Conventions 
+===========================
+Perl tidy is for use in code formatting. See the following config file for formatting conventions.
+
+::
+
+
+  edit a file called $HOME/.perltidyrc
+
+  -l=156
+  -et=4
+  -t
+  -ci=4
+  -st
+  -se
+  -vt=0
+  -cti=0
+  -pt=1
+  -bt=1
+  -sbt=1
+  -bbt=1
+  -nsfs
+  -nolq
+  -otr
+  -aws
+  -wls="= + - / * ."
+  -wrs=\"= + - / * .\"
+  -wbb="% + - * / x != == >= <= =~ < > | & **= += *= &= <<= &&= -= /= |= + >>= ||= .= %= ^= x="
+
+
+Database Management
+===================
+..  Add db naming conventions
+
+The admin.pl script is for use in managing the Traffic Ops database tables. Below is an example of its usage. 
+
+``$ db/admin.pl``
+
+Usage:  db/admin.pl [--env (development|test|production)] [arguments]
+
+Example: ``db/admin.pl --env=test reset``
+
+Purpose:  This script is used to manage the database. The environments are defined in the dbconf.yml, as well as the database names.
+
+* To use the ``admin.pl`` script, you may need to add ``traffic_ops/lib`` and ``traffic_ops/local/lib/perl5`` to your `PERL5LIB <http://modperlbook.org/html/3-9-2-2-Using-the-PERL5LIB-environment-variable.html>`_ environment variable.
+
++-----------+--------------------------------------------------------------------+
+| Arguments | Description                                                        |
++===========+====================================================================+
+| create    | Execute db 'create' the database for the current environment.      |
++-----------+--------------------------------------------------------------------+
+| down      | Roll back a single migration from the current version.             |
++-----------+--------------------------------------------------------------------+
+| drop      | Execute db 'drop' on the database for the current environment.     |
++-----------+--------------------------------------------------------------------+
+| redo      | Roll back the most recently applied migration, then run it again.  |
++-----------+--------------------------------------------------------------------+
+| reset     | Execute db drop, create, load_schema, migrate on the database for  |
+|           | the current environment.                                           |
++-----------+--------------------------------------------------------------------+
+| seed      | Execute SQL from db/seeds.sql for loading static data.             |
++-----------+--------------------------------------------------------------------+
+| setup     | Execute db drop, create, load_schema, migrate, seed on the         |
+|           | database for the current environment.                              |
++-----------+--------------------------------------------------------------------+
+| status    | Print the status of all migrations.                                |
++-----------+--------------------------------------------------------------------+
+| upgrade   | Execute migrate then seed on the database for the current          |
+|           | environment.                                                       |
++-----------+--------------------------------------------------------------------+
+
+Installing The Developer Environment
+====================================
+To install the Traffic Ops Developer environment:
+
+1. Clone the traffic_control repository from `github.com <https://github.com/apache/incubator-trafficcontrol>`_.
+2. Install the local dependencies using Carton (cpanfile).
+
+  ::
+
+   $ cd traffic_ops/app
+   $ carton
+
+3. Set up a user in MySQL.
+
+  Example: :: 
+
+    master $ mysql
+    Welcome to the MySQL monitor.  Commands end with ; or \g.
+    Your MySQL connection id is 305
+    Server version: 5.6.19 Homebrew
+
+    Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.
+
+    Oracle is a registered trademark of Oracle Corporation and/or its
+    affiliates. Other names may be trademarks of their respective
+    owners.
+
+    Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
+
+    mysql> create user 'to_user'@'localhost';
+    mysql> grant all on to_development.* to 'to_user'@'localhost' identified by 'twelve';
+    mysql> grant all on to_test.* to 'to_user'@'localhost' identified by 'twelve';
+    mysql> grant all on to_integration.* to 'to_user'@'localhost' identified by 'twelve';
+
+
+4. Enter ``db/admin.pl --env=<enviroment name> setup`` to set up the traffic_ops database(s). 
+
+   * Unit test database: ``$ db/admin.pl --env=test setup``
+   * Development database: ``$ db/admin.pl --env=development setup``
+   * Integration database: ``$ db/admin.pl --env=integration setup``
+
+   |
+
+   Running the the admin.pl script in setup mode should look like this: ::
+
+       master $ db/admin.pl --env=development setup
+       Using database.conf: conf/development/database.conf
+       Using database.conf: conf/development/database.conf
+       Using database.conf: conf/development/database.conf
+       Using database.conf: conf/development/database.conf
+       Using database.conf: conf/development/database.conf
+       Using database.conf: conf/development/database.conf
+       Executing 'drop database to_development'
+       Executing 'create database to_development'
+       Creating database tables...
+       Warning: Using a password on the command line interface can be insecure.
+       Migrating database...
+       goose: migrating db environment 'development', current version: 0, target: 20150210100000
+       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
+       Seeding database...
+       Warning: Using a password on the command line interface can be insecure.
+
+5. (Optional) To load temporary data into the tables: ``$ perl bin/db/setup_kabletown.pl``
+
+6. Run the postinstall script: ``traffic_ops/install/bin/postinstall``
+
+7. To start Traffic Ops, enter ``$ bin/start.pl``
+
+   The local Traffic Ops instance uses an open source framework called morbo, starting following the start command execution.
+
+   Start up success includes the following:
+
+  ::
+   
+
+   [2015-02-24 10:44:34,991] [INFO] Listening at "http://*:3000".
+   
+   Server available at http://127.0.0.1:3000.
+
+
+8. Using a browser, navigate to the given address: ``http://127.0.0.1:3000``
+9. For the initial log in:
+  
+  * User name: admin
+  * Password: password
+
+10. Change the log in information.
+
+Test Cases
+==========
+Use prove to execute test cases. Execute after a carton install:
+
+* To run the Unit Tests: ``$ local/bin/prove -qrp  t/``
+* To run the Integration Tests: ``$ local/bin/prove -qrp t_integration/``
+
+The KableTown CDN example
+-------------------------
+The integration tests will load an example CDN with most of the features of Traffic Control being used. This is mostly for testing purposes, but can also be used as an example of how to configure certain features. To load the KableTown CDN example and access it:
+
+1. Run the integration tests 
+2. Start morbo against the integration database: ``export MOJO_MODE=integration; ./bin/start.pl``
+3. Using a browser, navigate to the given address: ``http://127.0.0.1:3000``
+4. For the initial log in:
+  
+  * User name: admin
+  * Password: password
+
+
+Extensions
+==========
+Traffic Ops Extensions are a way to enhance the basic functionality of Traffic Ops in a custom manner. There are three types of extensions:
+
+1. Check Extensions
+
+  These allow you to add custom checks to the "Health->Server Checks" view.
+
+2. Configuration Extensions
+
+  These allow you to add custom configuration file generators.
+
+3. Data source Extensions
+
+  These allow you to add statistic sources for the graph views and APIs.
+
+Extensions are managed using the $TO_HOME/bin/extensions command line script. For more information see :ref:`admin-to-ext-script`.
+
+Check Extensions
+----------------
+
+In other words, check extensions are scripts that, after registering with Traffic Ops, have a column reserved in the "Health->Server Checks" view and that usually run periodically out of cron.
+
+.. |checkmark| image:: ../../../traffic_ops/app/public/images/good.png 
+
+.. |X| image:: ../../../traffic_ops/app/public/images/bad.png
+
+
+It is the responsibility of the check extension script to iterate over the servers it wants to check and post the results.
+
+An example script might proceed by logging into the Traffic Ops server using the HTTPS base_url provided on the command line. The script is hardcoded with an auth token that is also provisioned in the Traffic Ops User database. This token allows the script to obtain a cookie used in later communications with the Traffic Ops API. The script then obtains a list of all caches to be polled by accessing Traffic Ops' ``/api/1.1/servers.json`` REST target. This list is walked, running a command to gather the stats from that cache. For some extensions, an HTTP GET request might be made to the ATS astats plugin, while for others the cache might be pinged, or a command run over SSH. The results are then compiled into a numeric or boolean result and the script POSTs tha result back to the Traffic Ops ``/api/1.1/servercheck/`` target.
+
+A check extension can have a column of |checkmark|'s and |X|'s (CHECK_EXTENSION_BOOL) or a column that shows a number (CHECK_EXTENSION_NUM).A simple example of a check extension of type CHECK_EXTENSION_NUM that will show 99.33 for all servers of type EDGE is shown below: :: 
+
+
+  Script here.
+
+Check Extension scripts are located in the $TO_HOME/bin/checks directory.
+
+Currently, the following Check Extensions are available and installed by default:
+
+**Cache Disk Usage Check - CDU**
+  This check shows how much of the available total cache disk is in use. A "warm" cache should show 100.00.
+
+**Cache Hit Ratio Check - CHR**
+  The cache hit ratio for the cache in the last 15 minutes (the interval is determined by the cron entry). 
+
+**DiffServe CodePoint Check - DSCP**
+  Checks if the returning traffic from the cache has the correct DSCP value as assigned in the delivery service. (Some routers will overwrite DSCP)
+
+**Maximum Transmission Check - MTU**
+  Checks if the Traffic Ops host (if that is the one running the check) can send and receive 8192 size packets to the ``ip_address`` of the server in the server table.
+
+**Operational Readiness Check - ORT**
+  See :ref:`reference-traffic-ops-ort` for more information on the ort script. The ORT column shows how many changes the traffic_ops_ort.pl script would apply if it was run. The number in this column should be 0. 
+
+**Ping Check - 10G, ILO, 10G6, FQDN**
+  The bin/checks/ToPingCheck.pl is to check basic IP connectivity, and in the default setup it checks IP connectivity to the following:
+  
+  10G
+    Is the ``ip_address`` (the main IPv4 address) from the server table pingable?
+  ILO
+    Is the ``ilo_ip_address`` (the lights-out-mangement IPv4 address) from the server table pingable?
+  10G6
+    Is the ``ip6_address`` (the main IPv6 address) from the server table pingable?
+  FQDN 
+    Is the Fully Qualified Domain name (the concatenation of ``host_name`` and ``.`` and ``domain_name`` from the server table) pingable?
+
+**Traffic Router Check - RTR**
+  Checks the state of each cache as perceived by all Traffic Monitors (via Traffic Router). This extension asks each Traffic Router for the state of the cache. A check failure is indicated if one or more monitors report an error for a cache. A cache is only marked as good if all reports are positive. (This is a pessimistic approach, opposite of how TM marks a cache as up, "the optimistic approach")
+  
+
+Configuration Extensions
+------------------------
+NOTE: Config Extensions are Beta at this time.
+
+
+Data Source Extensions
+----------------------
+Traffic Ops has the ability to load custom code at runtime that allow any CDN user to build custom APIs for any requirement that Traffic Ops does not fulfill.  There are two classes of Data Source Extensions, private and public.  Private extensions are Traffic Ops extensions that are not publicly available, and should be kept in the /opt/traffic_ops_extensions/private/lib. Public extensions are Traffic Ops extensions that are Open Source in nature and free to enhance or contribute back to the Traffic Ops Open Source project and should be kept in /opt/traffic_ops/app/lib/Extensions.
+
+
+Extensions at Runtime
+---------------------
+The search path for extensions depends on the configuration of the PERL5LIB, which is preconfigured in the Traffic Ops start scripts.  The following directory structure is where Traffic Ops will look for Extensions in this order.
+
+Extension Directories
+---------------------
+PERL5LIB Example Configuration: ::
+
+   export PERL5LIB=/opt/traffic_ops_extensions/private/lib/Extensions:/opt/traffic_ops/app/lib/Extensions/TrafficStats
+
+Perl Package Naming Convention
+------------------------------
+To prevent Extension namespace collisions within Traffic Ops all Extensions should follow the package naming convention below:
+
+Extensions::<ExtensionName>
+
+Data Source Extension Perl package name example
+Extensions::TrafficStats
+Extensions::YourCustomExtension
+
+TrafficOpsRoutes.pm
+-------------------
+Traffic Ops accesses each extension through the addition of a URL route as a custom hook.  These routes will be defined in a file called TrafficOpsRoutes.pm that should live in the top directory of your Extension.  The routes that are defined should follow the Mojolicious route conventions.
+
+
+Development Configuration
+--------------------------
+To incorporate any custom Extensions during development set your PERL5LIB with any number of directories with the understanding that the PERL5LIB search order will come into play, so keep in mind that top-down is how your code will be located.  Once Perl locates your custom route or Perl package/class it 'pins' on that class or Mojo Route and doesn't look any further, which allows for the developer to *override* Traffic Ops functionality.
+
+API
+===
+The Traffic Ops API provides programmatic access to read and write CDN data providing authorized API consumers with the ability to monitor CDN performance and configure CDN settings and parameters.
+
+Response Structure
+------------------
+All successful responses have the following structure: ::
+
+    {
+      "response": <JSON object with main response>,
+    }
+
+To make the documentation easier to read, only the ``<JSON object with main response>`` is documented, even though the response and version fields are always present. 
+
+Using API Endpoints
+-------------------
+1. Authenticate with your Traffic Portal or Traffic Ops user account credentials.
+2. Upon successful user authentication, note the mojolicious cookie value in the response headers. 
+3. Pass the mojolicious cookie value, along with any subsequent calls to an authenticated API endpoint.
+
+Example: ::
+  
+    [jvd@laika ~]$ curl -H "Accept: application/json" http://localhost:3000/api/1.1/usage/asns.json
+    {"alerts":[{"level":"error","text":"Unauthorized, please log in."}]}
+    [jvd@laika ~]$
+    [jvd@laika ~]$ curl -v -H "Accept: application/json" -v -X POST --data '{ "u":"admin", "p":"secret_passwd" }' http://localhost:3000/api/1.1/user/login
+    * Hostname was NOT found in DNS cache
+    *   Trying ::1...
+    * connect to ::1 port 3000 failed: Connection refused
+    *   Trying 127.0.0.1...
+    * Connected to localhost (127.0.0.1) port 3000 (#0)
+    > POST /api/1.1/user/login HTTP/1.1
+    > User-Agent: curl/7.37.1
+    > Host: localhost:3000
+    > Accept: application/json
+    > Content-Length: 32
+    > Content-Type: application/x-www-form-urlencoded
+    >
+    * upload completely sent off: 32 out of 32 bytes
+    < HTTP/1.1 200 OK
+    < Connection: keep-alive
+    < Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
+    < Access-Control-Allow-Origin: http://localhost:8080
+    < Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
+    < Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862; expires=Sun, 19 Apr 2015 00:10:01 GMT; path=/; HttpOnly
+    < Content-Type: application/json
+    < Date: Sat, 18 Apr 2015 20:10:01 GMT
+    < Access-Control-Allow-Credentials: true
+    < Content-Length: 81
+    < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
+    * Server Mojolicious (Perl) is not blacklisted
+    < Server: Mojolicious (Perl)
+    <
+    * Connection #0 to host localhost left intact
+    {"alerts":[{"level":"success","text":"Successfully logged in."}]}
+    [jvd@laika ~]$
+
+    [jvd@laika ~]$ curl -H'Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;' -H "Accept: application/json" http://localhost:3000/api/1.1/asns.json
+    {"response":{"asns":[{"lastUpdated":"2012-09-17 15:41:22", .. asn data deleted ..   ,}
+    [jvd@laika ~]$
+
+API Errors
+----------
+
+**Response Properties**
+
++----------------------+--------+------------------------------------------------+
+| Parameter            | Type   | Description                                    |
++======================+========+================================================+
+|``alerts``            | array  | A collection of alert messages.                |
++----------------------+--------+------------------------------------------------+
+| ``>level``           | string | Success, info, warning or error.               |
++----------------------+--------+------------------------------------------------+
+| ``>text``            | string | Alert message.                                 |
++----------------------+--------+------------------------------------------------+
+
+The 3 most common errors returned by Traffic Ops are:
+
+401 Unauthorized
+  When you don't supply the right cookie, this is the response. :: 
+
+    [jvd@laika ~]$ curl -v -H "Accept: application/json" http://localhost:3000/api/1.1/usage/asns.json
+    * Hostname was NOT found in DNS cache
+    *   Trying ::1...
+    * connect to ::1 port 3000 failed: Connection refused
+    *   Trying 127.0.0.1...
+    * Connected to localhost (127.0.0.1) port 3000 (#0)
+    > GET /api/1.1/usage/asns.json HTTP/1.1
+    > User-Agent: curl/7.37.1
+    > Host: localhost:3000
+    > Accept: application/json
+    >
+    < HTTP/1.1 401 Unauthorized
+    < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
+    < Content-Length: 84
+    * Server Mojolicious (Perl) is not blacklisted
+    < Server: Mojolicious (Perl)
+    < Connection: keep-alive
+    < Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
+    < Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
+    < Access-Control-Allow-Origin: http://localhost:8080
+    < Date: Sat, 18 Apr 2015 20:36:12 GMT
+    < Content-Type: application/json
+    < Access-Control-Allow-Credentials: true
+    <
+    * Connection #0 to host localhost left intact
+    {"alerts":[{"level":"error","text":"Unauthorized, please log in."}]}
+    [jvd@laika ~]$
+
+404 Not Found
+  When the resource (path) is non existent Traffic Ops returns a 404::
+
+    [jvd@laika ~]$ curl -v -H'Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;' -H "Accept: application/json" http://localhost:3000/api/1.1/asnsjj.json
+    * Hostname was NOT found in DNS cache
+    *   Trying ::1...
+    * connect to ::1 port 3000 failed: Connection refused
+    *   Trying 127.0.0.1...
+    * Connected to localhost (127.0.0.1) port 3000 (#0)
+    > GET /api/1.1/asnsjj.json HTTP/1.1
+    > User-Agent: curl/7.37.1
+    > Host: localhost:3000
+    > Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;
+    > Accept: application/json
+    >
+    < HTTP/1.1 404 Not Found
+    * Server Mojolicious (Perl) is not blacklisted
+    < Server: Mojolicious (Perl)
+    < Content-Length: 75
+    < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
+    < Content-Type: application/json
+    < Date: Sat, 18 Apr 2015 20:37:43 GMT
+    < Access-Control-Allow-Credentials: true
+    < Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAzODYzLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--8a5a61b91473bc785d4073fe711de8d2c63f02dd; expires=Sun, 19 Apr 2015 00:37:43 GMT; path=/; HttpOnly
+    < Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
+    < Connection: keep-alive
+    < Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
+    < Access-Control-Allow-Origin: http://localhost:8080
+    <
+    * Connection #0 to host localhost left intact
+    {"alerts":[{"text":"Resource not found.","level":"error"}]}
+    [jvd@laika ~]$
+
+500 Internal Server Error
+  When you are asking for a correct path, but the database doesn't match, it returns a 500:: 
+
+    [jvd@laika ~]$ curl -v -H'Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;' -H "Accept: application/json" http://localhost:3000/api/1.1/servers/hostname/jj/details.json
+    * Hostname was NOT found in DNS cache
+    *   Trying ::1...
+    * connect to ::1 port 3000 failed: Connection refused
+    *   Trying 127.0.0.1...
+    * Connected to localhost (127.0.0.1) port 3000 (#0)
+    > GET /api/1.1/servers/hostname/jj/details.json HTTP/1.1
+    > User-Agent: curl/7.37.1
+    > Host: localhost:3000
+    > Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;
+    > Accept: application/json
+    >
+    < HTTP/1.1 500 Internal Server Error
+    * Server Mojolicious (Perl) is not blacklisted
+    < Server: Mojolicious (Perl)
+    < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
+    < Content-Length: 93
+    < Set-Cookie: mojolicious=eyJhdXRoX2RhdGEiOiJhZG1pbiIsImV4cGlyZXMiOjE0Mjk0MDQzMDZ9--1b08977e91f8f68b0ff5d5e5f6481c76ddfd0853; expires=Sun, 19 Apr 2015 00:45:06 GMT; path=/; HttpOnly
+    < Content-Type: application/json
+    < Date: Sat, 18 Apr 2015 20:45:06 GMT
+    < Access-Control-Allow-Credentials: true
+    < Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
+    < Connection: keep-alive
+    < Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
+    < Access-Control-Allow-Origin: http://localhost:8080
+    <
+    * Connection #0 to host localhost left intact
+    {"alerts":[{"level":"error","text":"An error occurred. Please contact your administrator."}]}
+    [jvd@laika ~]$
+
+  The rest of the API documentation will only document the ``200 OK`` case, where no errors have occured.
+
+Traffic Ops API Routes
+----------------------
+
+.. toctree:: 
+  :maxdepth: 1
+
+  traffic_ops_api/routes
+
+API 1.1 Reference 
+-----------------
+
+.. toctree:: 
+  :maxdepth: 1
+
+  traffic_ops_api/v11/asn
+  traffic_ops_api/v11/cachegroup
+  traffic_ops_api/v11/cdn
+  traffic_ops_api/v11/changelog
+  traffic_ops_api/v11/deliveryservice
+  traffic_ops_api/v11/hwinfo
+  traffic_ops_api/v11/parameter
+  traffic_ops_api/v11/phys_location
+  traffic_ops_api/v11/profile
+  traffic_ops_api/v11/region
+  traffic_ops_api/v11/role
+  traffic_ops_api/v11/server
+  traffic_ops_api/v11/static_dns
+  traffic_ops_api/v11/status
+  traffic_ops_api/v11/system
+  traffic_ops_api/v11/to_extension
+  traffic_ops_api/v11/type
+  traffic_ops_api/v11/user
+
+API 1.2 Reference 
+-----------------
+
+.. toctree:: 
+  :maxdepth: 1
+
+  traffic_ops_api/v12/asn
+  traffic_ops_api/v12/cachegroup
+  traffic_ops_api/v12/cache_stats
+  traffic_ops_api/v12/cdn
+  traffic_ops_api/v12/changelog
+  traffic_ops_api/v12/deliveryservice
+  traffic_ops_api/v12/deliveryservice_stats
+  traffic_ops_api/v12/division
+  traffic_ops_api/v12/federation
+  traffic_ops_api/v12/hwinfo
+  traffic_ops_api/v12/parameter
+  traffic_ops_api/v12/phys_location
+  traffic_ops_api/v12/profile
+  traffic_ops_api/v12/profile_parameter
+  traffic_ops_api/v12/influxdb
+  traffic_ops_api/v12/region
+  traffic_ops_api/v12/role
+  traffic_ops_api/v12/server
+  traffic_ops_api/v12/static_dns
+  traffic_ops_api/v12/status
+  traffic_ops_api/v12/system
+  traffic_ops_api/v12/to_extension
+  traffic_ops_api/v12/type
+  traffic_ops_api/v12/user
+  traffic_ops_api/v12/topology
+
+
+
+
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/routes.txt b/docs/1.8.0/_sources/development/traffic_ops_api/routes.txt
new file mode 100644
index 0000000..ec90963
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/routes.txt
@@ -0,0 +1,116 @@
+.. raw:: html
+
+  <style>
+  table {
+      table-layout: fixed;
+      width: 100%;
+  }
+
+  td {
+      word-wrap:break-word;
+  }
+  table.docutils col:nth-child(1) {
+      width: 30%;
+  }
+  table.docutils col:nth-child(2) {
+      width: 30%;
+  }
+  table.docutils col:nth-child(3) {
+      width: 30%;
+  }
+  .wy-nav-content {
+      max-width: 1200px;
+      width: 90%;
+  }
+  </style>
+
+.. 
+.. 
+.. 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.
+.. 
+
+
+.. _to-api-routes:
+
+API Routes
+==========
+
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| 1.0                                |   1.1                                              |   1.2                                              |
++====================================+====================================================+====================================================+
+| /asns                              |   :ref:`to-api-v11-asns-route`                     |   :ref:`to-api-v12-asns-route`                     |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /availableds                       |   :ref:`to-api-v11-ds-route`                       |   :ref:`to-api-v12-ds-route`                       |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| *Not Implemented*                  |   *Not Implemented*                                |   :ref:`to-api-v12-cache-stats-route`              |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datacrans                         |   /api/1.1/crans.json                              |   /api/1.2/crans.json                              |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datacrans/orderby/:field          |   /api/1.1/crans.json                              |   /api/1.2/crans.json                              |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datadeliveryservice               |   :ref:`to-api-v11-ds-route`                       |   :ref:`to-api-v12-ds-route`                       |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datadeliveryserviceserver         |   /api/1.1/deliveryserviceserver.json              |   /api/1.2/deliveryserviceserver.json              |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datadomains                       |   /api/1.1/cdns/domains.json                       |   /api/1.2/cdns/domains.json                       |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| *Not Implemented*                  |  *Not Implemented*                                 |   :ref:`to-api-v12-ds-stats-route`                 |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datahwinfo                        |   :ref:`to-api-v11-hwinfo-route`                   |   :ref:`to-api-v12-hwinfo-route`                   |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datalinks                         |   /api/1.1/deliveryserviceserver.json              |   /api/1.2/deliveryserviceserver.json              |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datalinks/orderby/:field          |   /api/1.1/deliveryserviceserver.json              |   /api/1.2/deliveryserviceserver.json              |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datalogs                          |   :ref:`to-api-v11-change-logs-route`              |   :ref:`to-api-v12-change-logs-route`              |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datalocation/orderby/id           |   :ref:`to-api-v11-cachegroups-route`              |   :ref:`to-api-v12-cachegroups-route`              |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datalocationparameters            |   :ref:`to-api-v11-cachegroups-route`              |   :ref:`to-api-v12-cachegroups-route`              |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /dataparameter                     |   :ref:`to-api-v11-parameters-route`               |   :ref:`to-api-v12-parameters-route`               |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /dataparameter/:parameter          |   /api/1.1/parameters/profile/:parameter.json      |   /api/1.2/parameters/profile/:parameter.json      |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /dataphys_location                 |   :ref:`to-api-v11-phys-loc-route`                 |   :ref:`to-api-v12-phys-loc-route`                 |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /dataprofile                       |   :ref:`to-api-v11-profiles-route`                 |   :ref:`to-api-v12-profiles-route`                 |
+|                                    |                                                    |                                                    |
+| /dataprofile/orderby/name          |                                                    |                                                    |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /dataregion                        |   :ref:`to-api-v11-regions-route`                  |   :ref:`to-api-v12-regions-route`                  |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datarole                          |   :ref:`to-api-v11-roles-route`                    |   :ref:`to-api-v12-roles-route`                    |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datarole/orderby/:field           |   :ref:`to-api-v11-roles-route`                    |   :ref:`to-api-v12-roles-route`                    |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /dataserver                        |   :ref:`to-api-v11-servers-route`                  |   :ref:`to-api-v12-servers-route`                  |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /dataserver/orderby/:field         |   :ref:`to-api-v11-servers-route`                  |   :ref:`to-api-v12-servers-route`                  |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /dataserverdetail/select/:hostname |   /api/1.1/servers/hostname/:hostname/details.json |   /api/1.2/servers/hostname/:hostname/details.json |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datastaticdnsentry                |   :ref:`to-api-v11-static-dns-route`               |   :ref:`to-api-v12-static-dns-route`               |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datastatus                        |   :ref:`to-api-v11-statuses-route`                 |   :ref:`to-api-v12-statuses-route`                 |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datastatus/orderby/name           |   :ref:`to-api-v11-statuses-route`                 |   :ref:`to-api-v12-statuses-route`                 |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datatype                          |   :ref:`to-api-v11-types-route`                    |   :ref:`to-api-v12-types-route`                    |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datatype/orderby/:field           |   :ref:`to-api-v11-types-route`                    |   :ref:`to-api-v12-types-route`                    |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datauser                          |   :ref:`to-api-v11-users-route`                    |   :ref:`to-api-v12-users-route`                    |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
+| /datauser/orderby/:field           |   :ref:`to-api-v11-users-route`                    |   :ref:`to-api-v12-users-route`                    |
++------------------------------------+----------------------------------------------------+----------------------------------------------------+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/asn.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/asn.txt
new file mode 100644
index 0000000..b6960d7
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/asn.txt
@@ -0,0 +1,69 @@
+.. 
+.. 
+.. 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.
+.. 
+
+
+.. _to-api-v11-asn:
+
+ASN
+===
+
+.. _to-api-v11-asns-route:
+
+/api/1.1/asns
++++++++++++++
+
+**GET /api/1.1/asns**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +------------------+--------+-------------------------------------------------------------------------+
+  |    Parameter     |  Type  |                               Description                               |
+  +==================+========+=========================================================================+
+  | ``asns``         | array  | A collection of asns                                                    |
+  +------------------+--------+-------------------------------------------------------------------------+
+  | ``>lastUpdated`` | string | The Time / Date this server entry was last updated                      |
+  +------------------+--------+-------------------------------------------------------------------------+
+  | ``>id``          | string | Local unique identifier for the ASN                                     |
+  +------------------+--------+-------------------------------------------------------------------------+
+  | ``>asn``         | string | Autonomous System Numbers per APNIC for identifying a service provider. |
+  +------------------+--------+-------------------------------------------------------------------------+
+  | ``>cachegroup``  | string | Related cachegroup name                                                 |
+  +------------------+--------+-------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": {
+        "asns": [
+           {
+              "lastUpdated": "2012-09-17 21:41:22",
+              "id": "27",
+              "asn": "7015",
+              "cachegroup": "us-ma-woburn"
+           },
+           {
+              "lastUpdated": "2012-09-17 21:41:22",
+              "id": "28",
+              "asn": "7016",
+              "cachegroup": "us-pa-pittsburgh"
+           }
+        ]
+     },
+    }
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/cachegroup.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/cachegroup.txt
new file mode 100644
index 0000000..5278645
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/cachegroup.txt
@@ -0,0 +1,317 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-cachegroup:
+
+Cache Group
+===========
+
+.. _to-api-v11-cachegroups-route:
+
+/api/1.1/cachegroups
+++++++++++++++++++++
+
+**GET /api/1.1/cachegroups**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | Parameter                         | Type   | Description                                                              |
+  +===================================+========+==========================================================================+
+  | ``id``                            | string | Local unique identifier for the Cache Group                              |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``lastUpdated``                   | string | The Time / Date this entry was last updated                              |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``latitude``                      | string | Latitude for the Cache Group                                             |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``longitude``                     | string | Longitude for the Cache Group                                            |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``name``                          | string | The name of the Cache Group entry                                        |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``parentCachegroupId``            | string | Parent cachegroup ID.                                                    |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``parentCachegroupName``          | string | Parent cachegroup name.                                                  |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``secondaryParentCachegroupId``   | string | Secondary parent cachegroup ID.                                          |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``secondaryParentCachegroupName`` | string | Secondary parent cachegroup name.                                        |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``shortName``                     | string | Abbreviation of the Cache Group Name                                     |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``typeId``                        | string | Unique identifier for the 'Type' of Cache Group entry                    |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``typeName``                      | string | The name of the type of Cache Group entry                                |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "id": "21",
+           "lastUpdated": "2012-09-25 20:27:28",
+           "latitude": "0",
+           "longitude": "0",
+           "name": "dc-chicago",
+           "parentCachegroupId": null,
+           "parentCachegroupName": null,
+           "secondaryParentCachegroupId": null,
+           "secondaryParentCachegroupName": null,
+           "shortName": "dcchi",
+           "typeName": "MID_LOC",
+           "typeId": "4"
+        },
+        {
+           "id": "22",
+           "lastUpdated": "2012-09-25 20:27:28",
+           "latitude": "0",
+           "longitude": "0",
+           "name": "dc-chicago-1",
+           "parentCachegroupId": null,
+           "parentCachegroupName": null,
+           "secondaryParentCachegroupId": null,
+           "secondaryParentCachegroupName": null,
+           "shortName": "dcchi",
+           "typeName": "MID_LOC",
+           "typeId": "4"
+        }
+     ],
+    }
+
+|
+
+**GET /api/1.1/cachegroups/trimmed**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``name``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+      {
+       "response": [
+          {
+             "name": "dc-chicago"
+          },
+          {
+             "name": "dc-cmc"
+          }
+       ],
+     }
+
+|
+
+**GET /api/1.1/cachegroups/:id**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | Parameter                         | Type   | Description                                                              |
+  +===================================+========+==========================================================================+
+  | ``id``                            | string | Local unique identifier for the Cache Group                              |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``lastUpdated``                   | string | The Time / Date this entry was last updated                              |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``latitude``                      | string | Latitude for the Cache Group                                             |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``longitude``                     | string | Longitude for the Cache Group                                            |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``name``                          | string | The name of the Cache Group entry                                        |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``parentCachegroupId``            | string | Parent cachegroup ID.                                                    |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``parentCachegroupName``          | string | Parent cachegroup name.                                                  |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``secondaryParentCachegroupId``   | string | Secondary parent cachegroup ID.                                          |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``secondaryParentCachegroupName`` | string | Secondary parent cachegroup name.                                        |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``shortName``                     | string | Abbreviation of the Cache Group Name                                     |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``typeId``                        | string | Unique identifier for the 'Type' of Cache Group entry                    |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+  | ``typeName``                      | string | The name of the type of Cache Group entry                                |
+  +-----------------------------------+--------+--------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "id": "21",
+           "lastUpdated": "2012-09-25 20:27:28",
+           "latitude": "0",
+           "longitude": "0",
+           "name": "dc-chicago",
+           "parentCachegroupId": null,
+           "parentCachegroupName": null,
+           "secondaryParentCachegroupId": null,
+           "secondaryParentCachegroupName": null,
+           "shortName": "dcchi",
+           "typeName": "MID_LOC",
+           "typeId": "4"
+        }
+     ],
+    }
+
+|
+
+
+**GET /api/1.1/cachegroup/:parameter_id/parameter**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +------------------+----------+-------------+
+  |       Name       | Required | Description |
+  +==================+==========+=============+
+  | ``parameter_id`` | yes      |             |
+  +------------------+----------+-------------+
+
+  **Response Properties**
+
+  +-----------------+--------+-------------+
+  |    Parameter    |  Type  | Description |
+  +=================+========+=============+
+  | ``cachegroups`` | array  |             |
+  +-----------------+--------+-------------+
+  | ``>name``       | string |             |
+  +-----------------+--------+-------------+
+  | ``>id``         | string |             |
+  +-----------------+--------+-------------+
+
+  **Response Example** ::
+
+    {
+     "response": {
+        "cachegroups": [
+           {
+              "name": "dc-chicago",
+              "id": "21"
+           },
+           {
+              "name": "dc-cmc",
+              "id": "22"
+           }
+        ]
+     },
+    }
+
+
+**GET /api/1.1/cachegroupparameters**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +--------------------------+--------+-----------------------------------------+
+  |        Parameter         |  Type  |               Description               |
+  +==========================+========+=========================================+
+  | ``cachegroupParameters`` | array  | A collection of cache group parameters. |
+  +--------------------------+--------+-----------------------------------------+
+  | ``>parameter``           | string |                                         |
+  +--------------------------+--------+-----------------------------------------+
+  | ``>last_updated``        | string |                                         |
+  +--------------------------+--------+-----------------------------------------+
+  | ``>cachegroup``          | string |                                         |
+  +--------------------------+--------+-----------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": {
+        "cachegroupParameters": [
+           {
+              "parameter": "379",
+              "last_updated": "2013-08-05 18:49:37",
+              "cachegroup": "us-ca-sanjose"
+           },
+           {
+              "parameter": "380",
+              "last_updated": "2013-08-05 18:49:37",
+              "cachegroup": "us-ca-sanjose"
+           },
+           {
+              "parameter": "379",
+              "last_updated": "2013-08-05 18:49:37",
+              "cachegroup": "us-ma-woburn"
+           }
+        ]
+     },
+    }
+
+
+|
+
+**GET /api/1.1/cachegroups/:parameter_id/parameter/available**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +------------------+----------+-------------+
+  |       Name       | Required | Description |
+  +==================+==========+=============+
+  | ``parameter_id`` | yes      |             |
+  +------------------+----------+-------------+
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``name``              |        |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``id``                |        |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "name": "dc-chicago",
+           "id": "21"
+        },
+        {
+           "name": "dc-cmc",
+           "id": "22"
+        }
+     ],
+    }
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/cdn.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/cdn.txt
new file mode 100644
index 0000000..d2f742e
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/cdn.txt
@@ -0,0 +1,1086 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-cdn-health:
+
+CDN 
+===
+
+.. _to-api-v11-cdn-health-route:
+
+/api/1.1/cdns
++++++++++++++
+
+**GET /api/1.1/cdns**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +-------------------+--------+-------------------------------------------------+
+  |    Parameter      |  Type  |                   Description                   |
+  +===================+========+=================================================+
+  | ``id``            | string | CDN id.                                         |
+  +-------------------+--------+-------------------------------------------------+
+  | ``name``          | string | CDN name.                                       |
+  +-------------------+--------+-------------------------------------------------+
+  | ``dnssecEnabled`` |  bool  | DNSSEC enabled.                                 |
+  +-------------------+--------+-------------------------------------------------+
+  | ``lastUpdated``   | string |                                                 |
+  +-------------------+--------+-------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+           {
+              "id": "1"
+              "name": "over-the-top",
+              "dnssecEnabled": false,
+              "lastUpdated": "2014-10-02 08:22:43"
+           },
+           {
+              "id": "2"
+              "name": "cdn2",
+              "dnssecEnabled": true,
+              "lastUpdated": "2014-10-02 08:22:43"
+           }
+        ]
+    }
+
+|
+
+**GET /api/1.1/cdns/:id**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------+----------+---------------------------------------------+
+  |   Name    | Required |                Description                  |
+  +===========+==========+=============================================+
+  |   ``id``  |   yes    | CDN id.                                     |
+  +-----------+----------+---------------------------------------------+
+
+  **Response Properties**
+
+  +-------------------+--------+-------------------------------------------------+
+  |    Parameter      |  Type  |                   Description                   |
+  +===================+========+=================================================+
+  | ``id``            | string | CDN id.                                         |
+  +-------------------+--------+-------------------------------------------------+
+  | ``name``          | string | CDN name.                                       |
+  +-------------------+--------+-------------------------------------------------+
+  | ``dnssecEnabled`` |  bool  | DNSSEC enabled.                                 |
+  +-------------------+--------+-------------------------------------------------+
+  | ``lastUpdated``   | string |                                                 |
+  +-------------------+--------+-------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+           {
+              "id": "2"
+              "name": "cdn2",
+              "dnssecEnabled": false,
+              "lastUpdated": "2014-10-02 08:22:43"
+           }
+        ]
+    }
+
+|
+
+**GET /api/1.1/cdns/name/:name**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------+----------+---------------------------------------------+
+  |   Name    | Required |                Description                  |
+  +===========+==========+=============================================+
+  |  ``name`` |   yes    | CDN name.                                   |
+  +-----------+----------+---------------------------------------------+
+
+  **Response Properties**
+
+  +-------------------+--------+-------------------------------------------------+
+  |    Parameter      |  Type  |                   Description                   |
+  +===================+========+=================================================+
+  | ``id``            | string | CDN id.                                         |
+  +-------------------+--------+-------------------------------------------------+
+  | ``name``          | string | CDN name.                                       |
+  +-------------------+--------+-------------------------------------------------+
+  | ``dnssecEnabled`` |  bool  | DNSSEC enabled.                                 |
+  +-------------------+--------+-------------------------------------------------+
+  | ``lastUpdated``   | string |                                                 |
+  +-------------------+--------+-------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+           {
+              "id": "2"
+              "name": "cdn2",
+              "dnssecEnabled": false,
+              "lastUpdated": "2014-10-02 08:22:43"
+           }
+        ]
+    }
+
+|
+
+Health
+++++++
+
+**GET /api/1.1/cdns/health**
+
+  Retrieves the health of all locations (cache groups) for all CDNs.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +------------------+--------+-------------------------------------------------+
+  |    Parameter     |  Type  |                   Description                   |
+  +==================+========+=================================================+
+  | ``totalOnline``  | int    | Total number of online caches across all CDNs.  |
+  +------------------+--------+-------------------------------------------------+
+  | ``totalOffline`` | int    | Total number of offline caches across all CDNs. |
+  +------------------+--------+-------------------------------------------------+
+  | ``cachegroups``  | array  | A collection of cache groups.                   |
+  +------------------+--------+-------------------------------------------------+
+  | ``>online``      | int    | The number of online caches for the cache group |
+  +------------------+--------+-------------------------------------------------+
+  | ``>offline``     | int    | The number of offline caches for the cache      |
+  |                  |        | group.                                          |
+  +------------------+--------+-------------------------------------------------+
+  | ``>name``        | string | Cache group name.                               |
+  +------------------+--------+-------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": {
+        "totalOnline": 148,
+        "totalOffline": 0,
+        "cachegroups": [
+           {
+              "online": 8,
+              "offline": 0,
+              "name": "us-co-denver"
+           },
+           {
+              "online": 7,
+              "offline": 0,
+              "name": "us-de-newcastle"
+           }
+        ]
+     },
+    }
+
+
+|
+
+**GET /api/1.1/cdns/:name/health**
+
+  Retrieves the health of all locations (cache groups) for a given CDN.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------------+----------+---------------------------------------------------+
+  | Name            | Required | Description                                       |
+  +=================+==========+===================================================+
+  |``name``         | yes      |                                                   |
+  +-----------------+----------+---------------------------------------------------+
+
+  **Response Properties**
+
+  +------------------+--------+-------------------------------------------------+
+  |    Parameter     |  Type  |                   Description                   |
+  +==================+========+=================================================+
+  | ``totalOnline``  | int    | Total number of online caches across the        |
+  |                  |        | specified CDN.                                  |
+  +------------------+--------+-------------------------------------------------+
+  | ``totalOffline`` | int    | Total number of offline caches across the       |
+  |                  |        | specified CDN.                                  |
+  +------------------+--------+-------------------------------------------------+
+  | ``cachegroups``  | array  | A collection of cache groups.                   |
+  +------------------+--------+-------------------------------------------------+
+  | ``>online``      | int    | The number of online caches for the cache group |
+  +------------------+--------+-------------------------------------------------+
+  | ``>offline``     | int    | The number of offline caches for the cache      |
+  |                  |        | group.                                          |
+  +------------------+--------+-------------------------------------------------+
+  | ``>name``        | string | Cache group name.                               |
+  +------------------+--------+-------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": {
+        "totalOnline": 148,
+        "totalOffline": 0,
+        "cachegroups": [
+           {
+              "online": 8,
+              "offline": 0,
+              "name": "us-co-denver"
+           },
+           {
+              "online": 7,
+              "offline": 0,
+              "name": "us-de-newcastle"
+           }
+        ]
+     },
+    }
+
+|
+
+**GET /api/1.1/cdns/usage/overview**
+
+  Retrieves the high-level CDN usage metrics.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``currentGbps``       | number |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``tps``               | int    |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``maxGbps``           | int    |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+
+  **Response Example** ::
+
+    {
+         "response": {
+            "currentGbps": 149.368167,
+            "tps": 36805,
+            "maxGbps": 3961
+         }
+    }
+
+
+**GET /api/1.1/cdns/capacity**
+
+  Retrieves the aggregate capacity percentages of all locations (cache groups) for a given CDN.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``availablePercent``  | number |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``unavailablePercent``| number |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``utilizedPercent``   | number |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``maintenancePercent``| number |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+         "response": {
+            "availablePercent": 89.0939840205533,
+            "unavailablePercent": 0,
+            "utilizedPercent": 10.9060020300395,
+            "maintenancePercent": 0.0000139494071146245
+         }
+    }
+
+|
+
+.. _to-api-v11-cdn-routing:
+
+Routing
++++++++
+
+**GET /api/1.1/cdns/routing**
+
+  Retrieves the aggregate routing percentages of all locations (cache groups) for a given CDN.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +-----------------+--------+-----------------------------------------+
+  |    Parameter    |  Type  |               Description               |
+  +=================+========+=========================================+
+  | ``staticRoute`` | number | Used pre-configured DNS entries.        |
+  +-----------------+--------+-----------------------------------------+
+  | ``miss``        | number | No location available for client IP.    |
+  +-----------------+--------+-----------------------------------------+
+  | ``geo``         | number | Used 3rd party geo-IP mapping.          |
+  +-----------------+--------+-----------------------------------------+
+  | ``err``         | number | Error localizing client IP.             |
+  +-----------------+--------+-----------------------------------------+
+  | ``cz``          | number | Used Coverage Zone   geo-IP mapping.    |
+  +-----------------+--------+-----------------------------------------+
+  | ``dsr``         | number | Overflow traffic sent to secondary CDN. |
+  +-----------------+--------+-----------------------------------------+
+
+  **Response Example** ::
+
+   {
+         "response": {
+            "staticRoute": 0,
+            "miss": 0,
+            "geo": 37.8855391018869,
+            "err": 0,
+            "cz": 62.1144608981131,
+            "dsr": 0
+         }
+    }
+
+|
+
+.. _to-api-v11-cdn-metrics:
+
+Metrics
++++++++
+
+**GET /api/1.1/cdns/metric_types/:metric/start_date/:start/end_date/:end**
+
+  Retrieves edge metrics of one or all locations (cache groups).
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------------+----------+---------------------------+
+  |       Name      | Required |        Description        |
+  +=================+==========+===========================+
+  | ``metric_type`` | yes      | ooff, origin_tps          |
+  +-----------------+----------+---------------------------+
+  | ``start``       | yes      | UNIX time, yesterday, now |
+  +-----------------+----------+---------------------------+
+  | ``end``         | yes      | UNIX time, yesterday, now |
+  +-----------------+----------+---------------------------+
+
+  **Response Properties**
+
+  +---------------------+--------+-------------+
+  |      Parameter      |  Type  | Description |
+  +=====================+========+=============+
+  | ``stats``           | hash   |             |
+  +---------------------+--------+-------------+
+  | ``>count``          | string |             |
+  +---------------------+--------+-------------+
+  | ``>98thPercentile`` | string |             |
+  +---------------------+--------+-------------+
+  | ``>min``            | string |             |
+  +---------------------+--------+-------------+
+  | ``>max``            | string |             |
+  +---------------------+--------+-------------+
+  | ``>5thPercentile``  | string |             |
+  +---------------------+--------+-------------+
+  | ``>95thPercentile`` | string |             |
+  +---------------------+--------+-------------+
+  | ``>mean``           | string |             |
+  +---------------------+--------+-------------+
+  | ``>sum``            | string |             |
+  +---------------------+--------+-------------+
+  | ``data``            | array  |             |
+  +---------------------+--------+-------------+
+  | ``>time``           | int    |             |
+  +---------------------+--------+-------------+
+  | ``>value``          | number |             |
+  +---------------------+--------+-------------+
+  | ``label``           | string |             |
+  +---------------------+--------+-------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "stats": {
+              "count": 1,
+              "98thPercentile": 1668.03,
+              "min": 1668.03,
+              "max": 1668.03,
+              "5thPercentile": 1668.03,
+              "95thPercentile": 1668.03,
+              "mean": 1668.03,
+              "sum": 1668.03
+           },
+           "data": [
+              [
+                 1425135900000,
+                 1668.03
+              ],
+              [
+                 1425136200000,
+                 null
+              ]
+           ],
+           "label": "Origin TPS"
+        }
+     ],
+    }
+
+|
+
+.. _to-api-v11-cdn-domains:
+
+Domains
++++++++
+
+**GET /api/1.1/cdns/domains**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``profileId``         | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``parameterId``       | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``profileName``       | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``profileDescription``| string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``domainName``        | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "profileId": "5",
+           "parameterId": "404",
+           "profileName": "CR_FOO",
+           "profileDescription": "Content Router for foo.domain.net",
+           "domainName": "foo.domain.net"
+        },
+        {
+           "profileId": "8",
+           "parameterId": "405",
+           "profileName": "CR_BAR",
+           "profileDescription": "Content Router for bar.domain.net",
+           "domainName": "bar.domain.net"
+        }
+     ],
+    }
+
+|
+
+.. _to-api-v11-cdn-topology:
+
+Topology
+++++++++
+
+**GET /api/1.1/cdns/:cdn_name/configs**
+
+  Retrieves CDN config information based upon the provided cdn name.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +--------------+----------+-----------------------+
+  |     Name     | Required |      Description      |
+  +==============+==========+=======================+
+  | ``cdn_name`` | yes      | Your cdn name or, all |
+  +--------------+----------+-----------------------+
+
+  **Response Properties**
+
+  +-----------------------+--------+-----------------------------------------------+
+  | Parameter             | Type   | Description                                   |
+  +=======================+========+===============================================+
+  |``id``                 | string |                                               |
+  +-----------------------+--------+-----------------------------------------------+
+  |``value``              | string |                                               |
+  +-----------------------+--------+-----------------------------------------------+
+  |``name``               | string |                                               |
+  +-----------------------+--------+-----------------------------------------------+
+  |``config_file``        | string |                                               |
+  +-----------------------+--------+-----------------------------------------------+
+
+  **Response Example** ::
+
+    TBD
+
+|
+
+**GET /api/1.1/cdns/:name/configs/monitoring**
+
+  Retrieves CDN monitoring information.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +----------+----------+-------------+
+  |   Name   | Required | Description |
+  +==========+==========+=============+
+  | ``name`` | yes      |  CDN name   |
+  +----------+----------+-------------+
+
+  **Response Properties**
+
+  +-------------------------------------------------+--------+--------------------+
+  |                    Parameter                    |  Type  |    Description     |
+  +=================================================+========+====================+
+  | ``trafficServers``                              | array  | A collection of    |
+  |                                                 |        | Traffic Servers.   |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>profile``                                    | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>ip``                                         | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>status``                                     | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>cacheGroup``                                 | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>ip6``                                        | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>port``                                       | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>hostName``                                   | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>fqdn``                                       | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>interfaceName``                              | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>type``                                       | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>hashId``                                     | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``cacheGroups``                                 | array  | A collection of    |
+  |                                                 |        | cache groups.      |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>coordinates``                                | hash   |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>>longitude``                                 | number |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>>latitude``                                  | number |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>name``                                       | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``config``                                      | hash   |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>hack.ttl``                                   | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>tm.healthParams.polling.url``                | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>tm.dataServer.polling.url``                  | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>health.timepad``                             | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>tm.polling.interval``                        | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>health.threadPool``                          | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>health.polling.interval``                    | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>health.event-count``                         | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>tm.crConfig.polling.url``                    | number |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>CDN_name``                                   | number |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``trafficMonitors``                             | array  | A collection of    |
+  |                                                 |        | Traffic Monitors.  |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>profile``                                    | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>location``                                   | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>ip``                                         | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>status``                                     | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>ip6``                                        | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>port``                                       | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>hostName``                                   | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>fqdn``                                       | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``deliveryServices``                            | array  | A collection of    |
+  |                                                 |        | delivery services. |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>xmlId``                                      | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>totalTpsThreshold``                          | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>status``                                     | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>totalKbpsThreshold``                         | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``profiles``                                    | array  | A collection of    |
+  |                                                 |        | profiles.          |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>parameters``                                 | hash   |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>>health.connection.timeout``                 | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>>health.polling.url``                        | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>>health.threshold.queryTime``                | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>>history.count``                             | int    |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>>health.threshold.availableBandwidthInKbps`` | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>>health.threshold.loadavg``                  | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>name``                                       | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+  | ``>type``                                       | string |                    |
+  +-------------------------------------------------+--------+--------------------+
+
+  **Response Example**
+  ::
+
+    TBD
+
+|
+
+**GET /api/1.1/cdns/:name/configs/routing**
+
+  Retrieves CDN routing information.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +----------+----------+-------------+
+  |   Name   | Required | Description |
+  +==========+==========+=============+
+  | ``name`` | yes      |             |
+  +----------+----------+-------------+
+
+  **Response Properties**
+
+  +-------------------------------------+---------+-----------------------------------+
+  |              Parameter              |   Type  |            Description            |
+  +=====================================+=========+===================================+
+  | ``trafficServers``                  | array   | A collection of Traffic Servers.  |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>profile``                        | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>ip``                             | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>status``                         | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>cacheGroup``                     | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>ip6``                            | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>port``                           | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>deliveryServices``               | array   |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>xmlId``                         | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>remaps``                        | array   |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>hostName``                      | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>fqdn``                           | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>interfaceName``                  | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>type``                           | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>hashId``                         | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``stats``                           | hash    |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>trafficOpsPath``                 | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>cdnName``                        | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>trafficOpsVersion``              | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>trafficOpsUser``                 | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>date``                           | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>trafficOpsHost``                 | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``cacheGroups``                     | array   | A collection of cache groups.     |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>coordinates``                    | hash    |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>longitude``                     | number  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>latitude``                      | number  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>name``                           | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``config``                          | hash    |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tld.soa.admin``                  | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tcoveragezone.polling.interval`` | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>geolocation.polling.interval``   | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tld.soa.expire``                 | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>coveragezone.polling.url``       | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tld.soa.minimum``                | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>geolocation.polling.url``        | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>domain_name``                    | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tld.ttls.AAAA``                  | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tld.soa.refresh``                | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tld.ttls.NS``                    | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tld.ttls.SOA``                   | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>geolocation6.polling.interval``  | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tld.ttls.A``                     | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>tld.soa.retry``                  | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>geolocation6.polling.url``       | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``trafficMonitors``                 | array   | A collection of Traffic Monitors. |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>profile``                        | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>location``                       | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>ip``                             | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>status``                         | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>ip6``                            | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>port``                           | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>hostName``                       | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>fqdn``                           | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``deliveryServices``                | array   | A collection of delivery          |
+  |                                     |         | services.                         |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>xmlId``                          | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>ttl``                            | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>geoEnabled``                     | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>coverageZoneOnly``               | boolean |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>matchSets``                      | array   |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>protocol``                      | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>matchList``                     | array   |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>>regex``                        | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>>matchType``                    | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>bypassDestination``              | hash    |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>maxDnsIpsForLocation``          | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>ttl``                           | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>type``                          | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>ttls``                           | hash    |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>A``                             | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>SOA``                           | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>NS``                            | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>AAAA``                          | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>missCoordinates``                | hash    |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>longitude``                     | number  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>latitude``                      | number  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>soa``                            | hash    |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>admin``                         | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>retry``                         | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>minimum``                       | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>refresh``                       | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>>expire``                        | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``trafficRouters``                  | hash    |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>profile``                        | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>location``                       | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>ip``                             | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>status``                         | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>ip6``                            | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>port``                           | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>hostName``                       | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>fqdn``                           | string  |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+  | ``>apiPort``                        | int     |                                   |
+  +-------------------------------------+---------+-----------------------------------+
+
+
+**Response Example**
+
+::
+  TBD
+
+ 
+.. _to-api-v11-cdn-dnsseckeys:
+
+DNSSEC Keys
++++++++++++
+
+**GET /api/1.1/cdns/name/:name/dnsseckeys**
+
+  Gets a list of dnsseckeys for CDN and all associated Delivery Services.
+  Before returning response to user, check to make sure keys aren't expired.  If they are expired, generate new ones.
+  Before returning response to user, make sure dnssec keys for all delivery services exist.  If they don't exist, create them.
+
+  Authentication Required: Yes
+
+  Role(s) Required: Admin
+
+  **Request Route Parameters**
+
+  +----------+----------+-------------+
+  |   Name   | Required | Description |
+  +==========+==========+=============+
+  | ``name`` | yes      |             |
+  +----------+----------+-------------+
+
+  **Response Properties**
+
+  +------------------------+--------+---------------------------------------------------------+
+  |       Parameter        |  Type  |                       Description                       |
+  +========================+========+=========================================================+
+  | ``cdn name/ds xml_id`` | string | identifier for ds or cdn                                |
+  +------------------------+--------+---------------------------------------------------------+
+  | ``>zsk/ksk``           | array  | collection of zsk/ksk data                              |
+  +------------------------+--------+---------------------------------------------------------+
+  | ``>>ttl``              | string | time-to-live for dnssec requests                        |
+  +------------------------+--------+---------------------------------------------------------+
+  | ``>>inceptionDate``    | string | epoch timestamp for when the keys were created          |
+  +------------------------+--------+---------------------------------------------------------+
+  | ``>>expirationDate``   | string | epoch timestamp representing the expiration of the keys |
+  +------------------------+--------+---------------------------------------------------------+
+  | ``>>private``          | string | encoded private key                                     |
+  +------------------------+--------+---------------------------------------------------------+
+  | ``>>public``           | string | encoded public key                                      |
+  +------------------------+--------+---------------------------------------------------------+
+  | ``>>name``             | string | domain name                                             |
+  +------------------------+--------+---------------------------------------------------------+
+  | ``version``            | string | API version                                             |
+  +------------------------+--------+---------------------------------------------------------+
+
+
+  **Response Example** ::
+
+    {
+      "response": {
+        "cdn1": {
+          "zsk": {
+            "ttl": "60",
+            "inceptionDate": "1426196750",
+            "private": "zsk private key",
+            "public": "zsk public key",
+            "expirationDate": "1428788750",
+            "name": "foo.kabletown.com."
+          },
+          "ksk": {
+            "name": "foo.kabletown.com.",
+            "expirationDate": "1457732750",
+            "public": "ksk public key",
+            "private": "ksk private key",
+            "inceptionDate": "1426196750",
+            "ttl": "60"
+          }
+        },
+        "ds-01": {
+          "zsk": {
+            "ttl": "60",
+            "inceptionDate": "1426196750",
+            "private": "zsk private key",
+            "public": "zsk public key",
+            "expirationDate": "1428788750",
+            "name": "ds-01.foo.kabletown.com."
+          },
+          "ksk": {
+            "name": "ds-01.foo.kabletown.com.",
+            "expirationDate": "1457732750",
+            "public": "ksk public key",
+            "private": "ksk private key",
+            "inceptionDate": "1426196750"
+          }
+        },
+        ... repeated for each ds in the cdn
+      },
+    }
+
+|
+
+**GET /api/1.1/cdns/name/:name/dnsseckeys/delete**
+
+  Delete dnssec keys for a cdn and all associated delivery services.
+
+  Authentication Required: Yes
+
+  Role(s) Required: Admin
+
+  **Request Route Parameters**
+
+  +----------+----------+----------------------------------------------------------+
+  |   Name   | Required |                       Description                        |
+  +==========+==========+==========================================================+
+  | ``name`` | yes      | name of the CDN for which you want to delete dnssec keys |
+  +----------+----------+----------------------------------------------------------+
+
+  **Response Properties**
+
+  +--------------+--------+------------------+
+  |  Parameter   |  Type  |   Description    |
+  +==============+========+==================+
+  | ``response`` | string | success response |
+  +--------------+--------+------------------+
+
+  **Response Example**
+  ::
+
+    {  
+      "response": "Successfully deleted dnssec keys for <cdn>"
+    }
+
+|
+  
+**POST /api/1.1/deliveryservices/dnsseckeys/generate**
+
+  Generates zsk and ksk keypairs for a cdn and all associated delivery services.
+
+  Authentication Required: Yes
+
+  Role(s) Required: Admin
+
+  **Request Properties**
+
+  +-----------------------+---------+------------------------------------------------+
+  |       Parameter       |   Type  |                  Description                   |
+  +=======================+=========+================================================+
+  | ``key``               | string  | name of the cdn                                |
+  +-----------------------+---------+------------------------------------------------+
+  | ``name``              | string  | domain name of the cdn                         |
+  +-----------------------+---------+------------------------------------------------+
+  | ``ttl``               | string  | time to live                                   |
+  +-----------------------+---------+------------------------------------------------+
+  | ``kskExpirationDays`` | string  | Expiration (in days) for the key signing keys  |
+  +-----------------------+---------+------------------------------------------------+
+  | ``zskExpirationDays`` | string  | Expiration (in days) for the zone signing keys |
+  +-----------------------+---------+------------------------------------------------+
+
+  **Request Example** ::
+
+    {
+      "key": "cdn1",
+      "name" "ott.kabletown.com",
+      "ttl": "60",
+      "kskExpirationDays": "365",
+      "zskExpirationDays": "90"
+    }
+
+  **Response Properties**
+
+  +--------------+--------+-----------------+
+  |  Parameter   |  Type  |   Description   |
+  +==============+========+=================+
+  | ``response`` | string | response string |
+  +--------------+--------+-----------------+
+  | ``version``  | string | API version     |
+  +--------------+--------+-----------------+
+
+  **Response Example** ::
+
+
+    {  
+      "response": "Successfully created dnssec keys for cdn1"
+    }
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/changelog.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/changelog.txt
new file mode 100644
index 0000000..22b1ff1
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/changelog.txt
@@ -0,0 +1,154 @@
+.. 
+.. 
+.. 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.
+.. 
+
+
+.. _to-api-v11-change-logs:
+
+Change Logs
+===========
+
+.. _to-api-v11-change-logs-route:
+
+/api/1.1/logs
++++++++++++++
+
+**GET /api/1.1/logs.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +-----------------+--------+--------------------------------------------------------------------------+
+  | Parameter       | Type   | Description                                                              |
+  +=================+========+==========================================================================+
+  | ``ticketNum``   | string | Optional field to cross reference with any bug tracking systems          |
+  +-----------------+--------+--------------------------------------------------------------------------+
+  | ``level``       | string | Log categories for each entry, examples: 'UICHANGE', 'OPER', 'APICHANGE'.|
+  +-----------------+--------+--------------------------------------------------------------------------+
+  | ``lastUpdated`` | string | Local unique identifier for the Log                                      |
+  +-----------------+--------+--------------------------------------------------------------------------+
+  | ``user``        | string | Current user who made the change that was logged                         |
+  +-----------------+--------+--------------------------------------------------------------------------+
+  | ``id``          | string | Local unique identifier for the Log entry                                |
+  +-----------------+--------+--------------------------------------------------------------------------+
+  | ``message``     | string | Log detail about what occurred                                           |
+  +-----------------+--------+--------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "ticketNum": null,
+           "level": "OPER",
+           "lastUpdated": "2015-02-04 22:59:13",
+           "user": "userid852",
+           "id": "22661",
+           "message": "Snapshot CRConfig created."
+        },
+        {
+           "ticketNum": null,
+           "level": "APICHANGE",
+           "lastUpdated": "2015-02-03 17:04:20",
+           "user": "userid853",
+           "id": "22658",
+           "message": "Update server odol-atsec-nyc-23.kbaletown.net status=REPORTED"
+        },
+     ],
+    }
+
+|
+
+**GET /api/1.1/logs/:days/days.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +----------+----------+-----------------+
+  |   Name   | Required |   Description   |
+  +==========+==========+=================+
+  | ``days`` | yes      | Number of days. |
+  +----------+----------+-----------------+
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``ticketNum``         | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``level``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``lastUpdated``       | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``user``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``id``                | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``message``           | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "ticketNum": null,
+           "level": "OPER",
+           "lastUpdated": "2015-02-04 22:59:13",
+           "user": "userid852",
+           "id": "22661",
+           "message": "Snapshot CRConfig created."
+        },
+        {
+           "ticketNum": null,
+           "level": "APICHANGE",
+           "lastUpdated": "2015-02-03 17:04:20",
+           "user": "userid853",
+           "id": "22658",
+           "message": "Update server odol-atsec-nyc-23.kabletown.net status=REPORTED"
+        }
+     ],
+    }
+
+|
+
+**GET /api/1.1/logs/newcount.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``newLogcount``       |  int   |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+         "response": {
+            "newLogcount": 0
+         }
+    }
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/deliveryservice.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/deliveryservice.txt
new file mode 100644
index 0000000..373c7ec
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/deliveryservice.txt
@@ -0,0 +1,1276 @@
+.. 
+.. 
+.. 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.
+.. 
+
+
+.. _to-api-v11-ds:
+
+Delivery Service
+================
+
+.. _to-api-v11-ds-route:
+
+/api/1.1/deliveryservices
++++++++++++++++++++++++++
+
+**GET /api/1.1/deliveryservices**
+
+  Retrieves all delivery services. See also `Using Traffic Ops - Delivery Service <http://trafficcontrol.apache.org/docs/latest/admin/traffic_ops_using.html#delivery-service>`_.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  |        Parameter         |  Type  |                                                             Description                                                              |
+  +==========================+========+======================================================================================================================================+
+  | ``active``               |  bool  | true if active, false if inactive.                                                                                                   |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``cacheurl``             | string | Cache URL rule to apply to this delivery service.                                                                                    |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``ccrDnsTtl``            | string | The TTL of the DNS response for A or AAAA queries requesting the IP address of the tr. host.                                         |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``cdnId``                | string | Id of the CDN to which the delivery service belongs to.                                                                              |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``cdnName``              | string | Name of the CDN to which the delivery service belongs to.                                                                            |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``checkPath``            | string | The path portion of the URL to check this deliveryservice for health.                                                                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``displayName``          | string | The display name of the delivery service.                                                                                            |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``dnsBypassIp``          | string | The IPv4 IP to use for bypass on a DNS deliveryservice  - bypass starts when serving more than the                                   |
+  |                          |        | globalMaxMbps traffic on this deliveryservice.                                                                                       |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``dnsBypassIp6``         | string | The IPv6 IP to use for bypass on a DNS deliveryservice - bypass starts when serving more than the                                    |
+  |                          |        | globalMaxMbps traffic on this deliveryservice.                                                                                       |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``dnsBypassTtl``         | string | The TTL of the DNS bypass response.                                                                                                  |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``dscp``                 | string | The Differentiated Services Code Point (DSCP) with which to mark downstream (EDGE ->  customer) traffic.                             |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``edgeHeaderRewrite``    | string | The EDGE header rewrite actions to perform.                                                                                          |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``geoLimitRedirectUrl``  | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``geoLimit``             | string | - 0: None - no limitations                                                                                                           |
+  |                          |        | - 1: Only route on CZF file hit                                                                                                      |
+  |                          |        | - 2: Only route on CZF hit or when from USA                                                                                          |
+  |                          |        |                                                                                                                                      |
+  |                          |        | Note that this does not prevent access to content or makes content secure; it just prevents                                          |
+  |                          |        | routing to the content by Traffic Router.                                                                                            |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``geoLimitCountries``    | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``geoProvider``          | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``globalMaxMbps``        | string | The maximum global bandwidth allowed on this deliveryservice. If exceeded, the traffic routes to the                                 |
+  |                          |        | dnsByPassIp* for DNS deliveryservices and to the httpBypassFqdn for HTTP deliveryservices.                                           |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``globalMaxTps``         | string | The maximum global transactions per second allowed on this deliveryservice. When this is exceeded                                    |
+  |                          |        | traffic will be sent to the dnsByPassIp* for DNS deliveryservices and to the httpBypassFqdn for                                      |
+  |                          |        | HTTP deliveryservices                                                                                                                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``httpBypassFqdn``       | string | The HTTP destination to use for bypass on an HTTP deliveryservice - bypass starts when serving more than the                         |
+  |                          |        | globalMaxMbps traffic on this deliveryservice.                                                                                       |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``id``                   | string | The deliveryservice id (database row number).                                                                                        |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``infoUrl``              | string | Use this to add a URL that points to more information about that deliveryservice.                                                    |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``initialDispersion``    | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``ipv6RoutingEnabled``   |  bool  | false: send IPv4 address of Traffic Router to client on HTTP type del.                                                               |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``lastUpdated``          | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``logsEnabled``          |  bool  |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``longDesc``             | string | Description field 1.                                                                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``longDesc1``            | string | Description field 2.                                                                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``longDesc2``            | string | Description field 2.                                                                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>>type``               | string | The type of MatchList (one of :ref:to-api-v11-types use_in_table='regex').                                                           |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>>setNumber``          | string | The set Number of the matchList.                                                                                                     |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>>pattern``            | string | The regexp for the matchList.                                                                                                        |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``maxDnsAnswers``        | string | The maximum number of IPs to put in a A/AAAA response for a DNS deliveryservice (0 means all                                         |
+  |                          |        | available).                                                                                                                          |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``midHeaderRewrite``     | string | The MID header rewrite actions to perform.                                                                                           |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``missLat``              | string | The latitude to use when the client cannot be found in the CZF or the Geo lookup.                                                    |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``missLong``             | string | The longitude to use when the client cannot be found in the CZF or the Geo lookup.                                                   |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``multiSiteOrigin``      |  bool  | Is the Multi Site Origin feature enabled for this delivery service (0=false, 1=true). See :ref:`rl-multi-site-origin`                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``multiSiteOriginAlgor`` |  bool  | Is the Multi Site Origin feature enabled for this delivery service (0=false, 1=true). See :ref:`rl-multi-site-origin`                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``orgServerFqdn``        | string | The origin server base URL (FQDN when used in this instance, includes the                                                            |
+  |                          |        | protocol (http:// or https://) for use in retrieving content from the origin server.                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``originShield``         | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``profileDescription``   | string | The description of the Traffic Router Profile with which this deliveryservice is associated.                                         |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``profileId``            | string | The id of the Traffic Router Profile with which this deliveryservice is associated.                                                  |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``profileName``          | string | The name of the Traffic Router Profile with which this deliveryservice is associated.                                                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``protocol``             | string | - 0: serve with http:// at EDGE                                                                                                      |
+  |                          |        | - 1: serve with https:// at EDGE                                                                                                     |
+  |                          |        | - 2: serve with both http:// and https:// at EDGE                                                                                    |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``qstringIgnore``        | string | - 0: no special query string handling; it is for use in the cache-key and pass up to origin.                                         |
+  |                          |        | - 1: ignore query string in cache-key, but pass it up to parent and or origin.                                                       |
+  |                          |        | - 2: drop query string at edge, and do not use it in the cache-key.                                                                  |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``rangeRequestHandling`` | string | 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/reference/plugins/background_fetch.en.html>`_ plugin. |
+  |                          |        | - 2 Use the cache_range_requests plugin.                                                                                             |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``regexRemap``           | string | Regex Remap rule to apply to this delivery service at the Edge tier.                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``regionalGeoBlocking``  |  bool  | Regex Remap rule to apply to this delivery service at the Edge tier.                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``remapText``            | string | Additional raw remap line text.                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``signed``               |  bool  | - false: token based auth (see :ref:token-based-auth) is not enabled for this deliveryservice.                                       |
+  |                          |        | - true: token based auth is enabled for this deliveryservice.                                                                        |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``sslKeyVersion``        | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``trRequestHeaders``     | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``trResponseHeaders``    | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``type``                 | string | The type of this deliveryservice (one of :ref:to-api-v11-types use_in_table='deliveryservice').                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``typeId``               | string | The type of this deliveryservice (one of :ref:to-api-v11-types use_in_table='deliveryservice').                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``xmlId``                | string | Unique string that describes this deliveryservice.                                                                                   |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+      "response": [
+        {
+            "active": true,
+            "cacheurl": null,
+            "ccrDnsTtl": "3600",
+            "cdnId": "2",
+            "cdnName": "over-the-top",
+            "checkPath": "",
+            "displayName": "My Cool Delivery Service",
+            "dnsBypassCname": "",
+            "dnsBypassIp": "",
+            "dnsBypassIp6": "",
+            "dnsBypassTtl": "30",
+            "dscp": "40",
+            "edgeHeaderRewrite": null,
+            "exampleURLs": [
+                "http://edge.foo-ds.foo.bar.net"
+            ],
+            "geoLimit": "0",
+            "geoLimitCountries": null,
+            "geoLimitRedirectURL": null,
+            "geoProvider": "0",
+            "globalMaxMbps": null,
+            "globalMaxTps": "0",
+            "httpBypassFqdn": "",
+            "id": "442",
+            "infoUrl": "",
+            "initialDispersion": "1",
+            "ipv6RoutingEnabled": true,
+            "lastUpdated": "2016-01-26 08:49:35",
+            "logsEnabled": false,
+            "longDesc": "",
+            "longDesc1": "",
+            "longDesc2": "",
+            "matchList": [
+                {
+                    "pattern": ".*\\.foo-ds\\..*",
+                    "setNumber": "0",
+                    "type": "HOST_REGEXP"
+                }
+            ],
+            "maxDnsAnswers": "0",
+            "midHeaderRewrite": null,
+            "missLat": "41.881944",
+            "missLong": "-87.627778",
+            "multiSiteOrigin": false,
+            "multiSiteOriginAlgorithm": null,
+            "orgServerFqdn": "http://baz.boo.net",
+            "originShield": null,
+            "profileDescription": "Content Router for over-the-top",
+            "profileId": "5",
+            "profileName": "ROUTER_TOP",
+            "protocol": "0",
+            "qstringIgnore": "1",
+            "rangeRequestHandling": "0",
+            "regexRemap": null,
+            "regionalGeoBlocking": false,
+            "remapText": null,
+            "signed": false,
+            "sslKeyVersion": "0",
+            "trRequestHeaders": null,
+            "trResponseHeaders": "Access-Control-Allow-Origin: *",
+            "type": "HTTP",
+            "typeId": "8",
+            "xmlId": "foo-ds"
+        }
+        { .. },
+        { .. }
+      ]
+    }
+
+|
+
+
+**GET /api/1.1/deliveryservices/:id**
+
+  Retrieves a specific delivery service. See also `Using Traffic Ops - Delivery Service <http://trafficcontrol.apache.org/docs/latest/admin/traffic_ops_using.html#delivery-service>`_.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  |        Parameter         |  Type  |                                                             Description                                                              |
+  +==========================+========+======================================================================================================================================+
+  | ``active``               |  bool  | true if active, false if inactive.                                                                                                   |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``cacheurl``             | string | Cache URL rule to apply to this delivery service.                                                                                    |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``ccrDnsTtl``            | string | The TTL of the DNS response for A or AAAA queries requesting the IP address of the tr. host.                                         |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``cdnId``                | string | Id of the CDN to which the delivery service belongs to.                                                                              |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``cdnName``              | string | Name of the CDN to which the delivery service belongs to.                                                                            |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``checkPath``            | string | The path portion of the URL to check this deliveryservice for health.                                                                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``displayName``          | string | The display name of the delivery service.                                                                                            |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``dnsBypassIp``          | string | The IPv4 IP to use for bypass on a DNS deliveryservice  - bypass starts when serving more than the                                   |
+  |                          |        | globalMaxMbps traffic on this deliveryservice.                                                                                       |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``dnsBypassIp6``         | string | The IPv6 IP to use for bypass on a DNS deliveryservice - bypass starts when serving more than the                                    |
+  |                          |        | globalMaxMbps traffic on this deliveryservice.                                                                                       |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``dnsBypassTtl``         | string | The TTL of the DNS bypass response.                                                                                                  |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``dscp``                 | string | The Differentiated Services Code Point (DSCP) with which to mark downstream (EDGE ->  customer) traffic.                             |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``edgeHeaderRewrite``    | string | The EDGE header rewrite actions to perform.                                                                                          |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``exampleURLs``          |  array | Entry points into the CDN for this deliveryservice.                                                                                  |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``geoLimitRedirectUrl``  | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``geoLimit``             | string | - 0: None - no limitations                                                                                                           |
+  |                          |        | - 1: Only route on CZF file hit                                                                                                      |
+  |                          |        | - 2: Only route on CZF hit or when from USA                                                                                          |
+  |                          |        |                                                                                                                                      |
+  |                          |        | Note that this does not prevent access to content or makes content secure; it just prevents                                          |
+  |                          |        | routing to the content by Traffic Router.                                                                                            |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``geoLimitCountries``    | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``geoProvider``          | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``globalMaxMbps``        | string | The maximum global bandwidth allowed on this deliveryservice. If exceeded, the traffic routes to the                                 |
+  |                          |        | dnsByPassIp* for DNS deliveryservices and to the httpBypassFqdn for HTTP deliveryservices.                                           |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``globalMaxTps``         | string | The maximum global transactions per second allowed on this deliveryservice. When this is exceeded                                    |
+  |                          |        | traffic will be sent to the dnsByPassIp* for DNS deliveryservices and to the httpBypassFqdn for                                      |
+  |                          |        | HTTP deliveryservices                                                                                                                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``httpBypassFqdn``       | string | The HTTP destination to use for bypass on an HTTP deliveryservice - bypass starts when serving more than the                         |
+  |                          |        | globalMaxMbps traffic on this deliveryservice.                                                                                       |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``id``                   | string | The deliveryservice id (database row number).                                                                                        |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``infoUrl``              | string | Use this to add a URL that points to more information about that deliveryservice.                                                    |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``initialDispersion``    | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``ipv6RoutingEnabled``   |  bool  | false: send IPv4 address of Traffic Router to client on HTTP type del.                                                               |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``lastUpdated``          | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``logsEnabled``          |  bool  |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``longDesc``             | string | Description field 1.                                                                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``longDesc1``            | string | Description field 2.                                                                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``longDesc2``            | string | Description field 2.                                                                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``matchList``            | array  | Array of matchList hashes.                                                                                                           |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>>type``               | string | The type of MatchList (one of :ref:to-api-v11-types use_in_table='regex').                                                           |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>>setNumber``          | string | The set Number of the matchList.                                                                                                     |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>>pattern``            | string | The regexp for the matchList.                                                                                                        |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``maxDnsAnswers``        | string | The maximum number of IPs to put in a A/AAAA response for a DNS deliveryservice (0 means all                                         |
+  |                          |        | available).                                                                                                                          |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``midHeaderRewrite``     | string | The MID header rewrite actions to perform.                                                                                           |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``missLat``              | string | The latitude to use when the client cannot be found in the CZF or the Geo lookup.                                                    |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``missLong``             | string | The longitude to use when the client cannot be found in the CZF or the Geo lookup.                                                   |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``multiSiteOrigin``      |  bool  | Is the Multi Site Origin feature enabled for this delivery service (0=false, 1=true). See :ref:`rl-multi-site-origin`                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``multiSiteOriginAlgor`` |  bool  | Is the Multi Site Origin feature enabled for this delivery service (0=false, 1=true). See :ref:`rl-multi-site-origin`                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``orgServerFqdn``        | string | The origin server base URL (FQDN when used in this instance, includes the                                                            |
+  |                          |        | protocol (http:// or https://) for use in retrieving content from the origin server.                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``originShield``         | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``profileDescription``   | string | The description of the Traffic Router Profile with which this deliveryservice is associated.                                         |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``profileId``            | string | The id of the Traffic Router Profile with which this deliveryservice is associated.                                                  |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``profileName``          | string | The name of the Traffic Router Profile with which this deliveryservice is associated.                                                |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``protocol``             | string | - 0: serve with http:// at EDGE                                                                                                      |
+  |                          |        | - 1: serve with https:// at EDGE                                                                                                     |
+  |                          |        | - 2: serve with both http:// and https:// at EDGE                                                                                    |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``qstringIgnore``        | string | - 0: no special query string handling; it is for use in the cache-key and pass up to origin.                                         |
+  |                          |        | - 1: ignore query string in cache-key, but pass it up to parent and or origin.                                                       |
+  |                          |        | - 2: drop query string at edge, and do not use it in the cache-key.                                                                  |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``rangeRequestHandling`` | string | 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/reference/plugins/background_fetch.en.html>`_ plugin. |
+  |                          |        | - 2 Use the cache_range_requests plugin.                                                                                             |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``regexRemap``           | string | Regex Remap rule to apply to this delivery service at the Edge tier.                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``regionalGeoBlocking``  |  bool  | Regex Remap rule to apply to this delivery service at the Edge tier.                                                                 |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``remapText``            | string | Additional raw remap line text.                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``signed``               |  bool  | - false: token based auth (see :ref:token-based-auth) is not enabled for this deliveryservice.                                       |
+  |                          |        | - true: token based auth is enabled for this deliveryservice.                                                                        |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``sslKeyVersion``        | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``trRequestHeaders``     | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``trResponseHeaders``    | string |                                                                                                                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``type``                 | string | The type of this deliveryservice (one of :ref:to-api-v11-types use_in_table='deliveryservice').                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``typeId``               | string | The type of this deliveryservice (one of :ref:to-api-v11-types use_in_table='deliveryservice').                                      |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``xmlId``                | string | Unique string that describes this deliveryservice.                                                                                   |
+  +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+      "response": [
+        {
+            "active": true,
+            "cacheurl": null,
+            "ccrDnsTtl": "3600",
+            "cdnId": "2",
+            "cdnName": "over-the-top",
+            "checkPath": "",
+            "displayName": "My Cool Delivery Service",
+            "dnsBypassCname": "",
+            "dnsBypassIp": "",
+            "dnsBypassIp6": "",
+            "dnsBypassTtl": "30",
+            "dscp": "40",
+            "edgeHeaderRewrite": null,
+            "exampleURLs": [
+                "http://edge.foo-ds.foo.bar.net"
+            ],
+            "geoLimit": "0",
+            "geoLimitCountries": null,
+            "geoLimitRedirectURL": null,
+            "geoProvider": "0",
+            "globalMaxMbps": null,
+            "globalMaxTps": "0",
+            "httpBypassFqdn": "",
+            "id": "442",
+            "infoUrl": "",
+            "initialDispersion": "1",
+            "ipv6RoutingEnabled": true,
+            "lastUpdated": "2016-01-26 08:49:35",
+            "logsEnabled": false,
+            "longDesc": "",
+            "longDesc1": "",
+            "longDesc2": "",
+            "matchList": [
+                {
+                    "pattern": ".*\\.foo-ds\\..*",
+                    "setNumber": "0",
+                    "type": "HOST_REGEXP"
+                }
+            ],
+            "maxDnsAnswers": "0",
+            "midHeaderRewrite": null,
+            "missLat": "41.881944",
+            "missLong": "-87.627778",
+            "multiSiteOrigin": false,
+            "multiSiteOriginAlgorithm": null,
+            "orgServerFqdn": "http://baz.boo.net",
+            "originShield": null,
+            "profileDescription": "Content Router for over-the-top",
+            "profileId": "5",
+            "profileName": "ROUTER_TOP",
+            "protocol": "0",
+            "qstringIgnore": "1",
+            "rangeRequestHandling": "0",
+            "regexRemap": null,
+            "regionalGeoBlocking": false,
+            "remapText": null,
+            "signed": false,
+            "sslKeyVersion": "0",
+            "trRequestHeaders": null,
+            "trResponseHeaders": "Access-Control-Allow-Origin: *",
+            "type": "HTTP",
+            "typeId": "8",
+            "xmlId": "foo-ds"
+        }
+      ]
+    }
+
+|
+
+
+.. _to-api-v11-ds-health:
+
+Health
+++++++
+
+**GET /api/1.1/deliveryservices/:id/state.json**
+
+  Retrieves the failover state for a delivery service.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +------------------+---------+-------------------------------------------------+
+  |    Parameter     |  Type   |                   Description                   |
+  +==================+=========+=================================================+
+  | ``failover``     |  hash   |                                                 |
+  +------------------+---------+-------------------------------------------------+
+  | ``>locations``   |  array  |                                                 |
+  +------------------+---------+-------------------------------------------------+
+  | ``>destination`` |  string |                                                 |
+  +------------------+---------+-------------------------------------------------+
+  | ``>configured``  | boolean |                                                 |
+  +------------------+---------+-------------------------------------------------+
+  | ``>enabled``     | boolean |                                                 |
+  +------------------+---------+-------------------------------------------------+
+  | ``enabled``      | boolean |                                                 |
+  +------------------+---------+-------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+        "response": {
+            "failover": {
+                "locations": [ ],
+                "destination": null,
+                "configured": false,
+                "enabled": false
+            },
+            "enabled": true
+        }
+    }
+
+|
+
+**GET /api/1.1/deliveryservices/:id/health.json**
+
+  Retrieves the health of all locations (cache groups) for a delivery service.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +------------------+--------+-------------------------------------------------+
+  |    Parameter     |  Type  |                   Description                   |
+  +==================+========+=================================================+
+  | ``totalOnline``  | int    | Total number of online caches across all CDNs.  |
+  +------------------+--------+-------------------------------------------------+
+  | ``totalOffline`` | int    | Total number of offline caches across all CDNs. |
+  +------------------+--------+-------------------------------------------------+
+  | ``cachegroups``  | array  | A collection of cache groups.                   |
+  +------------------+--------+-------------------------------------------------+
+  | ``>online``      | int    | The number of online caches for the cache group |
+  +------------------+--------+-------------------------------------------------+
+  | ``>offline``     | int    | The number of offline caches for the cache      |
+  |                  |        | group.                                          |
+  +------------------+--------+-------------------------------------------------+
+  | ``>name``        | string | Cache group name.                               |
+  +------------------+--------+-------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": {
+        "totalOnline": 148,
+        "totalOffline": 0,
+        "cachegroups": [
+           {
+              "online": 8,
+              "offline": 0,
+              "name": "us-co-denver"
+           },
+           {
+              "online": 7,
+              "offline": 0,
+              "name": "us-de-newcastle"
+           }
+        ]
+     }
+    }
+
+
+|
+
+**GET /api/1.1/deliveryservices/:id/capacity.json**
+
+  Retrieves the capacity percentages of a delivery service.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------------+----------+---------------------------------------------------+
+  | Name            | Required | Description                                       |
+  +=================+==========+===================================================+
+  |id               | yes      | delivery service id.                              |
+  +-----------------+----------+---------------------------------------------------+
+
+  **Response Properties**
+
+  +------------------------+--------+---------------------------------------------------+
+  |       Parameter        |  Type  |                    Description                    |
+  +========================+========+===================================================+
+  | ``availablePercent``   | number | The percentage of server capacity assigned to     |
+  |                        |        | the delivery service that is available.           |
+  +------------------------+--------+---------------------------------------------------+
+  | ``unavailablePercent`` | number | The percentage of server capacity assigned to the |
+  |                        |        | delivery service that is unavailable.             |
+  +------------------------+--------+---------------------------------------------------+
+  | ``utilizedPercent``    | number | The percentage of server capacity assigned to the |
+  |                        |        | delivery service being used.                      |
+  +------------------------+--------+---------------------------------------------------+
+  | ``maintenancePercent`` | number | The percentage of server capacity assigned to the |
+  |                        |        | delivery service that is down for maintenance.    |
+  +------------------------+--------+---------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": {
+        "availablePercent": 89.0939840205533,
+        "unavailablePercent": 0,
+        "utilizedPercent": 10.9060020300395,
+        "maintenancePercent": 0.0000139494071146245
+     },
+    }
+
+
+|
+
+**GET /api/1.1/deliveryservices/:id/routing.json**
+
+  Retrieves the routing method percentages of a delivery service.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------------+----------+---------------------------------------------------+
+  | Name            | Required | Description                                       |
+  +=================+==========+===================================================+
+  |id               | yes      | delivery service id.                              |
+  +-----------------+----------+---------------------------------------------------+
+
+  **Response Properties**
+
+  +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
+  |    Parameter    |  Type  |                                                         Description                                                         |
+  +=================+========+=============================================================================================================================+
+  | ``staticRoute`` | number | The percentage of Traffic Router responses for this deliveryservice satisfied with pre-configured DNS entries.              |
+  +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
+  | ``miss``        | number | The percentage of Traffic Router responses for this deliveryservice that were a miss (no location available for client IP). |
+  +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
+  | ``geo``         | number | The percentage of Traffic Router responses for this deliveryservice satisfied using 3rd party geo-IP mapping.               |
+  +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
+  | ``err``         | number | The percentage of Traffic Router requests for this deliveryservice resulting in an error.                                   |
+  +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
+  | ``cz``          | number | The percentage of Traffic Router requests for this deliveryservice satisfied by a CZF hit.                                  |
+  +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
+  | ``dsr``         | number | The percentage of Traffic Router requests for this deliveryservice satisfied by sending the                                 |
+  |                 |        | client to the overflow CDN.                                                                                                 |
+  +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": {
+        "staticRoute": 0,
+        "miss": 0,
+        "geo": 37.8855391018869,
+        "err": 0,
+        "cz": 62.1144608981131,
+        "dsr": 0
+     },
+    }
+
+|
+
+.. _to-api-v11-ds-metrics:
+
+Metrics
++++++++
+
+**GET /api/1.1/deliveryservices/:id/server_types/:type/metric_types/start_date/:start/end_date/:end.json**
+
+  Retrieves detailed and summary metrics for MIDs or EDGEs for a delivery service.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +------------------+----------+-----------------------------------------------------------------------------+
+  |       Name       | Required |                                 Description                                 |
+  +==================+==========+=============================================================================+
+  | ``id``           | yes      | The delivery service id.                                                    |
+  +------------------+----------+-----------------------------------------------------------------------------+
+  | ``server_types`` | yes      | EDGE or MID.                                                                |
+  +------------------+----------+-----------------------------------------------------------------------------+
+  | ``metric_types`` | yes      | One of the following: "kbps", "tps", "tps_2xx", "tps_3xx", "tps_4xx",       |
+  |                  |          | "tps_5xx".                                                                  |
+  +------------------+----------+-----------------------------------------------------------------------------+
+  | ``start_date``   | yes      | UNIX time                                                                   |
+  +------------------+----------+-----------------------------------------------------------------------------+
+  | ``end_date``     | yes      | UNIX time                                                                   |
+  +------------------+----------+-----------------------------------------------------------------------------+
+
+  **Request Query Parameters**
+
+  +------------------+----------+-----------------------------------------------------------------------------+
+  |       Name       | Required |                                 Description                                 |
+  +==================+==========+=============================================================================+
+  | ``stats``        | no       | Flag used to return only summary metrics                                    |
+  +------------------+----------+-----------------------------------------------------------------------------+
+
+  **Response Properties**
+
+  +----------------------+--------+-------------+
+  |      Parameter       |  Type  | Description |
+  +======================+========+=============+
+  | ``stats``            | hash   |             |
+  +----------------------+--------+-------------+
+  | ``>>count``          | int    |             |
+  +----------------------+--------+-------------+
+  | ``>>98thPercentile`` | number |             |
+  +----------------------+--------+-------------+
+  | ``>>min``            | number |             |
+  +----------------------+--------+-------------+
+  | ``>>max``            | number |             |
+  +----------------------+--------+-------------+
+  | ``>>5thPercentile``  | number |             |
+  +----------------------+--------+-------------+
+  | ``>>95thPercentile`` | number |             |
+  +----------------------+--------+-------------+
+  | ``>>median``         | number |             |
+  +----------------------+--------+-------------+
+  | ``>>mean``           | number |             |
+  +----------------------+--------+-------------+
+  | ``>>stddev``         | number |             |
+  +----------------------+--------+-------------+
+  | ``>>sum``            | number |             |
+  +----------------------+--------+-------------+
+  | ``data``             | array  |             |
+  +----------------------+--------+-------------+
+  | ``>>item``           | array  |             |
+  +----------------------+--------+-------------+
+  | ``>>time``           | number |             |
+  +----------------------+--------+-------------+
+  | ``>>value``          | number |             |
+  +----------------------+--------+-------------+
+  | ``label``            | string |             |
+  +----------------------+--------+-------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "stats": {
+              "count": 988,
+              "98thPercentile": 16589105.55958,
+              "min": 3185442.975,
+              "max": 17124754.257,
+              "5thPercentile": 3901253.95445,
+              "95thPercentile": 16013210.034,
+              "median": 8816895.576,
+              "mean": 8995846.31741194,
+              "stddev": 3941169.83683573,
+              "sum": 333296106.060112
+           },
+           "data": [
+              [
+                 1414303200000,
+                 12923518.466
+              ],
+              [
+                 1414303500000,
+                 12625139.65
+              ]
+           ],
+           "label": "MID Kbps"
+        }
+     ],
+    }
+
+
+.. _to-api-v11-ds-server:
+
+Server
+++++++
+
+**GET /api/1.1/deliveryserviceserver.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: Yes
+
+  **Request Query Parameters**
+
+  +-----------+----------+----------------------------------------+
+  |    Name   | Required |              Description               |
+  +===========+==========+========================================+
+  | ``page``  | no       | The page number for use in pagination. |
+  +-----------+----------+----------------------------------------+
+  | ``limit`` | no       | For use in limiting the result set.    |
+  +-----------+----------+----------------------------------------+
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``lastUpdated``       | array  |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``server``            | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``deliveryService``   | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "page": 2,
+     "orderby": "deliveryservice",
+     "response": [
+        {
+           "lastUpdated": "2014-09-26 17:53:43",
+           "server": "20",
+           "deliveryService": "1"
+        },
+        {
+           "lastUpdated": "2014-09-26 17:53:44",
+           "server": "21",
+           "deliveryService": "1"
+        },
+     ],
+     "limit": 2
+    }
+
+|
+
+.. _to-api-v11-ds-sslkeys:
+
+SSL Keys
++++++++++
+
+**GET /api/1.1/deliveryservices/xmlId/:xmlid/sslkeys.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: Admin
+
+  **Request Route Parameters**
+
+  +-----------+----------+----------------------------------------+
+  |    Name   | Required |              Description               |
+  +===========+==========+========================================+
+  | ``xmlId`` | yes      | xml_id of the desired delivery service |
+  +-----------+----------+----------------------------------------+
+
+  **Request Query Parameters**
+
+  +-------------+----------+--------------------------------+
+  |     Name    | Required |          Description           |
+  +=============+==========+================================+
+  | ``version`` | no       | The version number to retrieve |
+  +-------------+----------+--------------------------------+
+
+  **Response Properties**
+
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  |    Parameter     |  Type  |                                                               Description                                                               |
+  +==================+========+=========================================================================================================================================+
+  | ``crt``          | string | base64 encoded crt file for delivery service                                                                                            |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``csr``          | string | base64 encoded csr file for delivery service                                                                                            |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``key``          | string | base64 encoded private key file for delivery service                                                                                    |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``businessUnit`` | string | The business unit entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``city``         | string | The city entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response          |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``organization`` | string | The organization entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response  |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``hostname``     | string | The hostname entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response      |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``country``      | string | The country entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response       |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``state``        | string | The state entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response         |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``version``      | string | The version of the certificate record in Riak                                                                                           |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {  
+      "response": {
+        "certificate": {
+          "crt": "crt",
+          "key": "key",
+          "csr": "csr"
+        },
+        "businessUnit": "CDN_Eng",
+        "city": "Denver",
+        "organization": "KableTown",
+        "hostname": "foober.com",
+        "country": "US",
+        "state": "Colorado",
+        "version": "1"
+      }
+    }
+
+|
+
+**GET /api/1.1/deliveryservices/hostname/:hostname/sslkeys.json**
+
+  Authentication Required: Yes
+
+  Role Required: Admin
+
+  **Request Route Parameters**
+
+  +--------------+----------+---------------------------------------------------+
+  |     Name     | Required |                    Description                    |
+  +==============+==========+===================================================+
+  | ``hostname`` | yes      | pristine hostname of the desired delivery service |
+  +--------------+----------+---------------------------------------------------+
+
+  **Request Query Parameters**
+
+  +-------------+----------+--------------------------------+
+  |     Name    | Required |          Description           |
+  +=============+==========+================================+
+  | ``version`` | no       | The version number to retrieve |
+  +-------------+----------+--------------------------------+
+
+  **Response Properties**
+
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  |    Parameter     |  Type  |                                                               Description                                                               |
+  +==================+========+=========================================================================================================================================+
+  | ``crt``          | string | base64 encoded crt file for delivery service                                                                                            |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``csr``          | string | base64 encoded csr file for delivery service                                                                                            |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``key``          | string | base64 encoded private key file for delivery service                                                                                    |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``businessUnit`` | string | The business unit entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``city``         | string | The city entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response          |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``organization`` | string | The organization entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response  |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``hostname``     | string | The hostname entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response      |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``country``      | string | The country entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response       |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``state``        | string | The state entered by the user when generating certs.  Field is optional and if not provided by the user will not be in response         |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+  | ``version``      | string | The version of the certificate record in Riak                                                                                           |
+  +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {  
+      "response": {
+        "certificate": {
+          "crt": "crt",
+          "key": "key",
+          "csr": "csr"
+        },
+        "businessUnit": "CDN_Eng",
+        "city": "Denver",
+        "organization": "KableTown",
+        "hostname": "foober.com",
+        "country": "US",
+        "state": "Colorado",
+        "version": "1"
+      }
+    }
+
+|
+
+**GET /api/1.1/deliveryservices/xmlId/:xmlid/sslkeys/delete.json**
+
+  Authentication Required: Yes
+
+  Role Required: Admin
+
+  **Request Route Parameters**
+
+  +-----------+----------+----------------------------------------+
+  |    Name   | Required |              Description               |
+  +===========+==========+========================================+
+  | ``xmlId`` | yes      | xml_id of the desired delivery service |
+  +-----------+----------+----------------------------------------+
+
+  **Request Query Parameters**
+
+  +-------------+----------+--------------------------------+
+  |     Name    | Required |          Description           |
+  +=============+==========+================================+
+  | ``version`` | no       | The version number to retrieve |
+  +-------------+----------+--------------------------------+
+
+  **Response Properties**
+
+  +--------------+--------+------------------+
+  |  Parameter   |  Type  |   Description    |
+  +==============+========+==================+
+  | ``response`` | string | success response |
+  +--------------+--------+------------------+
+
+  **Response Example** ::
+
+    {  
+      "response": "Successfully deleted ssl keys for <xml_id>"
+    }
+
+|
+  
+**POST /api/1.1/deliveryservices/sslkeys/generate**
+
+  Generates SSL crt, csr, and private key for a delivery service
+
+  Authentication Required: Yes
+
+  Role(s) Required: Admin
+
+  **Request Properties**
+
+  +--------------+---------+-------------------------------------------------+
+  |  Parameter   |   Type  |                   Description                   |
+  +==============+=========+=================================================+
+  | ``key``      | string  | xml_id of the delivery service                  |
+  +--------------+---------+-------------------------------------------------+
+  | ``version``  | string  | version of the keys being generated             |
+  +--------------+---------+-------------------------------------------------+
+  | ``hostname`` | string  | the *pristine hostname* of the delivery service |
+  +--------------+---------+-------------------------------------------------+
+  | ``country``  | string  |                                                 |
+  +--------------+---------+-------------------------------------------------+
+  | ``state``    | string  |                                                 |
+  +--------------+---------+-------------------------------------------------+
+  | ``city``     | string  |                                                 |
+  +--------------+---------+-------------------------------------------------+
+  | ``org``      | string  |                                                 |
+  +--------------+---------+-------------------------------------------------+
+  | ``unit``     | boolean |                                                 |
+  +--------------+---------+-------------------------------------------------+
+
+  **Request Example** ::
+
+    {
+      "key": "ds-01",
+      "businessUnit": "CDN Engineering",
+      "version": "3",
+      "hostname": "tr.ds-01.ott.kabletown.com",
+      "certificate": {
+        "key": "some_key",
+        "csr": "some_csr",
+        "crt": "some_crt"
+      },
+      "country": "US",
+      "organization": "Kabletown",
+      "city": "Denver",
+      "state": "Colorado"
+    }
+
+|
+
+  **Response Properties**
+
+  +--------------+--------+-----------------+
+  |  Parameter   |  Type  |   Description   |
+  +==============+========+=================+
+  | ``response`` | string | response string |
+  +--------------+--------+-----------------+
+  | ``version``  | string | API version     |
+  +--------------+--------+-----------------+
+
+  **Response Example** ::
+
+    {  
+      "response": "Successfully created ssl keys for ds-01"
+    }
+
+|
+  
+**POST /api/1.1/deliveryservices/sslkeys/add**
+
+  Allows user to add SSL crt, csr, and private key for a delivery service.
+
+  Authentication Required: Yes
+
+  Role(s) Required:  Admin
+
+  **Request Properties**
+
+  +-------------+--------+-------------------------------------+
+  |  Parameter  |  Type  |             Description             |
+  +=============+========+=====================================+
+  | ``key``     | string | xml_id of the delivery service      |
+  +-------------+--------+-------------------------------------+
+  | ``version`` | string | version of the keys being generated |
+  +-------------+--------+-------------------------------------+
+  | ``csr``     | string |                                     |
+  +-------------+--------+-------------------------------------+
+  | ``crt``     | string |                                     |
+  +-------------+--------+-------------------------------------+
+  | ``key``     | string |                                     |
+  +-------------+--------+-------------------------------------+
+
+  **Request Example** ::
+
+    {
+      "key": "ds-01",
+      "version": "1",
+      "certificate": {
+        "key": "some_key",
+        "csr": "some_csr",
+        "crt": "some_crt"
+      }
+    }
+
+|
+
+  **Response Properties**
+
+  +--------------+--------+-----------------+
+  |  Parameter   |  Type  |   Description   |
+  +==============+========+=================+
+  | ``response`` | string | response string |
+  +--------------+--------+-----------------+
+  | ``version``  | string | API version     |
+  +--------------+--------+-----------------+
+
+  **Response Example** ::
+
+    {  
+      "response": "Successfully added ssl keys for ds-01"
+    }
+
+
+|
+
+**POST /api/1.1/deliveryservices/request**
+
+  Allows a user to send delivery service request details to a specified email address.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Properties**
+
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  |  Parameter                             |  Type  | Required |           Description                                                                       |
+  +========================================+========+==========+=============================================================================================+
+  | ``emailTo``                            | string | yes      | The email to which the delivery service request will be sent.                               |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``details``                            | hash   | yes      | Parameters for the delivery service request.                                                |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>customer``                          | string | yes      | Name of the customer to associated with the delivery service.                               |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>deliveryProtocol``                  | string | yes      | Eg. http or http/https                                                                      |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>routingType``                       | string | yes      | Eg. DNS or HTTP Redirect                                                                    |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>serviceDesc``                       | string | yes      | A description of the delivery service.                                                      |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>peakBPSEstimate``                   | string | yes      | Used to manage cache efficiency and plan for capacity.                                      |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>peakTPSEstimate``                   | string | yes      | Used to manage cache efficiency and plan for capacity.                                      |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>maxLibrarySizeEstimate``            | string | yes      | Used to manage cache efficiency and plan for capacity.                                      |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>originURL``                         | string | yes      | The URL path to the origin server.                                                          |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>hasOriginDynamicRemap``             | bool   | yes      | This is a feature which allows services to use multiple origin URLs for the same service.   |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>originTestFile``                    | string | yes      | A URL path to a test file available on the origin server.                                   |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>hasOriginACLWhitelist``             | bool   | yes      | Is access to your origin restricted using an access control list (ACL or whitelist) of Ips? |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>originHeaders``                     | string | no       | Header values that must be passed to requests to your origin.                               |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>otherOriginSecurity``               | string | no       | Other origin security measures that need to be considered for access.                       |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>queryStringHandling``               | string | yes      | How to handle query strings that come with the request.                                     |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>rangeRequestHandling``              | string | yes      | How to handle range requests.                                                               |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>hasSignedURLs``                     | bool   | yes      | Are Urls signed?                                                                            |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>hasNegativeCachingCustomization``   | bool   | yes      | Any customization required for negative caching?                                            |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>negativeCachingCustomizationNote``  | string | yes      | Negative caching customization instructions.                                                |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>serviceAliases``                    | array  | no       | Service aliases which will be used for this service.                                        |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>rateLimitingGBPS``                  | int    | no       | Rate Limiting - Bandwidth (Gigabits per second)                                             |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>rateLimitingTPS``                   | int    | no       | Rate Limiting - Transactions/Second                                                         |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>overflowService``                   | string | no       | An overflow point (URL or IP address) used if rate limits are met.                          |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>headerRewriteEdge``                 | string | no       | Headers can be added or altered at each layer of the CDN.                                   |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>headerRewriteMid``                  | string | no       | Headers can be added or altered at each layer of the CDN.                                   |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>headerRewriteRedirectRouter``       | string | no       | Headers can be added or altered at each layer of the CDN.                                   |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+  | ``>notes``                             | string | no       | Additional instructions to provide the delivery service provisioning team.                  |
+  +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
+
+  **Request Example** ::
+
+    {
+       "emailTo": "foo@bar.com",
+       "details": {
+          "customer": "XYZ Corporation",
+          "contentType": "video-on-demand",
+          "deliveryProtocol": "http",
+          "routingType": "dns",
+          "serviceDesc": "service description goes here",
+          "peakBPSEstimate": "less-than-5-Gbps",
+          "peakTPSEstimate": "less-than-1000-TPS",
+          "maxLibrarySizeEstimate": "less-than-200-GB",
+          "originURL": "http://myorigin.com",
+          "hasOriginDynamicRemap": false,
+          "originTestFile": "http://myorigin.com/crossdomain.xml",
+          "hasOriginACLWhitelist": true,
+          "originHeaders": "",
+          "otherOriginSecurity": "",
+          "queryStringHandling": "ignore-in-cache-key-and-pass-up",
+          "rangeRequestHandling": "range-requests-not-used",
+          "hasSignedURLs": true,
+          "hasNegativeCachingCustomization": true,
+          "negativeCachingCustomizationNote": "negative caching instructions",
+          "serviceAliases": [
+             "http://alias1.com",
+             "http://alias2.com"
+          ],
+          "rateLimitingGBPS": 50,
+          "rateLimitingTPS": 5000,
+          "overflowService": "http://overflowcdn.com",
+          "headerRewriteEdge": "",
+          "headerRewriteMid": "",
+          "headerRewriteRedirectRouter": "",
+          "notes": ""
+       }
+    }
+
+|
+
+  **Response Properties**
+
+  +-------------+--------+----------------------------------+
+  |  Parameter  |  Type  |           Description            |
+  +=============+========+==================================+
+  | ``alerts``  | array  | A collection of alert messages.  |
+  +-------------+--------+----------------------------------+
+  | ``>level``  | string | Success, info, warning or error. |
+  +-------------+--------+----------------------------------+
+  | ``>text``   | string | Alert message.                   |
+  +-------------+--------+----------------------------------+
+  | ``version`` | string |                                  |
+  +-------------+--------+----------------------------------+
+
+  **Response Example** ::
+
+    {
+      "alerts": [
+            {
+                "level": "success",
+                "text": "Delivery Service request sent to foo@bar.com."
+            }
+        ]
+    }
+
+|
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/hwinfo.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/hwinfo.txt
new file mode 100644
index 0000000..cc45b38
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/hwinfo.txt
@@ -0,0 +1,67 @@
+.. 
+.. 
+.. 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.
+.. 
+
+
+.. _to-api-v11-hwinfo:
+
+Hardware Info
+=============
+
+.. _to-api-v11-hwinfo-route:
+
+/api/1.1/hwinfo
++++++++++++++++
+
+**GET /api/1.1/hwinfo.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +--------------------+--------+----------------------------------------------------------------------+
+  | Parameter          | Type   | Description                                                          |
+  +====================+========+======================================================================+
+  | ``serverId``       | string | Local unique identifier for this specific server's hardware info     |
+  +--------------------+--------+----------------------------------------------------------------------+
+  | ``serverHostName`` | string | Hostname for this specific server's hardware info                    |
+  +--------------------+--------+----------------------------------------------------------------------+
+  | ``lastUpdated``    | string | The Time and Date for the last update for this server.               |
+  +--------------------+--------+----------------------------------------------------------------------+
+  | ``val``            | string | Freeform value used to track anything about a server's hardware info |
+  +--------------------+--------+----------------------------------------------------------------------+
+  | ``description``    | string | Freeform description for this specific server's hardware info        |
+  +--------------------+--------+----------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "serverId": "odol-atsmid-cen-09",
+           "lastUpdated": "2014-05-27 09:06:02",
+           "val": "D1S4",
+           "description": "Physical Disk 0:1:0"
+        },
+        {
+           "serverId": "odol-atsmid-cen-09",
+           "lastUpdated": "2014-05-27 09:06:02",
+           "val": "D1S4",
+           "description": "Physical Disk 0:1:1"
+        }
+     ],
+    }
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/parameter.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/parameter.txt
new file mode 100644
index 0000000..1b83d01
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/parameter.txt
@@ -0,0 +1,136 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-parameter:
+
+Parameter
+=========
+
+.. _to-api-v11-parameters-route:
+
+/api/1.1/parameters
++++++++++++++++++++
+
+**GET /api/1.1/parameters.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +------------------+---------+--------------------------------------------------------------------------------+
+  |    Parameter     |  Type   |                    Description                                                 |
+  +==================+=========+================================================================================+
+  | ``last_updated`` | string  | The Time / Date this server entry was last updated                             |
+  +------------------+---------+--------------------------------------------------------------------------------+
+  | ``secure``       | boolean | When true, the parameter is accessible only by admin users. Defaults to false. |
+  +------------------+---------+--------------------------------------------------------------------------------+
+  | ``value``        | string  | The parameter value, only visible to admin if secure is true                   |
+  +------------------+---------+--------------------------------------------------------------------------------+
+  | ``name``         | string  | The parameter name                                                             |
+  +------------------+---------+--------------------------------------------------------------------------------+
+  | ``config_file``  | string  | The parameter config_file                                                      |
+  +------------------+---------+--------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "last_updated": "2012-09-17 21:41:22",
+           "secure": 0,
+           "value": "foo.bar.net",
+           "name": "domain_name",
+           "config_file": "FooConfig.xml"
+        },
+        {
+           "last_updated": "2012-09-17 21:41:22",
+           "secure": 0,
+           "value": "0,1,2,3,4,5,6",
+           "name": "Drive_Letters",
+           "config_file": "storage.config"
+        },
+        {
+           "last_updated": "2012-09-17 21:41:22",
+           "secure": 0,
+           "value": "STRING __HOSTNAME__",
+           "name": "CONFIG proxy.config.proxy_name",
+           "config_file": "records.config"
+        }
+     ],
+    }
+
+|
+
+**GET /api/1.1/parameters/profile/:name.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +------------------+----------+-------------+
+  |       Name       | Required | Description |
+  +==================+==========+=============+
+  | ``profile_name`` | yes      |             |
+  +------------------+----------+-------------+
+
+  **Response Properties**
+
+  +------------------+---------+--------------------------------------------------------------------------------+
+  |    Parameter     |  Type   |                    Description                                                 |
+  +==================+=========+================================================================================+
+  | ``last_updated`` | string  | The Time / Date this server entry was last updated                             |
+  +------------------+---------+--------------------------------------------------------------------------------+
+  | ``secure``       | boolean | When true, the parameter is accessible only by admin users. Defaults to false. |
+  +------------------+---------+--------------------------------------------------------------------------------+
+  | ``value``        | string  | The parameter value, only visible to admin if secure is true                   |
+  +------------------+---------+--------------------------------------------------------------------------------+
+  | ``name``         | string  | The parameter name                                                             |
+  +------------------+---------+--------------------------------------------------------------------------------+
+  | ``config_file``  | string  | The parameter config_file                                                      |
+  +------------------+---------+--------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "last_updated": "2012-09-17 21:41:22",
+           "secure": 0,
+           "value": "foo.bar.net",
+           "name": "domain_name",
+           "config_file": "FooConfig.xml"
+        },
+        {
+           "last_updated": "2012-09-17 21:41:22",
+           "secure": 0,
+           "value": "0,1,2,3,4,5,6",
+           "name": "Drive_Letters",
+           "config_file": "storage.config"
+        },
+        {
+           "last_updated": "2012-09-17 21:41:22",
+           "secure": 0,
+           "value": "STRING __HOSTNAME__",
+           "name": "CONFIG proxy.config.proxy_name",
+           "config_file": "records.config"
+        }
+     ],
+    }
+
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/phys_location.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/phys_location.txt
new file mode 100644
index 0000000..6ebaff0
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/phys_location.txt
@@ -0,0 +1,449 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-phys-loc:
+
+Physical Location
+=================
+
+.. _to-api-v11-phys-loc-route:
+
+/api/1.1/phys_locations
++++++++++++++++++++++++
+
+**GET /api/1.1/phys_locations**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``address``           | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``city``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``comments``          | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``email``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``id``                | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``lastUpdated``       | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``name``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``phone``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``poc``               | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``region``            | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``regionId``          | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``shortName``         | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``state``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``zip``               | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "region": "Mile High",
+           "region": "4",
+           "poc": "Jane Doe",
+           "lastUpdated": "2014-10-02 08:22:43",
+           "name": "Albuquerque",
+           "comments": "Albuquerque",
+           "phone": "(123) 555-1111",
+           "state": "NM",
+           "email": "jane.doe@email.com",
+           "city": "Albuquerque",
+           "zip": "87107",
+           "id": "2",
+           "address": "123 East 3rd St",
+           "shortName": "Albuquerque"
+        },
+        {
+           "region": "Mile High",
+           "region": "4",
+           "poc": "Jane Doe",
+           "lastUpdated": "2014-10-02 08:22:43",
+           "name": "Albuquerque",
+           "comments": "Albuquerque",
+           "phone": "(123) 555-1111",
+           "state": "NM",
+           "email": "jane.doe@email.com",
+           "city": "Albuquerque",
+           "zip": "87107",
+           "id": "2",
+           "address": "123 East 3rd St",
+           "shortName": "Albuquerque"
+        }
+     ]
+    }
+
+|
+
+**GET /api/1.1/phys_locations/trimmed.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------+---------+------------------------------------------------+
+  | Parameter            | Type    | Description                                    |
+  +======================+=========+================================================+
+  |``name``              | string  |                                                |
+  +----------------------+---------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "name": "Albuquerque"
+        },
+        {
+           "name": "Ashburn"
+        }
+     ]
+    }
+
+|
+
+
+**GET /api/1.1/phys_locations/:id**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------+----------+---------------------------------------------+
+  |   Name    | Required |                Description                  |
+  +===========+==========+=============================================+
+  | ``id``    | yes      | Physical location ID.                       |
+  +-----------+----------+---------------------------------------------+
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``address``           | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``city``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``comments``          | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``email``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``id``                | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``lastUpdated``       | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``name``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``phone``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``poc``               | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``region``            | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``regionId``          | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``shortName``         | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``state``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``zip``               | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "region": "Mile High",
+           "region": "4",
+           "poc": "Jane Doe",
+           "lastUpdated": "2014-10-02 08:22:43",
+           "name": "Albuquerque",
+           "comments": "Albuquerque",
+           "phone": "(123) 555-1111",
+           "state": "NM",
+           "email": "jane.doe@email.com",
+           "city": "Albuquerque",
+           "zip": "87107",
+           "id": "2",
+           "address": "123 East 3rd St",
+           "shortName": "Albuquerque"
+        }
+     ]
+    }
+
+|
+
+**PUT /api/1.1/phys_locations/:id**
+  Update a physical location
+
+  Authentication Required: Yes
+
+  Role(s) Required: admin or oper
+
+  **Request Route Parameters**
+
+  +-------------------+----------+------------------------------------------------+
+  | Name              |   Type   |                 Description                    |
+  +===================+==========+================================================+
+  | ``id``            | int      | Physical location id.                          |
+  +-------------------+----------+------------------------------------------------+
+
+  **Request Properties**
+
+  +-------------------+----------+------------------------------------------------+
+  | Parameter         | Required | Description                                    |
+  +===================+==========+================================================+
+  | ``address``       |    yes   | Physical location address.                     |
+  +-------------------+----------+------------------------------------------------+
+  | ``city``          |    yes   | Physical location city.                        |
+  +-------------------+----------+------------------------------------------------+
+  | ``comments``      |    no    | Physical location comments.                    |
+  +-------------------+----------+------------------------------------------------+
+  | ``email``         |    no    | Physical location email.                       |
+  +-------------------+----------+------------------------------------------------+
+  | ``name``          |    yes   | Physical location name.                        |
+  +-------------------+----------+------------------------------------------------+
+  | ``phone``         |    no    | Physical location phone.                       |
+  +-------------------+----------+------------------------------------------------+
+  | ``poc``           |    no    | Physical location point of contact.            |
+  +-------------------+----------+------------------------------------------------+
+  | ``regionId``      |    no    | Physical location region ID.                   |
+  +-------------------+----------+------------------------------------------------+
+  | ``shortName``     |    yes   | Physical location short name.                  |
+  +-------------------+----------+------------------------------------------------+
+  | ``state``         |    yes   | Physical location state.                       |
+  +-------------------+----------+------------------------------------------------+
+  | ``zip``           |    yes   | Physical location zip.                         |
+  +-------------------+----------+------------------------------------------------+
+
+  **Request Example** ::
+
+     {
+        "regionId": "1",
+        "poc": "Jane Doesssss",
+        "name": "Albuquerque",
+        "comments": "Albuquerque",
+        "phone": "(123) 555-1111",
+        "state": "NM",
+        "email": "jane.doe@email.com",
+        "city": "Albuquerque",
+        "zip": "87107",
+        "address": "123 East 9rd St",
+        "shortName": "Albuquerque"
+     }
+
+|
+
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``address``           | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``city``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``comments``          | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``email``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``id``                | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``lastUpdated``       | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``name``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``phone``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``poc``               | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``region``            | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``regionId``          | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``shortName``         | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``state``             | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``zip``               | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+
+  **Response Example** ::
+
+    {
+     "alerts": [
+        {
+            "level": "success",
+            "text": "Physical location update was successful."
+        }
+      ],
+     "response": [
+        {
+           "region": "Mile High",
+           "region": "4",
+           "poc": "Jane Doe",
+           "lastUpdated": "2014-10-02 08:22:43",
+           "name": "Albuquerque",
+           "comments": "Albuquerque",
+           "phone": "(123) 555-1111",
+           "state": "NM",
+           "email": "jane.doe@email.com",
+           "city": "Albuquerque",
+           "zip": "87107",
+           "id": "2",
+           "address": "123 East 3rd St",
+           "shortName": "Albuquerque"
+        }
+     ]
+    }
+
+|
+
+
+**POST /api/1.1/regions/:region_name/phys_locations**
+  Create physical location.
+
+  Authentication Required: Yes
+
+  Role(s) Required: admin or oper
+
+  region_name: the name of the region to create physical location into.
+
+  **Request Route Parameters**
+
+  +-----------------+----------+-----------------------------------+
+  | Name            | Required | Description                       |
+  +=================+==========+===================================+
+  | ``region_name`` | yes      | The name of the physical location |
+  +-----------------+----------+-----------------------------------+
+
+  **Request Properties**
+
+  +-----------------+----------+---------------------------------------------------+
+  | Parameter       | Required | Description                                       |
+  +=================+==========+===================================================+
+  | ``name``        | yes      | The name of the location                          |
+  +-----------------+----------+---------------------------------------------------+
+  | ``shortName``   | yes      | The short name of the location                    |
+  +-----------------+----------+---------------------------------------------------+
+  | ``address``     | yes      |                                                   |
+  +-----------------+----------+---------------------------------------------------+
+  | ``city``        | yes      |                                                   |
+  +-----------------+----------+---------------------------------------------------+
+  | ``state``       | yes      |                                                   |
+  +-----------------+----------+---------------------------------------------------+
+  | ``zip``         | yes      |                                                   |
+  +-----------------+----------+---------------------------------------------------+
+  | ``phone``       | no       |                                                   |
+  +-----------------+----------+---------------------------------------------------+
+  | ``poc``         | no       | Point of contact                                  |
+  +-----------------+----------+---------------------------------------------------+
+  | ``email``       | no       |                                                   |
+  +-----------------+----------+---------------------------------------------------+
+  | ``comments``    | no       |                                                   |
+  +-----------------+----------+---------------------------------------------------+
+
+  **Request Example** ::
+
+    {
+        "name" : "my physical location1",
+        "shortName" : "myphylocation1",
+        "address" : "",
+        "city" : "Shanghai",
+        "state": "SH",
+        "zip": "200000",
+        "comments": "this is physical location1"
+    }
+
+|
+
+  **Response Properties**
+
+  +-----------------+--------+---------------------------------------------------+
+  | Parameter       | Type   | Description                                       |
+  +=================+========+===================================================+
+  | ``id``          | string | The id of the physical location created.          |
+  +-----------------+--------+---------------------------------------------------+
+  | ``name``        | string | The name of the location                          |
+  +-----------------+--------+---------------------------------------------------+
+  | ``shortName``   | string | The short name of the location                    |
+  +-----------------+--------+---------------------------------------------------+
+  | ``regionName``  | string | The region name the physical location belongs to. |
+  +-----------------+--------+---------------------------------------------------+
+  | ``regionId``    | string |                                                   |
+  +-----------------+--------+---------------------------------------------------+
+  | ``address``     | string |                                                   |
+  +-----------------+--------+---------------------------------------------------+
+  | ``city``        | string |                                                   |
+  +-----------------+--------+---------------------------------------------------+
+  | ``state``       | string |                                                   |
+  +-----------------+--------+---------------------------------------------------+
+  | ``zip``         | string |                                                   |
+  +-----------------+--------+---------------------------------------------------+
+  | ``phone``       | string |                                                   |
+  +-----------------+--------+---------------------------------------------------+
+  | ``poc``         | string | Point of contact                                  |
+  +-----------------+--------+---------------------------------------------------+
+  | ``email``       | string |                                                   |
+  +-----------------+--------+---------------------------------------------------+
+  | ``comments``    | string |                                                   |
+  +-----------------+--------+---------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+      "response": {
+        'shortName': 'myphylocati',
+        'regionName': 'myregion1',
+        'name': 'my physical location1',
+        'poc': '',
+        'phone': '',
+        'comments': 'this is physical location1',
+        'state': 'SH',
+        'email': '',
+        'zip': '20000',
+        'region_id': '20',
+        'city': 'Shanghai',
+        'address': '',
+        'id': '200'
+     }
+   }
+
+|
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/profile.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/profile.txt
new file mode 100644
index 0000000..5c37690
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/profile.txt
@@ -0,0 +1,129 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-profile:
+
+Profiles
+========
+
+.. _to-api-v11-profiles-route:
+
+/api/1.1/profiles
++++++++++++++++++
+
+**GET /api/1.1/profiles**
+
+	Authentication Required: Yes
+
+	Role(s) Required: None
+
+	**Response Properties**
+
+	+-----------------+--------+----------------------------------------------------+
+	|    Parameter    |  Type  |                    Description                     |
+	+=================+========+====================================================+
+	| ``lastUpdated`` | array  | The Time / Date this server entry was last updated |
+	+-----------------+--------+----------------------------------------------------+
+	| ``name``        | string | The name for the profile                           |
+	+-----------------+--------+----------------------------------------------------+
+	| ``id``          | string | Primary key                                        |
+	+-----------------+--------+----------------------------------------------------+
+	| ``description`` | string | The description for the profile                    |
+	+-----------------+--------+----------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+            "lastUpdated": "2012-10-08 19:34:45",
+            "name": "CCR_TOP",
+            "id": "8",
+            "description": "Content Router for top.foobar.net"
+        }
+     ]
+    }
+
+|
+
+**GET /api/1.1/profiles/trimmed**
+
+	Authentication Required: Yes
+
+	Role(s) Required: None
+
+	**Response Properties**
+
+	+-----------------+--------+----------------------------------------------------+
+	|    Parameter    |  Type  |                    Description                     |
+	+=================+========+====================================================+
+	| ``name``        | string | The name for the profile                           |
+	+-----------------+--------+----------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+            "name": "CCR_TOP"
+        }
+     ]
+    }
+
+|
+
+**GET /api/1.1/profiles/:id**
+
+	Authentication Required: Yes
+
+	Role(s) Required: None
+
+	**Request Route Parameters**
+
+	+-----------------+------------+------------------------------------------------+
+	|    Parameter    |  Required  |                    Description                 |
+	+=================+============+================================================+
+	| ``id``          |    yes     | The ID of the profile.                         |
+	+-----------------+------------+------------------------------------------------+
+
+	**Response Properties**
+
+	+-----------------+--------+----------------------------------------------------+
+	|    Parameter    |  Type  |                    Description                     |
+	+=================+========+====================================================+
+	| ``lastUpdated`` | array  | The Time / Date this server entry was last updated |
+	+-----------------+--------+----------------------------------------------------+
+	| ``name``        | string | The name for the profile                           |
+	+-----------------+--------+----------------------------------------------------+
+	| ``id``          | string | Primary key                                        |
+	+-----------------+--------+----------------------------------------------------+
+	| ``description`` | string | The description for the profile                    |
+	+-----------------+--------+----------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+            "lastUpdated": "2012-10-08 19:34:45",
+            "name": "CCR_TOP",
+            "id": "8",
+            "description": "Content Router for top.foobar.net"
+        }
+     ]
+    }
+
+|
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/region.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/region.txt
new file mode 100644
index 0000000..faddbb1
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/region.txt
@@ -0,0 +1,235 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-region:
+
+Regions
+=======
+
+.. _to-api-v11-regions-route:
+
+/api/1.1/regions
+++++++++++++++++
+
+**GET /api/1.1/regions**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``id``                | string | Region ID.                                     |
+  +----------------------+--------+------------------------------------------------+
+  |``name``              | string | Region name.                                   |
+  +----------------------+--------+------------------------------------------------+
+  |``division``          | string | Division ID.                                   |
+  +----------------------+--------+------------------------------------------------+
+  |``divisionName``      | string | Division name.                                 |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "id": "6",
+           "name": "Atlanta",
+           "division": "2",
+           "divisionName": "West"
+        },
+        {
+           "id": "7",
+           "name": "Denver",
+           "division": "2",
+           "divisionName": "West"
+        },
+     ]
+    }
+
+
+**GET /api/1.1/regions/:id**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------+----------+---------------------------------------------+
+  |   Name    | Required |                Description                  |
+  +===========+==========+=============================================+
+  |   ``id``  |   yes    | Region id.                                  |
+  +-----------+----------+---------------------------------------------+
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``id``                | string | Region ID.                                     |
+  +----------------------+--------+------------------------------------------------+
+  |``name``              | string | Region name.                                   |
+  +----------------------+--------+------------------------------------------------+
+  |``division``          | string | Division ID.                                   |
+  +----------------------+--------+------------------------------------------------+
+  |``divisionName``      | string | Division name.                                 |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "id": "6",
+           "name": "Atlanta",
+           "division": "2",
+           "divisionName": "West"
+        }
+     ]
+    }
+
+
+**PUT /api/1.1/regions/:id**
+  Update a region
+
+  Authentication Required: Yes
+
+  Role(s) Required: admin or oper
+
+  **Request Route Parameters**
+
+  +-------------------+----------+------------------------------------------------+
+  | Name              |   Type   |                 Description                    |
+  +===================+==========+================================================+
+  | ``id``            | int      | Region id.                                     |
+  +-------------------+----------+------------------------------------------------+
+
+  **Request Properties**
+
+  +----------------+----------+--------------------------+
+  | Parameter      | Required | Description              |
+  +================+==========+==========================+
+  | ``name``       | yes      | The name of the region   |
+  +----------------+----------+--------------------------+
+  | ``division``   | yes      | The division Id          |
+  +----------------+----------+--------------------------+
+
+  **Request Example** ::
+
+    {
+        "name": "myregion1",
+        "division": "4"
+    }
+
+|
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``division``          | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``divisionName``      | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``name``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``id``                | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``lastUpdated``       | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+	{
+		"alerts": [
+			{
+				"level": "success",
+				"text": "Region update was successful."
+			}
+		],
+		"response": {
+			"id": "1",
+			"lastUpdated": "2014-03-18 08:57:39",
+			"name": "myregion1",
+			"division": "4",
+			"divisionName": "mydivision1"
+		}
+	}
+|
+
+**POST /api/1.1/divisions/:division_name/regions**
+  Create Region
+
+  Authentication Required: Yes
+
+  Role(s) Required: admin or oper
+
+  division_name - The name of division to create new region into.
+
+  ** Request Route Parameters**
+
+  +-------------------+----------+------------------------------------------------+
+  | Name              | Required | Description                                    |
+  +===================+==========+================================================+
+  | ``division_name`` | yes      | The name of division will create new region in |
+  +-------------------+----------+------------------------------------------------+
+
+  **Request Properties**
+
+  +-------------------+----------+------------------------------------------+
+  | Parameter         | Required | Description                              |
+  +===================+==========+==========================================+
+  | ``name``          | yes      | The name of the region                   |
+  +-------------------+----------+------------------------------------------+
+
+  **Request Example** ::
+
+    {
+        "name": "myregion1",
+    }
+
+|
+
+  **Response Properties**
+
+  +-------------------+--------+-------------------------------------------+
+  | Parameter         | Type   | Description                               |
+  +===================+========+===========================================+
+  | ``name``          | string | name of region created                    |
+  +-------------------+--------+-------------------------------------------+
+  | ``id``            | string | id of region created                      |
+  +-------------------+--------+-------------------------------------------+
+  | ``divisionName``  | string | the division name the region belongs to.  |
+  +-------------------+--------+-------------------------------------------+
+  | ``divisionId``    | string | the id of division the region belongs to. |
+  +-------------------+--------+-------------------------------------------+
+
+  **Response Example** ::
+
+    {
+      "response": {
+        'divisionName': 'mydivision1',
+        'divsionId': '4',
+        'name': 'myregion1',
+        'id': '19'
+       }
+    }
+
+|
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/role.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/role.txt
new file mode 100644
index 0000000..bf3337c
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/role.txt
@@ -0,0 +1,58 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-roles:
+
+Roles
+=====
+
+.. _to-api-v11-roles-route:
+
+/api/1.1/roles
+++++++++++++++
+
+**GET /api/1.1/roles.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``name``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``id``                | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``privLevel``         | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``description``       | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+     "response": [
+        {
+           "name": "read-only",
+           "id": "2",
+           "privLevel": "10",
+           "description": "read-only user"
+        }
+     ],
+    }
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/server.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/server.txt
new file mode 100644
index 0000000..44f1292
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/server.txt
@@ -0,0 +1,630 @@
+..
+..
+.. 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.
+..
+
+.. _to-api-v11-server:
+
+Server
+======
+
+.. _to-api-v11-servers-route:
+
+/api/1.1/servers
+++++++++++++++++
+
+**GET /api/1.1/servers**
+
+  Retrieves properties of CDN servers.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Query Parameters**
+
+  +--------------------+----------+---------------------------------------------+
+  |   Name             | Required |                Description                  |
+  +====================+==========+=============================================+
+  | ``dsId``           | no       | Used to filter servers by delivery service. |
+  +--------------------+----------+---------------------------------------------+
+  | ``status``         | no       | Used to filter servers by status.           |
+  +--------------------+----------+---------------------------------------------+
+  | ``type``           | no       | Used to filter servers by type.             |
+  +--------------------+----------+---------------------------------------------+
+
+  **Response Properties**
+
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  |     Parameter      |  Type  |                                                Description                                                 |
+  +====================+========+============================================================================================================+
+  | ``cachegroup``     | string | The cache group name (see :ref:`to-api-v11-cachegroup`).                                                   |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``cachegroupId``   | string | The cache group id.                                                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``cdnId``          | string | Id of the CDN to which the server belongs to.                                                              |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``cdnName``        | string | Name of the CDN to which the server belongs to.                                                            |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``domainName``     | string | The domain name part of the FQDN of the cache.                                                             |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``guid``           | string | An identifier used to uniquely identify the server.                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``hostName``       | string | The host name part of the cache.                                                                           |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``httpsPort``      | string | The HTTPS port on which the main application listens (443 in most cases).                                  |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``id``             | string | The server id (database row number).                                                                       |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloIpAddress``   | string | The IPv4 address of the lights-out-management port.                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloIpGateway``   | string | The IPv4 gateway address of the lights-out-management port.                                                |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloIpNetmask``   | string | The IPv4 netmask of the lights-out-management port.                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloPassword``    | string | The password of the of the lights-out-management user (displays as ****** unless you are an 'admin' user). |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloUsername``    | string | The user name for lights-out-management.                                                                   |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``interfaceMtu``   | string | The Maximum Transmission Unit (MTU) to configure for ``interfaceName``.                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``interfaceName``  | string | The network interface name used for serving traffic.                                                       |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ip6Address``     | string | The IPv6 address/netmask for ``interfaceName``.                                                            |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ip6Gateway``     | string | The IPv6 gateway for ``interfaceName``.                                                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ipAddress``      | string | The IPv4 address for ``interfaceName``.                                                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ipGateway``      | string | The IPv4 gateway for ``interfaceName``.                                                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ipNetmask``      | string | The IPv4 netmask for ``interfaceName``.                                                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``lastUpdated``    | string | The Time and Date for the last update for this server.                                                     |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``mgmtIpAddress``  | string | The IPv4 address of the management port (optional).                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``mgmtIpGateway``  | string | The IPv4 gateway of the management port (optional).                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``mgmtIpNetmask``  | string | The IPv4 netmask of the management port (optional).                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``offlineReason``  | string | A user-entered reason why the server is in ADMIN_DOWN or OFFLINE status.                                   |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``physLocation``   | string | The physical location name (see :ref:`to-api-v11-phys-loc`).                                               |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``physLocationId`` | string | The physical location id (see :ref:`to-api-v11-phys-loc`).                                                 |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``profile``        | string | The assigned profile name (see :ref:`to-api-v11-profile`).                                                 |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``profileDesc``    | string | The assigned profile description (see :ref:`to-api-v11-profile`).                                          |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``profileId``      | string | The assigned profile Id (see :ref:`to-api-v11-profile`).                                                   |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``rack``           | string | A string indicating rack location.                                                                         |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``routerHostName`` | string | The human readable name of the router.                                                                     |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``routerPortName`` | string | The human readable name of the router port.                                                                |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``status``         | string | The Status string (See :ref:`to-api-v11-status`).                                                          |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``statusId``       | string | The Status id (See :ref:`to-api-v11-status`).                                                              |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``tcpPort``        | string | The default TCP port on which the main application listens (80 for a cache in most cases).                 |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``type``           | string | The name of the type of this server (see :ref:`to-api-v11-type`).                                          |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``typeId``         | string | The id of the type of this server (see :ref:`to-api-v11-type`).                                            |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``updPending``     |  bool  |                                                                                                            |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+   {
+      "response": [
+          {
+              "cachegroup": "us-il-chicago",
+              "cachegroupId": "3",
+              "cdnId": "3",
+              "cdnName": "CDN-1",
+              "domainName": "chi.kabletown.net",
+              "guid": null,
+              "hostName": "atsec-chi-00",
+              "id": "19",
+              "iloIpAddress": "172.16.2.6",
+              "iloIpGateway": "172.16.2.1",
+              "iloIpNetmask": "255.255.255.0",
+              "iloPassword": "********",
+              "iloUsername": "",
+              "interfaceMtu": "9000",
+              "interfaceName": "bond0",
+              "ip6Address": "2033:D0D0:3300::2:2/64",
+              "ip6Gateway": "2033:D0D0:3300::2:1",
+              "ipAddress": "10.10.2.2",
+              "ipGateway": "10.10.2.1",
+              "ipNetmask": "255.255.255.0",
+              "lastUpdated": "2015-03-08 15:57:32",
+              "mgmtIpAddress": "",
+              "mgmtIpGateway": "",
+              "mgmtIpNetmask": "",
+              "offlineReason": "N/A",
+              "physLocation": "plocation-chi-1",
+              "physLocationId": "9",
+              "profile": "EDGE1_CDN1_421_SSL",
+              "profileDesc": "EDGE1_CDN1_421_SSL profile",
+              "profileId": "12",
+              "rack": "RR 119.02",
+              "routerHostName": "rtr-chi.kabletown.net",
+              "routerPortName": "2",
+              "status": "ONLINE",
+              "statusId": "6",
+              "tcpPort": "80",
+              "httpsPort": "443",
+              "type": "EDGE",
+              "typeId": "3",
+              "updPending": false
+          },
+          {
+          ... more server data
+          }
+        ]
+    }
+
+|
+
+**GET /api/1.1/servers/:id**
+
+  Retrieves properties of a CDN server by server ID.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------+----------+---------------------------------------------+
+  |   Name    | Required |                Description                  |
+  +===========+==========+=============================================+
+  |   ``id``  |   yes    | Server id.                                  |
+  +-----------+----------+---------------------------------------------+
+
+  **Response Properties**
+
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  |     Parameter      |  Type  |                                                Description                                                 |
+  +====================+========+============================================================================================================+
+  | ``cachegroup``     | string | The cache group name (see :ref:`to-api-v11-cachegroup`).                                                   |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``cachegroupId``   | string | The cache group id.                                                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``cdnId``          | string | Id of the CDN to which the server belongs to.                                                              |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``cdnName``        | string | Name of the CDN to which the server belongs to.                                                            |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``domainName``     | string | The domain name part of the FQDN of the cache.                                                             |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``guid``           | string | An identifier used to uniquely identify the server.                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``hostName``       | string | The host name part of the cache.                                                                           |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``httpsPort``      | string | The HTTPS port on which the main application listens (443 in most cases).                                  |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``id``             | string | The server id (database row number).                                                                       |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloIpAddress``   | string | The IPv4 address of the lights-out-management port.                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloIpGateway``   | string | The IPv4 gateway address of the lights-out-management port.                                                |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloIpNetmask``   | string | The IPv4 netmask of the lights-out-management port.                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloPassword``    | string | The password of the of the lights-out-management user (displays as ****** unless you are an 'admin' user). |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``iloUsername``    | string | The user name for lights-out-management.                                                                   |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``interfaceMtu``   | string | The Maximum Transmission Unit (MTU) to configure for ``interfaceName``.                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``interfaceName``  | string | The network interface name used for serving traffic.                                                       |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ip6Address``     | string | The IPv6 address/netmask for ``interfaceName``.                                                            |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ip6Gateway``     | string | The IPv6 gateway for ``interfaceName``.                                                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ipAddress``      | string | The IPv4 address for ``interfaceName``.                                                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ipGateway``      | string | The IPv4 gateway for ``interfaceName``.                                                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``ipNetmask``      | string | The IPv4 netmask for ``interfaceName``.                                                                    |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``lastUpdated``    | string | The Time and Date for the last update for this server.                                                     |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``mgmtIpAddress``  | string | The IPv4 address of the management port (optional).                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``mgmtIpGateway``  | string | The IPv4 gateway of the management port (optional).                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``mgmtIpNetmask``  | string | The IPv4 netmask of the management port (optional).                                                        |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``offlineReason``  | string | A user-entered reason why the server is in ADMIN_DOWN or OFFLINE status.                                   |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``physLocation``   | string | The physical location name (see :ref:`to-api-v11-phys-loc`).                                               |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``physLocationId`` | string | The physical location id (see :ref:`to-api-v11-phys-loc`).                                                 |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``profile``        | string | The assigned profile name (see :ref:`to-api-v11-profile`).                                                 |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``profileDesc``    | string | The assigned profile description (see :ref:`to-api-v11-profile`).                                          |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``profileId``      | string | The assigned profile Id (see :ref:`to-api-v11-profile`).                                                   |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``rack``           | string | A string indicating rack location.                                                                         |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``routerHostName`` | string | The human readable name of the router.                                                                     |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``routerPortName`` | string | The human readable name of the router port.                                                                |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``status``         | string | The Status string (See :ref:`to-api-v11-status`).                                                          |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``statusId``       | string | The Status id (See :ref:`to-api-v11-status`).                                                              |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``tcpPort``        | string | The default TCP port on which the main application listens (80 for a cache in most cases).                 |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``type``           | string | The name of the type of this server (see :ref:`to-api-v11-type`).                                          |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``typeId``         | string | The id of the type of this server (see :ref:`to-api-v11-type`).                                            |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+  | ``updPending``     |  bool  |                                                                                                            |
+  +--------------------+--------+------------------------------------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+   {
+      "response": [
+          {
+              "cachegroup": "us-il-chicago",
+              "cachegroupId": "3",
+              "cdnId": "3",
+              "cdnName": "CDN-1",
+              "domainName": "chi.kabletown.net",
+              "guid": null,
+              "hostName": "atsec-chi-00",
+              "id": "19",
+              "iloIpAddress": "172.16.2.6",
+              "iloIpGateway": "172.16.2.1",
+              "iloIpNetmask": "255.255.255.0",
+              "iloPassword": "********",
+              "iloUsername": "",
+              "interfaceMtu": "9000",
+              "interfaceName": "bond0",
+              "ip6Address": "2033:D0D0:3300::2:2/64",
+              "ip6Gateway": "2033:D0D0:3300::2:1",
+              "ipAddress": "10.10.2.2",
+              "ipGateway": "10.10.2.1",
+              "ipNetmask": "255.255.255.0",
+              "lastUpdated": "2015-03-08 15:57:32",
+              "mgmtIpAddress": "",
+              "mgmtIpGateway": "",
+              "mgmtIpNetmask": "",
+              "offlineReason": "N/A",
+              "physLocation": "plocation-chi-1",
+              "physLocationId": "9",
+              "profile": "EDGE1_CDN1_421_SSL",
+              "profileDesc": "EDGE1_CDN1_421_SSL profile",
+              "profileId": "12",
+              "rack": "RR 119.02",
+              "routerHostName": "rtr-chi.kabletown.net",
+              "routerPortName": "2",
+              "status": "ONLINE",
+              "statusId": "6",
+              "tcpPort": "80",
+              "httpsPort": "443",
+              "type": "EDGE",
+              "typeId": "3",
+              "updPending": false
+          }
+        ]
+    }
+
+|
+
+
+**GET /api/1.1/servers/summary**
+
+  Retrieves a count of CDN servers by type.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +-----------+--------+------------------------------------------------------------------------+
+  | Parameter |  Type  |                             Description                                |
+  +===========+========+========================================================================+
+  | ``count`` | int    | The number of servers of this type in this instance of Traffic Ops.    |
+  +-----------+--------+------------------------------------------------------------------------+
+  | ``type``  | string | The name of the type of the server count (see :ref:`to-api-v11-type`). |
+  +-----------+--------+------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+      "response": [
+        {
+          "count": 4,
+          "type": "CCR"
+        },
+        {
+          "count": 55,
+          "type": "EDGE"
+        },
+        {
+          "type": "MID",
+          "count": 18
+        },
+        {
+          "count": 0,
+          "type": "INFLUXDB"
+        },
+        {
+          "count": 4,
+          "type": "RASCAL"
+        }
+    }
+
+|
+
+**GET /api/1.1/servers/hostname/:name/details**
+
+  Retrieves the details of a server.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +----------+----------+----------------------------------+
+  |   Name   | Required |           Description            |
+  +==========+==========+==================================+
+  | ``name`` | yes      | The host name part of the cache. |
+  +----------+----------+----------------------------------+
+
+  **Response Properties**
+
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  |      Parameter       |  Type  |                                                 Description                                                 |
+  +======================+========+=============================================================================================================+
+  | ``cachegroup``       | string | The cache group name (see :ref:`to-api-v11-cachegroup`).                                                    |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``deliveryservices`` | array  | Array of strings with the delivery service ids assigned (see :ref:`to-api-v11-ds`).                         |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``domainName``       | string | The domain name part of the FQDN of the cache.                                                              |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``hardwareInfo``     | hash   | Hwinfo struct (see :ref:`to-api-v11-hwinfo`).                                                               |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``hostName``         | string | The host name part of the cache.                                                                            |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``id``               | string | The server id (database row number).                                                                        |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``iloIpAddress``     | string | The IPv4 address of the lights-out-management port.                                                         |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``iloIpGateway``     | string | The IPv4 gateway address of the lights-out-management port.                                                 |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``iloIpNetmask``     | string | The IPv4 netmask of the lights-out-management port.                                                         |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``iloPassword``      | string | The password of the of the lights-out-management user  (displays as ****** unless you are an 'admin' user). |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``iloUsername``      | string | The user name for lights-out-management.                                                                    |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``interfaceMtu``     | string | The Maximum Transmission Unit (MTU) to configure for ``interfaceName``.                                     |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``interfaceName``    | string | The network interface name used for serving traffic.                                                        |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``ip6Address``       | string | The IPv6 address/netmask for ``interfaceName``.                                                             |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``ip6Gateway``       | string | The IPv6 gateway for ``interfaceName``.                                                                     |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``ipAddress``        | string | The IPv4 address for ``interfaceName``.                                                                     |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``ipGateway``        | string | The IPv4 gateway for ``interfaceName``.                                                                     |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``ipNetmask``        | string | The IPv4 netmask for ``interfaceName``.                                                                     |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``lastUpdated``      | string | The Time/Date of the last update for this server.                                                           |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``mgmtIpAddress``    | string | The IPv4 address of the management port (optional).                                                         |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``mgmtIpGateway``    | string | The IPv4 gateway of the management port (optional).                                                         |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``mgmtIpNetmask``    | string | The IPv4 netmask of the management port (optional).                                                         |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``physLocation``     | string | The physical location name (see :ref:`to-api-v11-phys-loc`).                                                |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``profile``          | string | The assigned profile name (see :ref:`to-api-v11-profile`).                                                  |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``rack``             | string | A string indicating rack location.                                                                          |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``routerHostName``   | string | The human readable name of the router.                                                                      |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``routerPortName``   | string | The human readable name of the router port.                                                                 |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``status``           | string | The Status string (See :ref:`to-api-v11-status`).                                                           |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``tcpPort``          | string | The default TCP port on which the main application listens (80 for a cache in most cases).                  |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``httpsPort``        | string | The default HTTPS port on which the main application listens (443 for a cache in most cases).               |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``type``             | string | The name of the type of this server (see :ref:`to-api-v11-type`).                                           |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``xmppId``           | string | Deprecated.                                                                                                 |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+  | ``xmppPasswd``       | string | Deprecated.                                                                                                 |
+  +----------------------+--------+-------------------------------------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+      "response": {
+        "cachegroup": "us-il-chicago",
+        "deliveryservices": [
+          "1",
+          "2",
+          "3",
+          "4"
+        ],
+        "domainName": "chi.kabletown.net",
+        "hardwareInfo": {
+          "Physical Disk 0:1:3": "D1S2",
+          "Physical Disk 0:1:2": "D1S2",
+          "Physical Disk 0:1:15": "D1S2",
+          "Power Supply.Slot.2": "04.07.15",
+          "Physical Disk 0:1:24": "YS08",
+          "Physical Disk 0:1:1": "D1S2",
+          "Model": "PowerEdge R720xd",
+          "Physical Disk 0:1:22": "D1S2",
+          "Physical Disk 0:1:18": "D1S2",
+          "Enterprise UEFI Diagnostics": "4217A5",
+          "Lifecycle Controller": "1.0.8.42",
+          "Physical Disk 0:1:8": "D1S2",
+          "Manufacturer": "Dell Inc.",
+          "Physical Disk 0:1:6": "D1S2",
+          "SysMemTotalSize": "196608",
+          "PopulatedDIMMSlots": "24",
+          "Physical Disk 0:1:20": "D1S2",
+          "Intel(R) Ethernet 10G 2P X520 Adapter": "13.5.7",
+          "Physical Disk 0:1:14": "D1S2",
+          "BACKPLANE FIRMWARE": "1.00",
+          "Dell OS Drivers Pack, 7.0.0.29, A00": "7.0.0.29",
+          "Integrated Dell Remote Access Controller": "1.57.57",
+          "Physical Disk 0:1:5": "D1S2",
+          "ServiceTag": "D6XPDV1",
+          "PowerState": "2",
+          "Physical Disk 0:1:23": "D1S2",
+          "Physical Disk 0:1:25": "D903",
+          "BIOS": "1.3.6",
+          "Physical Disk 0:1:12": "D1S2",
+          "System CPLD": "1.0.3",
+          "Physical Disk 0:1:4": "D1S2",
+          "Physical Disk 0:1:0": "D1S2",
+          "Power Supply.Slot.1": "04.07.15",
+          "PERC H710P Mini": "21.0.2-0001",
+          "PowerCap": "689",
+          "Physical Disk 0:1:16": "D1S2",
+          "Physical Disk 0:1:10": "D1S2",
+          "Physical Disk 0:1:11": "D1S2",
+          "Lifecycle Controller 2": "1.0.8.42",
+          "BP12G+EXP 0:1": "1.07",
+          "Physical Disk 0:1:9": "D1S2",
+          "Physical Disk 0:1:17": "D1S2",
+          "Broadcom Gigabit Ethernet BCM5720": "7.2.20",
+          "Physical Disk 0:1:21": "D1S2",
+          "Physical Disk 0:1:13": "D1S2",
+          "Physical Disk 0:1:7": "D1S2",
+          "Physical Disk 0:1:19": "D1S2"
+        },
+        "hostName": "atsec-chi-00",
+        "id": "19",
+        "iloIpAddress": "172.16.2.6",
+        "iloIpGateway": "172.16.2.1",
+        "iloIpNetmask": "255.255.255.0",
+        "iloPassword": "********",
+        "iloUsername": "",
+        "interfaceMtu": "9000",
+        "interfaceName": "bond0",
+        "ip6Address": "2033:D0D0:3300::2:2/64",
+        "ip6Gateway": "2033:D0D0:3300::2:1",
+        "ipAddress": "10.10.2.2",
+        "ipGateway": "10.10.2.1",
+        "ipNetmask": "255.255.255.0",
+        "mgmtIpAddress": "",
+        "mgmtIpGateway": "",
+        "mgmtIpNetmask": "",
+        "physLocation": "plocation-chi-1",
+        "profile": "EDGE1_CDN1_421_SSL",
+        "rack": "RR 119.02",
+        "routerHostName": "rtr-chi.kabletown.net",
+        "routerPortName": "2",
+        "status": "ONLINE",
+        "tcpPort": "80",
+        "httpsPort": "443",
+        "type": "EDGE",
+        "xmppId": "atsec-chi-00-dummyxmpp",
+        "xmppPasswd": "X"
+
+      }
+    }
+
+|
+
+**POST /api/1.1/servercheck**
+
+  Post a server check result to the serverchecks table.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +----------------------------+----------+-------------+
+  |            Name            | Required | Description |
+  +============================+==========+=============+
+  | ``id``                     | yes      |             |
+  +----------------------------+----------+-------------+
+  | ``host_name``              | yes      |             |
+  +----------------------------+----------+-------------+
+  | ``servercheck_short_name`` | yes      |             |
+  +----------------------------+----------+-------------+
+  | ``value``                  | yes      |             |
+  +----------------------------+----------+-------------+
+
+  **Request Example** ::
+
+    {
+     "id": "",
+     "host_name": "",
+     "servercheck_short_name": "",
+     "value": ""
+    }
+
+|
+
+  **Response Properties**
+
+  +-------------+--------+----------------------------------+
+  |  Parameter  |  Type  |           Description            |
+  +=============+========+==================================+
+  | ``alerts``  | array  | A collection of alert messages.  |
+  +-------------+--------+----------------------------------+
+  | ``>level``  | string | Success, info, warning or error. |
+  +-------------+--------+----------------------------------+
+  | ``>text``   | string | Alert message.                   |
+  +-------------+--------+----------------------------------+
+  | ``version`` | string |                                  |
+  +-------------+--------+----------------------------------+
+
+  **Response Example** ::
+
+
+    Response Example:
+
+    {
+      "alerts":
+        [
+          {
+            "level": "success",
+            "text": "Server Check was successfully updated."
+          }
+        ],
+    }
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/static_dns.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/static_dns.txt
new file mode 100644
index 0000000..c9d3a3d
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/static_dns.txt
@@ -0,0 +1,63 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-dns:
+
+Static DNS Entries
+==================
+
+.. _to-api-v11-static-dns-route:
+
+/api/1.1/staticdnsentries
++++++++++++++++++++++++++
+
+**GET /api/1.1/staticdnsentries.json**
+
+    Authentication Required: Yes
+
+    Role(s) Required: None
+
+    **Response Properties**
+
+    +---------------------+-----------+------------------------------------------------------------+
+    | Parameter           |  Type     |                             Description                    |
+    +=====================+===========+============================================================+
+    | ``deliveryservice`` | string    |                                                            |
+    +---------------------+-----------+------------------------------------------------------------+
+    | ``ttl``             | string    |                                                            |
+    +---------------------+-----------+------------------------------------------------------------+
+    | ``type``            | string    |                                                            |
+    +---------------------+-----------+------------------------------------------------------------+
+    | ``address``         | string    |                                                            |
+    +---------------------+-----------+------------------------------------------------------------+
+    | ``cachegroup``      | string    |                                                            |
+    +---------------------+-----------+------------------------------------------------------------+
+    | ``host``            | string    |                                                            |
+    +---------------------+-----------+------------------------------------------------------------+
+
+    **Response Example** ::
+
+       {
+        "response": [
+          {
+            "deliveryservice": "foo-ds",
+            "ttl": "30",
+            "type": "CNAME_RECORD",
+            "address": "bar.foo.baz.tv.",
+            "cachegroup": "us-co-denver",
+            "host": "mm"
+          }
+        ]
+      }
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/status.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/status.txt
new file mode 100644
index 0000000..6a8c92a
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/status.txt
@@ -0,0 +1,127 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-status:
+
+Status
+======
+
+.. _to-api-v11-statuses-route:
+
+/api/1.1/statuses
++++++++++++++++++
+
+**GET /api/1.1/statuses**
+
+  Retrieves a list of the server status codes available.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +-----------------+--------+--------------------------------------------------------------------------------+
+  |    Parameter    |  Type  |                                  Description                                   |
+  +=================+========+================================================================================+
+  | ``id``          | string | The id with which Traffic Ops stores this status, and references it internally |
+  +-----------------+--------+--------------------------------------------------------------------------------+
+  | ``name``        | string | The string equivalent of the status                                            |
+  +-----------------+--------+--------------------------------------------------------------------------------+
+  | ``description`` | string | A short description of the status                                              |
+  +-----------------+--------+--------------------------------------------------------------------------------+
+  | ``lastUpdated`` | string | The Time / Date this server entry was last updated                             |
+  +-----------------+--------+--------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+       {
+        "response": [
+          {
+            "id": "4",
+            "name": "ADMIN_DOWN",
+            "description": "Temporary down. Edge: XMPP client will send status OFFLINE to CCR, otherwise similar to REPORTED. Mid: Server will not be included in parent.config files for its edge caches",
+            "lastUpdated": "2013-02-13 16:34:29"
+          },
+          {
+            "id": "5",
+            "name": "CCR_IGNORE",
+            "description": "Edge: 12M will not include caches in this state in CCR config files. Mid: N\/A for now",
+            "lastUpdated": "2013-02-13 16:34:29"
+          },
+          {
+            "id": "1",
+            "name": "OFFLINE",
+            "description": "Edge: Puts server in CCR config file in this state, but CCR will never route traffic to it. Mid: Server will not be included in parent.config files for its edge caches",
+            "lastUpdated": "2013-02-13 16:34:29"
+          },
+          {
+            "id": "2",
+            "name": "ONLINE",
+            "description": "Edge: Puts server in CCR config file in this state, and CCR will always route traffic to it. Mid: Server will be included in parent.config files for its edges",
+            "lastUpdated": "2013-02-13 16:34:29"
+          },
+          {
+            "id": "3",
+            "name": "REPORTED",
+            "description": "Edge: Puts server in CCR config file in this state, and CCR will adhere to the health protocol. Mid: N\/A for now",
+            "lastUpdated": "2013-02-13 16:34:29"
+          }
+        ]
+      }
+
+**GET /api/1.1/statuses/:id**
+
+  Retrieves a server status by ID.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +-----------+----------+---------------------------------------------+
+  |   Name    | Required |                Description                  |
+  +===========+==========+=============================================+
+  |   ``id``  |   yes    | Status id.                                  |
+  +-----------+----------+---------------------------------------------+
+
+  **Response Properties**
+
+  +-----------------+--------+--------------------------------------------------------------------------------+
+  |    Parameter    |  Type  |                                  Description                                   |
+  +=================+========+================================================================================+
+  | ``id``          | string | The id with which Traffic Ops stores this status, and references it internally |
+  +-----------------+--------+--------------------------------------------------------------------------------+
+  | ``name``        | string | The string equivalent of the status                                            |
+  +-----------------+--------+--------------------------------------------------------------------------------+
+  | ``description`` | string | A short description of the status                                              |
+  +-----------------+--------+--------------------------------------------------------------------------------+
+  | ``lastUpdated`` | string | The Time / Date this server entry was last updated                             |
+  +-----------------+--------+--------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+       {
+        "response": [
+          {
+            "id": "4",
+            "name": "ADMIN_DOWN",
+            "description": "Temporary down. Edge: XMPP client will send status OFFLINE to CCR, otherwise similar to REPORTED. Mid: Server will not be included in parent.config files for its edge caches",
+            "lastUpdated": "2013-02-13 16:34:29"
+          }
+        ]
+      }
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/system.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/system.txt
new file mode 100644
index 0000000..c4e53df
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/system.txt
@@ -0,0 +1,79 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-sys:
+
+System
+======
+
+.. _to-api-v11-sys-route:
+
+/api/1.1/system
++++++++++++++++
+
+**GET /api/1.1/system/info.json**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Response Properties**
+
+  +----------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  |            Key             |  Type  |                                                             Description                                                              |
+  +============================+========+======================================================================================================================================+
+  | ``parameters``             | hash   | This is a hash with the parameter names that describe the Traffic Ops installation as keys.                                          |
+  |                            |        | These are all the parameters in the ``GLOBAL`` profile.                                                                              |
+  +----------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>tm.toolname``           | string | The name of the Traffic Ops tool. Usually "Traffic Ops". Used in the About screen and in the comments headers of the files generated |
+  |                            |        | (``# DO NOT EDIT - Generated for atsec-lax-04 by Traffic Ops (https://traffops.kabletown.net/) on Fri Mar  6 05:15:15 UTC 2015``).   |
+  +----------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>tm.instance_name``      | string | The name of the Traffic Ops instance. Can be used when multiple instances are active. Visible in the About page.                     |
+  +----------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>traffic_rtr_fwd_proxy`` | string | When collecting stats from Traffic Router, 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 Router stats system and it is recommended to                         |
+  |                            |        | set this parameter on a production system.                                                                                           |
+  +----------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>tm.url``                | string | The URL for this Traffic Ops instance. Used in the About screen and in the comments headers of the files generated                   |
+  |                            |        | (``# DO NOT EDIT - Generated for atsec-lax-04 by Traffic Ops (https://traffops.kabletown.net/) on Fri Mar  6 05:15:15 UTC 2015``).   |
+  +----------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>traffic_mon_fwd_proxy`` | string | 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.                                                                                           |
+  +----------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>tm.logourl``            | string | This is the URL of the logo for Traffic Ops and can be relative if the logo is under traffic_ops/app/public.                         |
+  +----------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+  | ``>tm.infourl``            | string | This is the "for more information go here" URL, which is visible in the About page.                                                  |
+  +----------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
+
+  **Response Example** ::
+
+    {
+      "response": {
+        "parameters": {
+          "tm.toolname": "Traffic Ops",
+          "tm.infourl": "http:\/\/staging-03.cdnlab.kabletown.net\/tm\/info",
+          "traffic_mon_fwd_proxy": "http:\/\/proxy.kabletown.net:81",
+          "traffic_rtr_fwd_proxy": "http:\/\/proxy.kabletown.net:81",
+          "tm.logourl": "\/images\/tc_logo.png",
+          "tm.url": "https:\/\/tm.kabletown.net\/",
+          "tm.instance_name": "Kabletown CDN"
+        }
+      },
+    }
+
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/to_extension.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/to_extension.txt
new file mode 100644
index 0000000..5ed2654
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/to_extension.txt
@@ -0,0 +1,210 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-ext:
+
+TO Extensions
+=============
+
+.. _to-api-v11-ext-route:
+
+/api/1.1/to_extensions
+++++++++++++++++++++++
+
+**GET /api/1.1/to_extensions.json**
+
+Retrieves the list of extensions.
+
+Authentication Required: Yes
+
+Role(s) Required: None
+
+**Response Properties**
+
++--------------------------+--------+--------------------------------------------+
+| Parameter                | Type   | Description                                |
++==========================+========+============================================+
+|``script_file``           | string |                                            |
++--------------------------+--------+--------------------------------------------+
+|``version``               | string |                                            |
++--------------------------+--------+--------------------------------------------+
+|``name``                  | string |                                            |
++--------------------------+--------+--------------------------------------------+
+|``description``           | string |                                            |
++--------------------------+--------+--------------------------------------------+
+|``info_url``              | string |                                            |
++--------------------------+--------+--------------------------------------------+
+|``additional_config_json``| string |                                            |
++--------------------------+--------+--------------------------------------------+
+|``isactive``              | string |                                            |
++--------------------------+--------+--------------------------------------------+
+|``id``                    | string |                                            |
++--------------------------+--------+--------------------------------------------+
+|``type``                  | string |                                            |
++--------------------------+--------+--------------------------------------------+
+|``servercheck_short_name``| string |                                            |
++--------------------------+--------+--------------------------------------------+
+
+**Response Example** ::
+
+  {
+         "response": [
+                {
+                        script_file: "ping",
+                        version: "1.0.0",
+                        name: "ILO_PING",
+                        description: null,
+                        info_url: "http://foo.com/bar.html",
+                        additional_config_json: "{ "path": "/api/1.1/servers.json", "match": { "type": "EDGE"}, "select": "ilo_ip_address", "cron": "9 * * * *" }",
+                        isactive: "1",
+                        id: "1",
+                        type: "CHECK_EXTENSION_BOOL",
+                        servercheck_short_name: "ILO"
+                },
+                {
+                        script_file: "ping",
+                        version: "1.0.0",
+                        name: "10G_PING",
+                        description: null,
+                        info_url: "http://foo.com/bar.html",
+                        additional_config_json: "{ "path": "/api/1.1/servers.json", "match": { "type": "EDGE"}, "select": "ip_address", "cron": "18 * * * *" }",
+                        isactive: "1",
+                        id: "2",
+                        type: "CHECK_EXTENSION_BOOL",
+                        servercheck_short_name: "10G"
+                }
+         ],
+  }
+
+
+|
+
+**POST /api/1.1/to_extensions**
+
+  Creates a Traffic Ops extension.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Parameters**
+
+  +--------------------------+--------+--------------------------------------------+
+  | Parameter                | Type   | Description                                |
+  +==========================+========+============================================+
+  |``name``                  | string |                                            |
+  +--------------------------+--------+--------------------------------------------+
+  |``version``               | string |                                            |
+  +--------------------------+--------+--------------------------------------------+
+  |``info_url``              | string |                                            |
+  +--------------------------+--------+--------------------------------------------+
+  |``script_file``           | string |                                            |
+  +--------------------------+--------+--------------------------------------------+
+  |``isactive``              | string |                                            |
+  +--------------------------+--------+--------------------------------------------+
+  |``additional_config_json``| string |                                            |
+  +--------------------------+--------+--------------------------------------------+
+  |``description``           | string |                                            |
+  +--------------------------+--------+--------------------------------------------+
+  |``servercheck_short_name``| string |                                            |
+  +--------------------------+--------+--------------------------------------------+
+  |``type``                  | string |                                            |
+  +--------------------------+--------+--------------------------------------------+
+
+  **Request Example** ::
+
+
+    {
+          "name": "ILO_PING",
+          "version": "1.0.0",
+          "info_url": "http://foo.com/bar.html",
+          "script_file": "ping",
+          "isactive": "1",
+          "additional_config_json": "{ "path": "/api/1.1/servers.json", "match": { "type": "EDGE"}",
+          "description": null,
+          "servercheck_short_name": "ILO"
+          "type": "CHECK_EXTENSION_BOOL",
+    }
+
+|
+
+  **Response Properties**
+
+  +------------+--------+----------------------------------+
+  | Parameter  |  Type  |           Description            |
+  +============+========+==================================+
+  | ``alerts`` | array  | A collection of alert messages.  |
+  +------------+--------+----------------------------------+
+  | ``>level`` | string | Success, info, warning or error. |
+  +------------+--------+----------------------------------+
+  | ``>text``  | string | Alert message.                   |
+  +------------+--------+----------------------------------+
+
+  **Response Example** ::
+
+    {
+     "alerts": [
+        {
+           "level": "success",
+           "text": "Check Extension loaded."
+        }
+     ],
+    }
+
+
+|
+
+**POST /api/1.1/to_extensions/:id/delete**
+
+  Deletes a Traffic Ops extension.
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Route Parameters**
+
+  +--------+----------+-----------------+
+  |  Name  | Required |   Description   |
+  +========+==========+=================+
+  | ``id`` | yes      | TO extension id |
+  +--------+----------+-----------------+
+
+  **Response Properties**
+
+  +------------+--------+----------------------------------+
+  | Parameter  |  Type  |           Description            |
+  +============+========+==================================+
+  | ``alerts`` | array  | A collection of alert messages.  |
+  +------------+--------+----------------------------------+
+  | ``>level`` | string | Success, info, warning or error. |
+  +------------+--------+----------------------------------+
+  | ``>text``  | string | Alert message.                   |
+  +------------+--------+----------------------------------+
+
+  **Response Example** ::
+
+    {
+     "alerts": [
+        {
+           "level": "success",
+           "text": "Extension deleted."
+        }
+     ],
+    }
+
+
+|
+
diff --git a/docs/1.8.0/_sources/development/traffic_ops_api/v11/type.txt b/docs/1.8.0/_sources/development/traffic_ops_api/v11/type.txt
new file mode 100644
index 0000000..6c7806b
--- /dev/null
+++ b/docs/1.8.0/_sources/development/traffic_ops_api/v11/type.txt
@@ -0,0 +1,151 @@
+.. 
+.. 
+.. 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.
+.. 
+
+.. _to-api-v11-type:
+
+Types
+=====
+
+.. _to-api-v11-types-route:
+
+/api/1.1/types
+++++++++++++++
+
+**GET /api/1.1/types**
+
+  Authentication Required: Yes
+
+  Role(s) Required: None
+
+  **Request Query Parameters**
+
+  +----------------+----------+----------------------------------------------------+
+  |   Name         | Required |                Description                         |
+  +================+==========+====================================================+
+  | ``useInTable`` | no       | Filter types by the table in which they apply      |
+  +----------------+----------+----------------------------------------------------+
+
+  **Response Properties**
+
+  +----------------------+--------+------------------------------------------------+
+  | Parameter            | Type   | Description                                    |
+  +======================+========+================================================+
+  |``id``                | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``name``              | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``description``       | string |                                                |
+  +----------------------+--------+------------------------------------------------+
+  |``useInTable``        | string |                                                |
+  +----------------------