You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficcontrol.apache.org by ne...@apache.org on 2017/01/05 19:40:25 UTC
[5/6] incubator-trafficcontrol git commit: Minor structural fix in
traffic-router developers guide
Minor structural fix in traffic-router developers guide
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/commit/dd067810
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/tree/dd067810
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/diff/dd067810
Branch: refs/heads/master
Commit: dd06781043395a35e3b118508228bccbc5a0027b
Parents: c3e9bd1
Author: Nir B. Sopher <ni...@qwilt.com>
Authored: Tue Dec 27 15:21:10 2016 +0200
Committer: David Neuman <da...@gmail.com>
Committed: Thu Jan 5 12:40:03 2017 -0700
----------------------------------------------------------------------
docs/source/development/traffic_router.rst | 29 +++++++++++++------------
1 file changed, 15 insertions(+), 14 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/dd067810/docs/source/development/traffic_router.rst
----------------------------------------------------------------------
diff --git a/docs/source/development/traffic_router.rst b/docs/source/development/traffic_router.rst
index 09e6a1a..52ad553 100644
--- a/docs/source/development/traffic_router.rst
+++ b/docs/source/development/traffic_router.rst
@@ -87,19 +87,20 @@ To install the Traffic Router Developer environment:
1. Clone the traffic_control repository using Git.
2. Change directories into ``traffic_control/traffic_router``.
3. Set the environment variable TRAFFIC_MONITOR_HOSTS to be a semicolon delimited list of Traffic Monitors that can be accessed during integration tests
-4. core/src/test/resources no longer exists
-5. core/src/test/conf contains a properties file for accessing Traffic Ops
-6. Default configuration values now reside in core/src/main/webapp/WEB-INF/applicationContext.xml
-7. The above values may be overridden by creating and/or modifying the property files listed in core/src/main/resources/applicationProperties.xml
-8. Pre-existing properties files are still honored by Traffic Router
+4. Additional configuration is set using the below files:
+ * core/src/test/resources no longer exists
+ * core/src/test/conf/traffic_ops.properties file holds the credentials for accessing Traffic Ops.
+ * Default configuration values now reside in core/src/main/webapp/WEB-INF/applicationContext.xml
+ * The above values may be overridden by creating and/or modifying the property files listed in core/src/main/resources/applicationProperties.xml
+ * Pre-existing properties files are still honored by Traffic Router. For example traffic_monitor.properties:
-+-------------------------------------+------------------------------------------------------------------------------------------------------------------+
-| Parameter | Value |
-+=====================================+==================================================================================================================+
-| ``traffic_monitor.bootstrap.hosts`` | FQDN and port of the Traffic Monitor instance(s), separated by semicolons as necessary (do not include http://). |
-+-------------------------------------+------------------------------------------------------------------------------------------------------------------+
+ +-------------------------------------+------------------------------------------------------------------------------------------------------------------+
+ | Parameter | Value |
+ +=====================================+==================================================================================================================+
+ | ``traffic_monitor.bootstrap.hosts`` | FQDN and port of the Traffic Monitor instance(s), separated by semicolons as necessary (do not include http://). |
+ +-------------------------------------+------------------------------------------------------------------------------------------------------------------+
-4. Import the existing git repo into Eclipse:
+5. Import the existing git repo into Eclipse:
a. File -> Import -> Git -> Projects from Git; Next
b. Existing local repository; Next
@@ -109,9 +110,9 @@ To install the Traffic Router Developer environment:
f. Ensure ``traffic_router_api``, ``traffic_router_connector``, and ``traffic_router_core`` are checked; Finish (this step can take several minutes to complete)
g. Ensure ``traffic_router_api``, ``traffic_router_connector``, and ``traffic_router_core`` have been opened by Eclipse after importing
-5. From the terminal, run ``mvn clean verify`` from the ``traffic_router`` directory
+6. From the terminal, run ``mvn clean verify`` from the ``traffic_router`` directory
-6. Start the embedded Jetty instance for Core from within Eclipse
+7. Start the embedded Jetty instance for Core from within Eclipse
a. In the package explorer, expand ``traffic_router_core``
b. Expand ``src/test/java``
@@ -120,7 +121,7 @@ To install the Traffic Router Developer environment:
.. Note:: If an error is displayed in the Console, run ``mvn clean verify`` from the ``traffic_router`` directory
-7. Traffic Router Core should now be running; the HTTP routing interface is available on http://localhost:8081, while HTTPS is available on http://localhost:8443. The DNS server and routing interface is available on localhost:1053 via TCP and UDP.
+8. Traffic Router Core should now be running; the HTTP routing interface is available on http://localhost:8081, while HTTPS is available on http://localhost:8443. The DNS server and routing interface is available on localhost:1053 via TCP and UDP.
Test Cases
==========