From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH v2 0/4] Update response of status of spp_nfv and spp_vm
Date: Thu, 11 Oct 2018 19:33:43 +0900 [thread overview]
Message-ID: <20181011103347.48630-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20181009105047.42568-1-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Hi,
I updated calling port_add and port_del methods to be simple. Here is
the change of definition of port_add(), and port_del() is also the same.
- def port_add(self, if_type, if_num):
- return "add {if_type} {if_num}".format(**locals())
+ def port_add(self, port):
+ return "add {port}".format(**locals())
Thanks,
Yasufumi
>Spp-ctl provides a set of REST APIs for managing all of SPP processes in
>a unified way. If the REST API is called, spp-ctl sets up a request for
>SPP process by parsing user's request and replies to the user.
>
>This update is to update spp_nfv and spp_vm to return responses as JSON
>as similar to spp_vf for better maintaince of spp-ctl.
Yasufumi Ogawa (4):
shared: update status format of spp_nfv
controller: update parsing status message
spp-ctl: update syntax of add and del command
spp-ctl: update parsing status
src/controller/shell.py | 21 +++---
src/nfv/nfv.c | 10 +--
src/shared/common.c | 179 ++++++++++++++++++++++++++++++++++++----------
src/shared/common.h | 14 +++-
src/spp-ctl/spp_proc.py | 8 +--
src/spp-ctl/spp_webapi.py | 39 +++-------
src/vm/init.c | 2 +-
src/vm/main.c | 8 +--
8 files changed, 189 insertions(+), 92 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2018-10-11 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 10:50 [spp] [PATCH " ogawa.yasufumi
2018-10-09 10:50 ` [spp] [PATCH 1/4] shared: update status format of spp_nfv ogawa.yasufumi
2018-10-09 10:50 ` [spp] [PATCH 2/4] controller: update parsing status message ogawa.yasufumi
2018-10-09 10:50 ` [spp] [PATCH 3/4] spp-ctl: update syntax of add and del command ogawa.yasufumi
2018-10-09 21:56 ` Itsuro ODA
2018-10-10 4:41 ` Yasufumi Ogawa
2018-10-09 10:50 ` [spp] [PATCH 4/4] spp-ctl: update parsing status ogawa.yasufumi
2018-10-11 10:33 ` ogawa.yasufumi [this message]
2018-10-11 10:33 ` [spp] [PATCH v2 1/4] shared: update status format of spp_nfv ogawa.yasufumi
2018-10-11 10:33 ` [spp] [PATCH v2 2/4] controller: update parsing status message ogawa.yasufumi
2018-10-11 10:33 ` [spp] [PATCH v2 3/4] spp-ctl: update syntax of add and del command ogawa.yasufumi
2018-10-11 10:33 ` [spp] [PATCH v2 4/4] spp-ctl: update parsing status 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=20181011103347.48630-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).