summaryrefslogtreecommitdiffstats
path: root/docs/requirements/summary.rst
diff options
context:
space:
mode:
authorGerald Kunzmann <kunzmann@docomolab-euro.com>2016-01-07 13:55:58 +0100
committerGerald Kunzmann <kunzmann@docomolab-euro.com>2016-01-07 14:15:55 +0100
commit9fdb1e0b443e68f67b0978e27ec211bd7aa4cd89 (patch)
treedc6a02bb87ef699134810f2b1a6637bf8fe34770 /docs/requirements/summary.rst
parent127b173d18c76993efc8fdf16eebb6cd3994d661 (diff)
Split Shim-layer architecture and Integrated architecture
Create two sub-sections in "05 Detailed architecture" for the Shim-layer architecture and the Integrated architecture. Fix several implementations bugs and warnings. Remove numbering of files. JIRA: PROMISE-57 Change-Id: Ia0b4067c0cc3a461e54b6b010f8310764fb08d73
Diffstat (limited to 'docs/requirements/summary.rst')
-rw-r--r--docs/requirements/summary.rst24
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/requirements/summary.rst b/docs/requirements/summary.rst
new file mode 100644
index 0000000..ebd2bb9
--- /dev/null
+++ b/docs/requirements/summary.rst
@@ -0,0 +1,24 @@
+======================
+Summary and conclusion
+======================
+
+Resource Reservation and Resource Capacity Management are features to be
+supported by the VIM and exposed to the consumer via the VIM NBI. These
+features have been specified by ETSI NFV.
+
+This document has described several use cases and corresponding high level
+flows where Resource Reservation and Capacity Management are of great benefit
+for the consumer of the virtualised resource management interface: the NFVO or
+the VNFM. The use cases include:
+
+* Notification of changes in capacity in the NFVI
+* Query of available resource capacity
+* Reservation of a resource or set of resources for immediate use
+* 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.