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/4] Change format of sec status to JSON
Date: Thu, 4 Oct 2018 14:59:14 +0900 [thread overview]
Message-ID: <20181004055918.5922-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Spp_nfv or spp_vm returns its status as a YAML-like format for
simplicity and requires clients to parse the response. It is better the
format to parse if it is standardized format.
This update is to change the response to JSON format from spp_nfv and
spp_vm.
{
"status": "running",
"ports": [
{"src":"phy:0","dst": "ring:0"},
{"src":"ring:0","dst": "null"}
]
}
SPP controller is also updated to parse the new format.
In shared/common.c and shared/common.h, function retrieving the status
is changed from print_active_port() to get_sec_status_json() to return
not only ports info but also whole of info including running status.
Yasufumi Ogawa (4):
shared: change sec status to JSON format
spp_nfv: update retrieving status
spp_vm: update retrieving status
controller: update for parsing JSON status
src/controller/shell.py | 50 ++++++++++-------------------
src/nfv/nfv.c | 10 +++---
src/shared/common.c | 84 +++++++++++++++++++++++++++++--------------------
src/shared/common.h | 2 +-
src/vm/main.c | 10 +++---
5 files changed, 77 insertions(+), 79 deletions(-)
--
2.7.4
next reply other threads:[~2018-10-04 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 5:59 ogawa.yasufumi [this message]
2018-10-04 5:59 ` [spp] [PATCH 1/4] shared: change sec status to JSON format ogawa.yasufumi
2018-10-04 5:59 ` [spp] [PATCH 2/4] spp_nfv: update retrieving status ogawa.yasufumi
2018-10-04 5:59 ` [spp] [PATCH 3/4] spp_vm: " ogawa.yasufumi
2018-10-04 5:59 ` [spp] [PATCH 4/4] controller: update for parsing JSON 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=20181004055918.5922-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).