From 4dcbec01916b8fdab3ee88f6748a0076c24c6f6a Mon Sep 17 00:00:00 2001 From: Gerald Kunzmann Date: Wed, 9 Dec 2015 12:28:27 +0100 Subject: Use case for Brahmaputra This patch is adding the agreed use case for B-release to the Annex of the requirement document. JIRA: PROMISE-54 Change-Id: Id63bbcf49d53ddd07920721a5b9b12e9d9410036 --- docs/requirements/90-annex1.rst | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 docs/requirements/90-annex1.rst (limited to 'docs/requirements/90-annex1.rst') diff --git a/docs/requirements/90-annex1.rst b/docs/requirements/90-annex1.rst new file mode 100644 index 0000000..8185b18 --- /dev/null +++ b/docs/requirements/90-annex1.rst @@ -0,0 +1,34 @@ +.. _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 -- cgit