From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/5] Add exit command support for spp_nfv and spp_vm
Date: Thu, 25 Oct 2018 14:19:38 +0900 [thread overview]
Message-ID: <20181025051943.17129-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Hi,
SPP controller does not support `exit` command after it is changed to
request via `spp-ctl` because REST APIs for `exit` command is not
implemented. This series of patches is to add `exit' command for spp_nfv
and spp_vm. Spp_primary and spp_vf is also needed to add this support,
and updated in the next patches.
Thanks,
Yasufumi
Yasufumi Ogawa (5):
spp_nfv: chage to return msg of exit command
spp-ctl: add exit cmd support for spp_nfv
spp_vm: chage to return msg of exit command
controller: update sec exit cmd to call REST API
docs: add DELETE method for exiting spp_nfv
docs/guides/spp-ctl/api-reference.rst | 43 +++++++++++++++++++++++++++++++++++
src/controller/commands/sec.py | 10 +++++++-
src/nfv/nfv.c | 10 ++++----
src/spp-ctl/spp_ctl.py | 9 ++++++++
src/spp-ctl/spp_proc.py | 4 ++++
src/spp-ctl/spp_webapi.py | 5 ++++
src/vm/main.c | 12 ++++++----
7 files changed, 83 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2018-10-25 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 5:19 ogawa.yasufumi [this message]
2018-10-25 5:19 ` [spp] [PATCH 1/5] spp_nfv: chage to return msg of exit command ogawa.yasufumi
2018-10-25 5:19 ` [spp] [PATCH 2/5] spp-ctl: add exit cmd support for spp_nfv ogawa.yasufumi
2018-10-25 5:19 ` [spp] [PATCH 3/5] spp_vm: chage to return msg of exit command ogawa.yasufumi
2018-10-25 5:19 ` [spp] [PATCH 4/5] controller: update sec exit cmd to call REST API ogawa.yasufumi
2018-10-25 5:19 ` [spp] [PATCH 5/5] docs: add DELETE method for exiting spp_nfv ogawa.yasufumi
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=20181025051943.17129-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).