From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 02/11] docs: move overview of spp-ctl to SPP overview
Date: Wed, 9 Jan 2019 10:49:23 +0900 [thread overview]
Message-ID: <1546998573-26108-3-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1546998573-26108-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Move overview of spp-ctl to SPP's overvew section.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/overview/design.rst | 17 +++++++++++++++++
docs/guides/spp-ctl/overview.rst | 32 --------------------------------
2 files changed, 17 insertions(+), 32 deletions(-)
diff --git a/docs/guides/overview/design.rst b/docs/guides/overview/design.rst
index 486550d..9663a09 100644
--- a/docs/guides/overview/design.rst
+++ b/docs/guides/overview/design.rst
@@ -30,6 +30,23 @@ By using networking-spp and doing some of extra tunings for optimization, you
can deploy high-performance NFV services on OpenStack [2].
+SPP Controller
+--------------
+
+spp-ctl
+~~~~~~~
+
+``spp-ctl`` is designed for managing SPP from several controllers
+via REST-like APIs for users or other applications.
+
+There are several usecases where SPP is managed from other process without
+user inputs. For example, you need a intermediate process if you think of
+using SPP from a framework, such as OpenStack.
+`networking-spp
+<https://github.com/openstack/networking-spp>`_
+is a Neutron ML2 plugin for SPP and `spp-agent` works as a SPP controller.
+
+
Reference
---------
diff --git a/docs/guides/spp-ctl/overview.rst b/docs/guides/spp-ctl/overview.rst
index 4c7181c..6b88f3b 100644
--- a/docs/guides/spp-ctl/overview.rst
+++ b/docs/guides/spp-ctl/overview.rst
@@ -6,38 +6,6 @@
spp-ctl
=======
-Overview
---------
-
-``spp-ctl`` is an alternative SPP controller which provides a REST-like
-APIs.
-
-It maintains connections between SPP processes for managing them
-via the REST-like APIs for users or other processes.
-
-Background and Motivation
--------------------------
-
-``spp-ctl`` is designed for supporting to manage SPP from several
-controllers.
-
-There are some usecases where SPP is managed from other
-process without user inputs.
-For example, you need a intermediate process if you think of using SPP
-from a framework, such as OpenStack.
-`networking-spp
-<https://github.com/openstack/networking-spp>`_
-is a Neutron ML2 plugin for SPP and `spp-agent` works as a
-SPP controller.
-
-It is a problem to prepare several controllers for each of usages for
-CLI, OpenStack or others because it would be hard to maintain for
-updates.
-
-Spp-ctl is designed to solve the problem of several controllers with
-application-independent REST APIs.
-You can manage SPP by requesting via this APIs.
-
Architecture
------------
--
2.7.4
next prev parent reply other threads:[~2019-01-09 1:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 1:49 [spp] Update docs structure ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 01/11] docs: change structure of overview section ogawa.yasufumi
2019-01-09 1:49 ` ogawa.yasufumi [this message]
2019-01-09 1:49 ` [spp] [PATCH 03/11] docs: update image of SPP overview ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 04/11] docs: update overview section ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 05/11] docs: add overview image for design section ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 06/11] docs: add image of design of spp-ctl ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 07/11] docs: add SPP controller in design section ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 08/11] docs: add spp_primary " ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 09/11] docs: move design section to doc root ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 10/11] docs: move usecases " ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 11/11] docs: remove spp-ctl section 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=1546998573-26108-3-git-send-email-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).