diff options
author | Gerald Kunzmann <kunzmann@docomolab-euro.com> | 2017-03-07 15:07:42 +0000 |
---|---|---|
committer | Gerald Kunzmann <kunzmann@docomolab-euro.com> | 2017-03-07 15:15:40 +0000 |
commit | 6006ef9d98c872d15ab3b15bac47a6178fe5cb88 (patch) | |
tree | 0dc0a6c0ad8e4c186392afc5a5afed33cc106ea2 /docs/development | |
parent | 8875d28761c945a083c5628d3f4a10f4cd42058c (diff) |
Various updates to documentation, e.g. remove the history table
Change-Id: If7dca26bf63dde6f5724347a0363326afd5a39eb
Signed-off-by: Gerald Kunzmann <kunzmann@docomolab-euro.com>
Diffstat (limited to 'docs/development')
-rw-r--r-- | docs/development/requirements/index.rst | 10 | ||||
-rw-r--r-- | docs/development/requirements/revision.rst | 43 | ||||
-rw-r--r-- | docs/development/requirements/summary.rst | 7 |
3 files changed, 2 insertions, 58 deletions
diff --git a/docs/development/requirements/index.rst b/docs/development/requirements/index.rst index 00edf0e..ae7acc7 100644 --- a/docs/development/requirements/index.rst +++ b/docs/development/requirements/index.rst @@ -11,15 +11,6 @@ Promise: Resource Management Gerald Kunzmann (NTT DOCOMO), Ryota Mibu (NEC), Carlos Goncalves (NEC), Arturo Martin De Nicolas (Ericsson) -:History: - ========== ===================================================== - Date Description - ========== ===================================================== - 04.12.2014 Project creation - 20.04.2015 Initial version of the deliverable uploaded to gerrit - 19.06.2015 Stable version of the Promise deliverable - ========== ===================================================== - :Abstract: Promise is an OPNFV requirement project. Its objective is to realize ETSI NFV defined resource reservation and NFVI capacity features within the scope of OPNFV. Promise provides the details of the @@ -49,4 +40,3 @@ Promise: Resource Management annex1.rst schemas.rst supported_apis.rst - revision.rst diff --git a/docs/development/requirements/revision.rst b/docs/development/requirements/revision.rst deleted file mode 100644 index cd0b76b..0000000 --- a/docs/development/requirements/revision.rst +++ /dev/null @@ -1,43 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -ANNEX D: Document revision -========================== - -+---------+-----------------------------------------+ -| Version | Description | -+---------+-----------------------------------------+ -| 1.0.1 | JIRA: PROMISE-23 | -| | - Reference to YangForge Framework | -| | - Corrections to figure 3.1 | -+---------+-----------------------------------------+ -| 1.0.2 | JIRA: PROMISE-11 | -| | - OPNFV Logo Added | -| | - Alignment to ETSI NFV Specs | -+---------+-----------------------------------------+ -| 1.0.3 | JIRA: PROMISE-54 | -| | - Use case for Brahmaputra | -+---------+-----------------------------------------+ -| 1.0.4 | JIRA: PROMISE-60 | -| | - Editorial fixes | -| | | -| | JIRA: PROMISE-57 | -| | - Split shim-layer architecture and | -| | integrated architecture sections | -+---------+-----------------------------------------+ -| 1.0.5 | JIRA: PROMISE-61 | -| | - Updated Promise Yang Schema | -+---------+-----------------------------------------+ -| 1.0.6 | JIRA: PROMISE-62 | -| | - Supported APIs for Brahmaputra | -+---------+-----------------------------------------+ -| 1.0.7 | JIRA: PROMISE-63 | -| | - Update message flow for shim-layer | -| | JIRA: PROMISE-58 | -| | - Integrated approach description | -| | JIRA: PROMISE-64 | -| | - Promise userguide | -+---------+-----------------------------------------+ -| 1.0.8 | JIRA: PROMISE-11 | -| | - Alignment to ETSI NVF Specs | -+---------+-----------------------------------------+ diff --git a/docs/development/requirements/summary.rst b/docs/development/requirements/summary.rst index fcf10d1..cf6ed88 100644 --- a/docs/development/requirements/summary.rst +++ b/docs/development/requirements/summary.rst @@ -20,8 +20,5 @@ the VNFM. The use cases include: * Reservation of a resource or set of resources for future use The Promise project has performed a gap analysis in order to fulfill the -required functionality. Based on the gap analysis an implementation plan and -way forward has been proposed, including a possible design architecture and -high level information model. Immediate next steps of this project is to -deliver a working Proof-of-Concepts (PoC) and engage upstream communities to -fill out the gaps identified by Promise. +required functionality. Based on the gap analysis an implementation plan an +architecture, information model and northbound interface has been specified. |