[networking-guide] master: Correction: JSON format configuration file (a113cab)
stephenw at fedoraproject.org
stephenw at fedoraproject.org
Fri Jul 25 06:46:54 UTC 2014
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit a113cab211b9cb37a4144631891c3d2655551d62
Author: Stephen Wadeley <swadeley at redhat.com>
Date: Mon Jul 21 22:51:57 2014 +0200
Correction: JSON format configuration file
>---------------------------------------------------------------
en-US/Configure_Network_Teaming.xml | 50 +++++++++++++++++++++++------------
1 files changed, 33 insertions(+), 17 deletions(-)
diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml
index 775eac7..2059436 100644
--- a/en-US/Configure_Network_Teaming.xml
+++ b/en-US/Configure_Network_Teaming.xml
@@ -669,7 +669,7 @@ To view the configuration of a port <interface>em1</interface>, that is part of
<section id="sec-Configure_the_broadcast_Runner">
<title>Configure the broadcast Runner</title>
<para>
- To configure the broadcast runner, using an editor as <systemitem class="username">root</systemitem>, add the following to the team <filename>ifcfg</filename> file:
+ To configure the broadcast runner, using an editor as <systemitem class="username">root</systemitem>, add the following to the team JSON format configuration file:
<screen>
{
"device": "team0",
@@ -677,7 +677,10 @@ To view the configuration of a port <interface>em1</interface>, that is part of
"ports": {"em1": {}, "em2": {}}
}</screen>
</para>
- </section>
+<para>
+Please see the <filename>teamd.conf(5)</filename> man page for more information.
+</para>
+</section>
<section id="sec-Configure_the_random_Runner">
<title>Configure the random Runner</title>
@@ -685,7 +688,7 @@ To view the configuration of a port <interface>em1</interface>, that is part of
The random runner behaves similarly to the roundrobin runner, but it does not do percentage calculations and therefore uses less system resources.
</para>
<para>
- To configure the random runner, using an editor as <systemitem class="username">root</systemitem>, add the following to the team <filename>ifcfg</filename> file:
+ To configure the random runner, using an editor as <systemitem class="username">root</systemitem>, add the following to the team JSON format configuration file:
<screen>
{
"device": "team0",
@@ -693,12 +696,15 @@ To view the configuration of a port <interface>em1</interface>, that is part of
"ports": {"em1": {}, "em2": {}}
}</screen>
</para>
- </section>
+<para>
+Please see the <filename>teamd.conf(5)</filename> man page for more information.
+</para>
+</section>
<section id="sec-Configure_the_roundrobin_Runner">
<title>Configure the roundrobin Runner</title>
<para>
- To configure the roundrobin runner, using an editor as <systemitem class="username">root</systemitem>, add the following to the team <filename>ifcfg</filename> file:
+ To configure the roundrobin runner, using an editor as <systemitem class="username">root</systemitem>, add the following to the team JSON format configuration file:
<screen>
{
"device": "team0",
@@ -707,12 +713,14 @@ To view the configuration of a port <interface>em1</interface>, that is part of
}</screen>
A very basic configuration for roundrobin.
</para>
-
+<para>
+Please see the <filename>teamd.conf(5)</filename> man page for more information.
+</para>
</section>
<section id="sec-Configure_the_activebackup_Runner">
<title>Configure the activebackup Runner</title>
<para>
- The active backup runner can use all of the link-watchers to determine the status of links in a team. Any one of the following examples can be added to the team <filename>ifcfg</filename> file:
+ The active backup runner can use all of the link-watchers to determine the status of links in a team. Any one of the following examples can be added to the team JSON format configuration file:
</para>
<para>
<screen>
@@ -762,7 +770,7 @@ To view the configuration of a port <interface>em1</interface>, that is part of
</para>
<para>
- To configure the activebackup runner using <application>ethtool</application> as the link watcher and applying a delay, using an editor as <systemitem class="username">root</systemitem>, add the following to the team <filename>ifcfg</filename> file:
+ To configure the activebackup runner using <application>ethtool</application> as the link watcher and applying a delay, using an editor as <systemitem class="username">root</systemitem>, add the following to the team JSON format configuration file:
<screen>
{
"device": "team0",
@@ -786,7 +794,9 @@ To view the configuration of a port <interface>em1</interface>, that is part of
}</screen>
This example configuration uses the active-backup runner with <application>ethtool</application> as the link watcher. Port <interface>em2</interface> has higher priority. But the sticky flag ensures that if <interface>em1</interface> becomes active, it stays active while the link remains up. Link changes are not propagated to the runner immediately, but delays are applied.
</para>
-
+<para>
+Please see the <filename>teamd.conf(5)</filename> man page for more information.
+</para>
</section>
<section id="sec-Configure_the_loadbalance_Runner">
<title>Configure the loadbalance Runner</title>
@@ -794,7 +804,7 @@ To view the configuration of a port <interface>em1</interface>, that is part of
This runner can be used for two types of load balancing, active and passive. In active mode, constant re-balancing of traffic is done by using statistics of recent traffic to share out traffic as evenly as possible. In static mode, streams of traffic are distributed randomly across the available links. This has a speed advantage due to lower processing overhead. In high volume traffic applications this is often preferred as traffic usually consists of multiple stream which will be distributed randomly between the available links, in his way load sharing is accomplished without intervention by <systemitem class="daemon">teamd</systemitem>.
</para>
<para>
- To configure the loadbalance runner for passive transmit (Tx) load balancing, using an editor as <systemitem class="username">root</systemitem>, add the following to the team <filename>ifcfg</filename> file:
+ To configure the loadbalance runner for passive transmit (Tx) load balancing, using an editor as <systemitem class="username">root</systemitem>, add the following to the team JSON format configuration file:
<screen>
{
"device": "team0",
@@ -808,7 +818,7 @@ To view the configuration of a port <interface>em1</interface>, that is part of
</para>
<para>
- To configure the loadbalance runner for active transmit (Tx) load balancing, using an editor as <systemitem class="username">root</systemitem>, add the following to the team <filename>ifcfg</filename> file:
+ To configure the loadbalance runner for active transmit (Tx) load balancing, using an editor as <systemitem class="username">root</systemitem>, add the following to the team JSON format configuration file:
<screen>
{
"device": "team0",
@@ -823,13 +833,15 @@ To view the configuration of a port <interface>em1</interface>, that is part of
}</screen>
Configuration for active transmit (Tx) load balancing using basic load balancer.
</para>
-
+<para>
+Please see the <filename>teamd.conf(5)</filename> man page for more information.
+</para>
</section>
<section id="sec-Configure_the_LACP_Runner">
<title>Configure the LACP (802.3ad) Runner</title>
<para>
- To configure the LACP runner using <application>ethtool</application> as a link watcher, using an editor as <systemitem class="username">root</systemitem>, add the following to the team <filename>ifcfg</filename> file:
+ To configure the LACP runner using <application>ethtool</application> as a link watcher, using an editor as <systemitem class="username">root</systemitem>, add the following to the team JSON format configuration file:
<screen>
{
"device": "team0",
@@ -844,18 +856,20 @@ To view the configuration of a port <interface>em1</interface>, that is part of
}</screen>
Configuration for connection to a <firstterm>link access control protocol</firstterm> (<acronym>LACP</acronym>) capable counterpart. The LACP runner should use <application>ethtool</application> to monitor the status of a link. It does not make sense to use any other link monitoring method besides the <application>ethtool</application> because, for example in the case of <application>arp_ping</application>, the link would never come up. The reason is that the link has to be established first and only after that can packets, ARP included, go through. Using <application>ethtool</application> prevents this because it monitors each link layer individually.</para>
<para>
- Active load balancing is possible with this runner in the same why as it is done for the loadbalance runner. To enable active transmit (Tx) load balancing, add the following section:
+ Active load balancing is possible with this runner in the same way as it is done for the loadbalance runner. To enable active transmit (Tx) load balancing, add the following section:
<screen>"tx_balancer": {
"name": "basic"
}</screen>
</para>
+<para>
+Please see the <filename>teamd.conf(5)</filename> man page for more information.
+</para>
</section>
-
<section id="sec-Configure_Monitoring_of_the_Link_State">
<title>Configure Monitoring of the Link State</title>
<para>
- The following methods of link state monitoring are available. To implement one of the methods, add the JSON format string to the team <filename>ifcfg</filename> file using an editor running with <systemitem class="username">root</systemitem> privileges.
+ The following methods of link state monitoring are available. To implement one of the methods, add the JSON format string to the team JSON format configuration file using an editor running with <systemitem class="username">root</systemitem> privileges.
</para>
<section id="sec-Configure_Ethtool_for_Link-state_Monitoring">
<title>Configure Ethtool for link-state Monitoring</title>
@@ -967,7 +981,9 @@ To view the configuration of a port <interface>em1</interface>, that is part of
}</screen>
Host name to be converted to an <systemitem class="protocol">IPv6</systemitem> address which will be used as the target address for the NS/NA packets. An <systemitem class="protocol">IPv6</systemitem> address can be used in place of a host name.
</para>
-
+<para>
+Please see the <filename>teamd.conf(5)</filename> man page for more information.
+</para>
</section>
</section>
More information about the docs-commits
mailing list