diff options
| author |   Gerald Kunzmann <kunzmann@docomolab-euro.com> | 2017-02-09 09:36:29 +0000 |
|---|---|---|
| committer | Gerald Kunzmann <kunzmann@docomolab-euro.com> | 2017-02-15 15:30:08 +0000 |
| commit | 78aa63af02df682b3c8d825c1bec9cec6cd3b207 (patch) | |
| tree | 26ea243c8ac8c6e921c1c93d8292eb569f814dae /docs/requirements/annex1.rst | |
| parent | b74c2245db019bfadcae29190de4caa6fc6f826d (diff) | |
Update docs structure according to new guidelines in https://wiki.opnfv.org/display/DOC
Change-Id: I69e6536d9044dd9db2ed3cd698059aa3a800c318
Signed-off-by: Gerald Kunzmann <kunzmann@docomolab-euro.com>
Diffstat (limited to 'docs/requirements/annex1.rst')
| -rw-r--r-- | docs/requirements/annex1.rst | 37 |
1 files changed, 0 insertions, 37 deletions
diff --git a/docs/requirements/annex1.rst b/docs/requirements/annex1.rst deleted file mode 100644 index 65a5f22..0000000 --- a/docs/requirements/annex1.rst +++ /dev/null @@ -1,37 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -.. _uc-brahmaputra: - -ANNEX A: 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 |