diff options
author | Gerald Kunzmann <kunzmann@docomolab-euro.com> | 2016-01-12 06:40:41 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@172.30.200.206> | 2016-01-12 06:40:41 +0000 |
commit | 05fbd5c48c97f1f56f42261cdb671bbe7036ddd1 (patch) | |
tree | 2ed2390bd1e2a99bb07f2549d883b371fa770617 /docs/requirements/annex1.rst | |
parent | 598a47c4677cbc646ccb56d8e45677d3b94cfde6 (diff) | |
parent | 9fdb1e0b443e68f67b0978e27ec211bd7aa4cd89 (diff) |
Merge "Split Shim-layer architecture and Integrated architecture"
Diffstat (limited to 'docs/requirements/annex1.rst')
-rw-r--r-- | docs/requirements/annex1.rst | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/docs/requirements/annex1.rst b/docs/requirements/annex1.rst new file mode 100644 index 0000000..aa5546c --- /dev/null +++ b/docs/requirements/annex1.rst @@ -0,0 +1,34 @@ +.. _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 |