openstack/openstack-manuals
Code Issues Proposed changes

Further explained the the ping-all subcommand to neutron-debug

Browse Source 
A couple typos were fixed, and the subcommand was elaborated on.

Change-Id: I86f13e58afe6781a510213628a61397dc886e124
This commit is contained in:
Steven Deaton 2014-08-19 04:58:27 +00:00 committed by Anne Gentle
parent 7a2cf97a3a
commit ce63c9fb71
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/cli-reference/ch_cli_neutron-debug_commands.xml
View File

@ -77,7 +77,7 @@
<term><command>ping-all</command></term>
<listitem>
<para>
ping-all is all-in-one command to ping all fixed IP's in a specified network.
ping-all is an all-in-one command to ping all fixed IPs in a specified network.
</para>
</listitem>
</varlistentry>
@ -262,8 +262,14 @@ Remove a probe.
<section xml:id="neutron-debug_subcommand_ping-all">
<title>neutron-debug ping-all command</title>
<screen><computeroutput>usage: neutron-debug ping-all &lt;port-id> --timeout &lt;number</computeroutput></screen>
<para>All-in-one command to ping all fixed IP's
in a specified network.</para> <variablelist wordsize="10">
<para>All-in-one command to ping all fixed IPs
in a specified network. A probe creation is not needed
for this command. A new probe is created automatically. It will,
however, need to be deleted manually when it is no longer needed.
When there are multiple networks, the newly created probe will be
attached to a random network and thus the ping will take
place from within that random network.</para>
<variablelist wordsize="10">
<title>Positional arguments</title>
<varlistentry>
<term><command>&lt;port-id&gt;</command></term>