From: Yasufumi Ogawa <yasufum.o@gmail.com>
To: x-fn-spp@sl.ntt-tx.co.jp, ferruh.yigit@intel.com
Cc: spp@dpdk.org
Subject: Re: [spp] [PATCH v2] recipes: add rcps for multiple nodes usecase
Date: Tue, 10 Sep 2019 14:45:49 +0900 [thread overview]
Message-ID: <78c1b9f1-9479-4eb3-5090-0f656a65817a@gmail.com> (raw)
In-Reply-To: <201909100137.x8A1bLWw004236@imss03.silk.ntt-tx.co.jp>
> From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
>
> This patch is to provide rcps for usecase of Multiple Nodes.
>
> Signed-off-by: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
> Signed-off-by: Naoki Takada <ntakada14@gmail.com>
Applied, thaks.
> ---
> recipes/usecases/multiple_nodes/1_add_server.rcps | 4 ++++
> recipes/usecases/multiple_nodes/2_switch_check.rcps | 2 ++
> 2 files changed, 6 insertions(+)
> create mode 100644 recipes/usecases/multiple_nodes/1_add_server.rcps
> create mode 100644 recipes/usecases/multiple_nodes/2_switch_check.rcps
>
> diff --git a/recipes/usecases/multiple_nodes/1_add_server.rcps b/recipes/usecases/multiple_nodes/1_add_server.rcps
> new file mode 100644
> index 0000000..fee7324
> --- /dev/null
> +++ b/recipes/usecases/multiple_nodes/1_add_server.rcps
> @@ -0,0 +1,4 @@
> +# Add server
> +server add 192.168.11.102
> +server add 192.168.11.103
> +server add 192.168.11.104
> diff --git a/recipes/usecases/multiple_nodes/2_switch_check.rcps b/recipes/usecases/multiple_nodes/2_switch_check.rcps
> new file mode 100644
> index 0000000..80480af
> --- /dev/null
> +++ b/recipes/usecases/multiple_nodes/2_switch_check.rcps
> @@ -0,0 +1,2 @@
> +# Switch to server 3
> +server 3
>
prev parent reply other threads:[~2019-09-10 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 2:14 [spp] [PATCH] " x-fn-spp
2019-09-10 1:37 ` [spp] [PATCH v2] " x-fn-spp
2019-09-10 5:45 ` Yasufumi Ogawa [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=78c1b9f1-9479-4eb3-5090-0f656a65817a@gmail.com \
--to=yasufum.o@gmail.com \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
--cc=x-fn-spp@sl.ntt-tx.co.jp \
/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).