blob: 65a5f22addeaf9f7dc9ae317dedd5eaa00de0ab9 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
.. 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
|
