New diagram and overview sections

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

Branch: refs/heads/master
Commit: 8b91374637469c40e0c3bcc59a7c097629625ac1
Parents: 84b87ab
Author: Ryan Durfey <ryandur...@users.noreply.github.com>
Authored: Wed Feb 8 18:21:55 2017 -0800
Committer: Jeremy Mitchell <mitchell...@gmail.com>
Committed: Fri Feb 17 08:07:41 2017 -0700

----------------------------------------------------------------------
 docs/source/overview/introduction.rst | 27 ++++++++++++++++++++++++---
 1 file changed, 24 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/8b913746/docs/source/overview/introduction.rst
----------------------------------------------------------------------
diff --git a/docs/source/overview/introduction.rst 
b/docs/source/overview/introduction.rst
index a983820..4f60141 100644
--- a/docs/source/overview/introduction.rst
+++ b/docs/source/overview/introduction.rst
@@ -15,14 +15,35 @@
 
 Introduction
 ============
-Traffic Control is a control plane for a CDN, which includes all of the 
components mentioned in the CDN Basics section, except for the Log File 
Analysis System. The caching software chosen for Traffic Control is `Apache 
Traffic Server <http://trafficserver.apache.org/>`_ (ATS). Although the current 
release only supports ATS as a cache, this may change with future releases. 
+Traffic Control is a CDN control plane, which includes all of the components 
mentioned in the CDN Basics section, except for the Log File Analysis System. 
The CDN caching software chosen for Traffic Control is `Apache Traffic Server 
<http://trafficserver.apache.org/>`_ (ATS). Although the current release only 
supports ATS as a cache, this may change with future releases. 
 
 Traffic Control was first developed at Comcast for internal use and released 
to Open Source in April of 2015. Traffic Control moved into the Apache 
Incubator in August of 2016.
 
-Traffic Control implements the blue boxes in the architecture diagram below. 
+Traffic Control implements the elements illustrated in green in the diagram  
below. 
 
 
-.. image:: traffic_control_overview_3.png
+.. image:: CDN-Traffic-Control.png
        :align: center
 
+
+**Traffic Ops**
+*`Traffic Ops 
<http://trafficcontrol.apache.org/docs/latest/overview/traffic_ops.html>` is 
used configure Traffic Servers and CDN Delivery Services. It also contains APIs 
used to access CDN data.
+
+**Traffic Router**
+*`Traffic Router 
<http://trafficcontrol.apache.org/docs/latest/overview/traffic_ops.html>` is 
used to route clients with the closest healthy cache by analyzing the state of 
the Traffic Servers and the the location of the Client.
+
+**Traffic Monitor**
+*`Traffic Monitor 
<http://trafficcontrol.apache.org/docs/latest/overview/traffic_monitor.html>` 
does health polling of the Traffic Servers on a very short interval to keep 
track of which servers should be kept in rotation.
+
+**Traffic Stats**
+*`Traffic Stats 
<http://trafficcontrol.apache.org/docs/latest/overview/traffic_stats.html>` 
collects real time traffic statistics aggregated from each of the Traffic 
Servers. This data is used by the Traffic Router to assess whether a Traffic 
Server is over taxed.
+
+
+**Traffic Portal**
+*`Traffic Portal 
<http://trafficcontrol.apache.org/docs/latest/overview/traffic_portal.html>` is 
a web application which leverages the Traffic Ops APIs to present CDN data 
through a web interface.
+
+**Traffic Logs**
+*Traffic Logs is currently under construction with the intent of being an 
aggregator for all Traffic Server request and response logs.  Logs are parsed 
by service and indexed for search.
+
+
 In the next sections each of these components will be explained further.

Reply via email to