From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148]) by dpdk.org (Postfix) with ESMTP id F36471B202 for ; Wed, 9 Jan 2019 02:51:44 +0100 (CET) Received: from vc1.ecl.ntt.co.jp (vc1.ecl.ntt.co.jp [129.60.86.153]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id x091phIB016704; Wed, 9 Jan 2019 10:51:43 +0900 Received: from vc1.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 99A5CEA728E; Wed, 9 Jan 2019 10:51:43 +0900 (JST) Received: from localhost.localdomain (lobster.nslab.ecl.ntt.co.jp [129.60.13.95]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 785CAEA6F01; Wed, 9 Jan 2019 10:51:43 +0900 (JST) From: ogawa.yasufumi@lab.ntt.co.jp To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp Date: Wed, 9 Jan 2019 10:49:23 +0900 Message-Id: <1546998573-26108-3-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1546998573-26108-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> References: <1546998573-26108-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> X-TM-AS-MML: disable Subject: [spp] [PATCH 02/11] docs: move overview of spp-ctl to SPP overview X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2019 01:51:45 -0000 From: Yasufumi Ogawa Move overview of spp-ctl to SPP's overvew section. Signed-off-by: Yasufumi Ogawa --- 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 +`_ +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 -`_ -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