From: Itsuro ODA <oda@valinux.co.jp>
To: spp@dpdk.org
Subject: [spp] [PATCH v2 0/9] spp-ctl: SPP controller with Web API
Date: Sun, 23 Sep 2018 11:22:34 +0900 [thread overview]
Message-ID: <20180923112233.2D71.277DD91C@valinux.co.jp> (raw)
From: Itsuro Oda <oda@valinux.co.jp>
spp-ctl is a SPP controller with a REST like web API.
spp-ctl maintains the connections from the SPP processes and at
the same time exposes the API for the user to request for the
SPP processes.
Background and motivation:
Current CLI (spp.py/spp_vf.py) can be used by intaractive only.
Therefore, spp-agent, a component of networking-spp which make
SPP available on OpenStack environment, implements SPP controller
in itself. (see. https://github.com/openstack/networking-spp )
Either CLI or spp-agent, there is a problem that other people can
not request to SPP processes while using. spp-ctl is invented to
solve this problem.
Both CLI and spp-agent can be used spp-ctl to request SPP
processes instead of owning contoroller itself. In that case,
multiple people can request to SPP processes at the same time.
Note that spp-agent has a plan to change to use spp-ctl.
It is also available not using CLI but requesting spp-ctl
directly.
Itsuro Oda (9):
docs: overview
docs: api reference
docs: index
docs: top index
add requirement.txt
spp-ctl: executable
spp-ctl: controller
spp-ctl: web api handler
spp-ctl: spp command interface
docs/guides/index.rst | 1 +
docs/guides/spp-ctl/api-reference.rst | 790 ++++++++++++++++++++++++++
docs/guides/spp-ctl/index.rst | 39 ++
docs/guides/spp-ctl/overview.rst | 102 ++++
requirements.txt | 3 +
src/spp-ctl/spp-ctl | 11 +
src/spp-ctl/spp_ctl.py | 158 ++++++
src/spp-ctl/spp_proc.py | 184 ++++++
src/spp-ctl/spp_webapi.py | 440 ++++++++++++++
9 files changed, 1728 insertions(+)
create mode 100644 docs/guides/spp-ctl/api-reference.rst
create mode 100644 docs/guides/spp-ctl/index.rst
create mode 100644 docs/guides/spp-ctl/overview.rst
create mode 100644 requirements.txt
create mode 100755 src/spp-ctl/spp-ctl
create mode 100644 src/spp-ctl/spp_ctl.py
create mode 100644 src/spp-ctl/spp_proc.py
create mode 100644 src/spp-ctl/spp_webapi.py
--
Itsuro ODA <oda@valinux.co.jp>
next reply other threads:[~2018-09-23 2:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 2:22 Itsuro ODA [this message]
2018-09-23 2:25 ` [spp] [PATCH v2 1/9] docs: overview Itsuro ODA
2018-10-02 3:29 ` Yasufumi Ogawa
2018-09-23 2:28 ` [spp] [PATCH v2 2/9] docs: api reference Itsuro ODA
2018-10-02 3:42 ` Yasufumi Ogawa
2018-10-02 4:10 ` Yasufumi Ogawa
2018-09-23 2:30 ` [spp] [PATCH v2 3/9] docs: index Itsuro ODA
2018-09-23 2:32 ` [spp] [PATCH v2 4/9] docs: top index Itsuro ODA
2018-09-23 2:33 ` [spp] PATCH v2 5/9] add requirements.txt Itsuro ODA
2018-09-23 2:35 ` [spp] [PATCH v2 6/9] spp-ctl: executable Itsuro ODA
2018-10-02 5:47 ` Yasufumi Ogawa
2018-09-23 2:36 ` [spp] [PATCH v2 7/9] spp-ctl: SPP controller with Web API Itsuro ODA
2018-09-23 2:44 ` Itsuro ODA
2018-09-25 2:01 ` Yasufumi Ogawa
2018-09-23 2:38 ` [spp] [PATCH v2 8/9] spp-ctl: web api handler Itsuro ODA
2018-10-02 4:03 ` Yasufumi Ogawa
2018-09-23 2:39 ` [spp] [PATCH v2 9/9] spp-ctl: spp command interface Itsuro ODA
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=20180923112233.2D71.277DD91C@valinux.co.jp \
--to=oda@valinux.co.jp \
--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).