svn commit: r1145528 - in /trafficserver/site/branches/ats-cms/content/docs/trunk: STATUS admin/cluster-howto/index.en.mdtext

[ig...@apache.org]

Author: igalic
Date: Tue Jul 12 10:32:21 2011
New Revision: 1145528

URL: http://svn.apache.org/viewvc?rev=1145528&view=rev
Log:
Cluster Howto chapter reviewed, fixed typoes and some formating

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS?rev=1145528&r1=1145527&r2=1145528&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS Tue Jul 12 10:32:21 2011
@@ -64,7 +64,7 @@ hierachical-caching - done (commented ou
 configuring-cache - done
 monitoring-traffic
 configuring-traffic-server
-cluster-howto
+cluster-howto - done
 security-options
 working-log-files
 traffic-line-commands - This needs work!

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext?rev=1145528&r1=1145527&r2=1145528&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext Tue Jul 12 10:32:21 2011
@@ -17,7 +17,7 @@ Notice:    Licensed to the Apache Softwa
            under the License.
 
 
-## Traffic Server Cluster
+# Traffic Server Cluster
 
 Traffic Server scales from a single node to multiple nodes that form a
 cluster allowing you to improve system performance and reliability. This
@@ -25,7 +25,7 @@ chapter discusses the following topics:
 
 [TOC](#toc)
 
-### Understanding Traffic Server Clusters ### {#UnderstandingTSClusters}
+## Understanding Traffic Server Clusters ## {#UnderstandingTSClusters}
 
 A Traffic Server cluster consists of multiple Traffic Server nodes. The
 nodes in a cluster share configuration information and can form a single
@@ -39,7 +39,7 @@ cluster. Traffic Server has two clusteri
 * Full-clustering mode; refer to Full Clustering
 
 
-#### Management-Only Clustering #### {#ManagementOnlyClustering}
+### Management-Only Clustering ### {#ManagementOnlyClustering}
 
 In management-only clustering mode, Traffic Server cluster nodes share
 configuration information. You can administer all the nodes at the same
@@ -50,7 +50,7 @@ nodes, and the `traffic_manager` process
 configuration changes to all the nodes.
 
 
-#### Full Clustering  #### {#FullClustering}
+### Full Clustering  ### {#FullClustering}
 
 In full-clustering mode, as well as sharing configuration information, a
 Traffic Server cluster distributes its cache across its nodes into a
@@ -73,7 +73,7 @@ Full clustering recommends a dedicated n
 communication to get better performance.
 
 
-### Enable Clustering Mode ### {#EnableClusteringMode}
+## Enable Clustering Mode ## {#EnableClusteringMode}
 
 Before you put a node into a Cluster, please make sure the following thing
 checked:
@@ -81,7 +81,7 @@ checked:
 * you are using the samy Operation System:
     + Using the same distrobution, ie: RHEL 5.5
     + Have same kernel, ie: 2.6.18-194.17.1.el5
-    + The same ARCH, ie: x86\_64
+    + The same ARCH, ie: `x86_64`
 * install with the same version of Traffic Server
 * the same hardware
 * on the same switch or same vlan.
@@ -92,29 +92,34 @@ individually. You may following these in
 
 1. setup the same cluster name, or proxy name, e.g. MyCluster:
 
+                ::::text
 		traffic_line -s proxy.config.proxy_name -v MyCluster
 
 2. enable cluster mode:
 
+                ::::text
 		traffic_line -s proxy.local.cluster.type -v 1
 		traffic_line -s proxy.config.cluster.ethernet_interface -v eth0
- eth0 should be replaced by your real interface, we recommends a 
+ `eth0` should be replaced by your real interface, we recommends a 
  dedicated interface here. Refer to [`proxy.local.cluster.type`](../configuration-files/records.config#proxy.local.cluster.type)
  for a full description.
 
 3. enable:
 
-	traffic_line -x
+        ::::text
+        traffic_line -x
 
-Traffic Server will join into the Cluster in about 10 seconds, you man run
+Traffic Server will join into the Cluster in about 10 seconds and you can run
 `traffic_line -r proxy.process.cluster.nodes` to check the hosts in cluster
-or checkout the cluster.config in config dir.
+or checkout the [`cluster.config`](../configuration-files/cluster.configcluster.config)
+in the configuration directory.
 
 After a successful join of the cluster, all changes of global configurations on any
 node, will take effect on **all** node now.
 
 
-### Deleting Nodes from a Cluster ### {#DeletingNodesFromCluster}
+## Deleting Nodes from a Cluster ## {#DeletingNodesFromCluster}
+
 To delete a node from the Traffic Server cluster, just roll back
 `proxy.config.cluster.type` to the default value 3 and reload.