From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 4/4] docs: add usage of server add command in usecase
Date: Thu, 31 Jan 2019 20:03:09 +0900 [thread overview]
Message-ID: <1548932589-21099-5-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1548932589-21099-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
In `Multiple Nodes` section in usecase, add an example of adding nodes
by using `server add` command as usage.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/use_cases/multi_nodes.rst | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/docs/guides/use_cases/multi_nodes.rst b/docs/guides/use_cases/multi_nodes.rst
index 6be567e..b44d0bd 100644
--- a/docs/guides/use_cases/multi_nodes.rst
+++ b/docs/guides/use_cases/multi_nodes.rst
@@ -49,8 +49,24 @@ for each of hosts. SPP CLI is able to be launched on any of nodes.
-b 192.168.11.103 \
-b 192.168.11.104 \
-If you succeeded to launch all of processes before, you can find them
-by running ``sever list`` command.
+Or you can add nodes after launching SPP CLI. Here is an example of
+launching it with first node, and adding the rest of nodes after.
+
+.. code-block:: console
+
+ # Launch SPP CLI
+ $ python src/spp.py -b 192.168.11.101
+ Welcome to the spp. Type help or ? to list commands.
+
+ spp > server add 192.168.11.102
+ Registered spp-ctl "192.168.11.102:7777".
+ spp > server add 192.168.11.103
+ Registered spp-ctl "192.168.11.103:7777".
+ spp > server add 192.168.11.104
+ Registered spp-ctl "192.168.11.104:7777".
+
+If you have succeeded to launch all of ``spp-ctl`` processes before,
+you can find them by running ``sever list`` command.
.. code-block:: console
--
2.7.4
prev parent reply other threads:[~2019-01-31 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 11:03 [spp] [PATCH 0/4] Update REST API reference and usecases ogawa.yasufumi
2019-01-31 11:03 ` [spp] [PATCH 1/4] docs: add lcores in pri status in REST API ogawa.yasufumi
2019-01-31 11:03 ` [spp] [PATCH 2/4] docs: add launch of primary to REST API reference ogawa.yasufumi
2019-01-31 11:03 ` [spp] [PATCH 3/4] docs: refactor spp_nfv " ogawa.yasufumi
2019-01-31 11:03 ` ogawa.yasufumi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1548932589-21099-5-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).