summaryrefslogtreecommitdiffstats
path: root/docs/requirements/90-annex1.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/90-annex1.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/90-annex1.rst')
-rw-r--r--docs/requirements/90-annex1.rst34
1 files changed, 0 insertions, 34 deletions
diff --git a/docs/requirements/90-annex1.rst b/docs/requirements/90-annex1.rst
deleted file mode 100644
index 8185b18..0000000
--- a/docs/requirements/90-annex1.rst
+++ /dev/null
@@ -1,34 +0,0 @@
-.. _uc-brahmaputra:
-
-ANNEX B: Use case for OPNFV Brahmaputra
-=======================================
-
-A basic resource reservation use case to be realized for OPNFV B-release may
-look as follows:
-
-* Step 0: Shim-layer is monitoring/querying available capacity at NFVI
-
- * Step 0a: Cloud operator creates a new OpenStack tenant user and updates
- quota values for this user
-
- * Step 0b: The tenant user is creating and instantiating a simple VNF
- (e.g. 1 network, 2 VMs)
-
- * Step 0c: OpenStack is notifying shim-layer about capacity change for
- this new tenant user
-
- * Step 0d: Cloud operator can visualize the changes using the GUI
-
-* Step 1: Consumer(NFVO) is sending a reservation request for future use to
- shim-layer
-
-* Step 2: Shim-layer is checking for available capacity at the given time
- window
-
-* Step 3: Shim-layer is responding with reservation identifier
-
-* Step 4 (optional): Consumer(NFVO) is sending an update reservation request
- to shim-layer (startTime set to now) -> continue with Steps 2 and 3.
-
-* Step 5: Consumer(VNFM) is requesting the allocation of virtualised resources
- using the reservation identifier in Step 3 \ No newline at end of file