From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org
Cc: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH 0/3] Introduce recipes as config
Date: Wed, 13 Jun 2018 11:44:56 +0900 [thread overview]
Message-ID: <20180613024459.31031-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Hi,
SPP's network configuration is able to be restored with 'playback'
command. This command is useful especially if the network has a lot
of ports and paths.
Config files are included in 'docs/samples/command' and named as
'*.config'. However, it is not a good habit because path is not
appropriate in meaning and the extension '*config' is ambiguous.
I would like to introduce 'recipe' which is used for describing network
configuration instead of 'config' file. As '*.config', the contents of
recipe file is a set of SPP commands. So, you do not need to change
existing config files, but simply rename it for usign as recipe.
Recipe files will be included in 'recipes' directory under the project
root. Recipe will be named as '*.rcps' it stands for recipe scripts
for SPP. Although you can use any of extension such as '*.txt' or
'*.conf' as long as it is included in 'recipes' directory because it is
just a text file actually, but it is better to use 'rcps' to be
explicit.
Recipe is loaded with 'playback' command to restore the network
configuration. This is an example.
spp > playback recipes/spp/usecase/dual_bidir.rcps
Yasufumi Ogawa (3):
recipes: add recipes directory
recipes: update SPP usecases
recipes: update SPP_VF usecases
docs/samples/command/spp/1nfv_1vm_bi.config | 28 -----------------
docs/samples/command/spp/1nfv_1vm_uni.config | 21 -------------
docs/samples/command/spp/1nfv_bi.config | 10 -------
.../samples/command/spp/2nfv_1ring_uni.config | 18 -----------
docs/samples/command/spp/2nfv_1vm_bi.config | 30 -------------------
docs/samples/command/spp/2nfv_bi.config | 12 --------
.../spp_vf/usecase1/2-add_ports_path1.config | 25 ----------------
.../spp_vf/usecase1/5-add_ports_path2.config | 25 ----------------
recipes/spp/usecases/dual_bidir.rcps | 5 ++++
recipes/spp/usecases/dual_loopback.rcps | 4 +++
recipes/spp/usecases/ring_dual_bidir.rcps | 14 +++++++++
recipes/spp/usecases/ring_dual_unidir.rcps | 9 ++++++
recipes/spp/usecases/single_bidir.rcps | 4 +++
recipes/spp/usecases/vhost_unidir.rcps | 6 ++++
.../usecase1/setup/1-start_components.rcps | 0
.../usecase1/setup/2-add_ports_path1.rcps | 20 +++++++++++++
.../usecase1/setup/3-reg_mac_path1.rcps | 0
.../usecase1/setup/4-start_components.rcps | 0
.../usecase1/setup/5-add_ports_path2.rcps | 20 +++++++++++++
.../usecase1/setup/6-reg_mac_path2.rcps | 0
recipes/spp_vf/usecase1/setup/7-flush.rcps | 1 +
.../usecase1/shutdown/1-del_mac_path1.rcps | 3 ++
.../usecase1/shutdown/2-del_ports_path1.rcps | 20 +++++++++++++
.../usecase1/shutdown/3-stop_components.rcps | 7 +++++
.../usecase1/shutdown/4-del_mac_path2.rcps | 3 ++
.../usecase1/shutdown/5-del_ports_path2.rcps | 20 +++++++++++++
.../usecase1/shutdown/6-stop_components.rcps | 7 +++++
recipes/spp_vf/usecase1/shutdown/7-flush.rcps | 1 +
recipes/sppc/samples/l2fwd.rcps | 22 ++++++++++++++
recipes/sppc/samples/load_balancer.rcps | 30 +++++++++++++++++++
30 files changed, 196 insertions(+), 169 deletions(-)
delete mode 100644 docs/samples/command/spp/1nfv_1vm_bi.config
delete mode 100644 docs/samples/command/spp/1nfv_1vm_uni.config
delete mode 100644 docs/samples/command/spp/1nfv_bi.config
delete mode 100644 docs/samples/command/spp/2nfv_1ring_uni.config
delete mode 100644 docs/samples/command/spp/2nfv_1vm_bi.config
delete mode 100644 docs/samples/command/spp/2nfv_bi.config
delete mode 100644 docs/samples/command/spp_vf/usecase1/2-add_ports_path1.config
delete mode 100644 docs/samples/command/spp_vf/usecase1/5-add_ports_path2.config
create mode 100644 recipes/spp/usecases/dual_bidir.rcps
create mode 100644 recipes/spp/usecases/dual_loopback.rcps
create mode 100644 recipes/spp/usecases/ring_dual_bidir.rcps
create mode 100644 recipes/spp/usecases/ring_dual_unidir.rcps
create mode 100644 recipes/spp/usecases/single_bidir.rcps
create mode 100644 recipes/spp/usecases/vhost_unidir.rcps
rename docs/samples/command/spp_vf/usecase1/1-start_components_path1.config => recipes/spp_vf/usecase1/setup/1-start_components.rcps (100%)
create mode 100644 recipes/spp_vf/usecase1/setup/2-add_ports_path1.rcps
rename docs/samples/command/spp_vf/usecase1/3-reg_mac_path1.config => recipes/spp_vf/usecase1/setup/3-reg_mac_path1.rcps (100%)
rename docs/samples/command/spp_vf/usecase1/4-start_components_path2.config => recipes/spp_vf/usecase1/setup/4-start_components.rcps (100%)
create mode 100644 recipes/spp_vf/usecase1/setup/5-add_ports_path2.rcps
rename docs/samples/command/spp_vf/usecase1/6-reg_mac_path2.config => recipes/spp_vf/usecase1/setup/6-reg_mac_path2.rcps (100%)
create mode 100644 recipes/spp_vf/usecase1/setup/7-flush.rcps
create mode 100644 recipes/spp_vf/usecase1/shutdown/1-del_mac_path1.rcps
create mode 100644 recipes/spp_vf/usecase1/shutdown/2-del_ports_path1.rcps
create mode 100644 recipes/spp_vf/usecase1/shutdown/3-stop_components.rcps
create mode 100644 recipes/spp_vf/usecase1/shutdown/4-del_mac_path2.rcps
create mode 100644 recipes/spp_vf/usecase1/shutdown/5-del_ports_path2.rcps
create mode 100644 recipes/spp_vf/usecase1/shutdown/6-stop_components.rcps
create mode 100644 recipes/spp_vf/usecase1/shutdown/7-flush.rcps
create mode 100644 recipes/sppc/samples/l2fwd.rcps
create mode 100644 recipes/sppc/samples/load_balancer.rcps
--
2.17.1
next reply other threads:[~2018-06-13 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 2:44 ogawa.yasufumi [this message]
2018-06-13 2:44 ` [spp] [PATCH 1/3] recipes: add recipes directory ogawa.yasufumi
2018-06-13 2:44 ` [spp] [PATCH 2/3] recipes: update SPP usecases ogawa.yasufumi
2018-06-13 2:44 ` [spp] [PATCH 3/3] recipes: update SPP_VF usecases ogawa.yasufumi
2018-08-15 15:19 ` [spp] [PATCH 0/3] Introduce recipes as config Ferruh Yigit
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=20180613024459.31031-1-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).