summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorGergely Csatari <gergely.csatari@nokia.com>2016-05-09 17:57:26 +0200
committerGeorg Kunz <georg.kunz@ericsson.com>2016-05-10 19:11:20 +0200
commit431339258a4629d8c7ca5185d115863860652e2c (patch)
treec14b6bfd862ad77522917c8d52e7a0c81f73547b /docs
parentc43b4b3554b695ba7c32afceb8d34ee57472680d (diff)
First draft of programmable provisioning use cases.
Change-Id: Iedcffde320ac2e68918e0ade59380e451aaf3730 Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/requirements/use_cases.rst5
-rw-r--r--docs/requirements/use_cases/programmable_provisioning.rst38
2 files changed, 40 insertions, 3 deletions
diff --git a/docs/requirements/use_cases.rst b/docs/requirements/use_cases.rst
index 3f9f009..0aabc65 100644
--- a/docs/requirements/use_cases.rst
+++ b/docs/requirements/use_cases.rst
@@ -6,7 +6,6 @@ Use cases
The following sections address networking use cases that have been identified to be relevant in the scope of NFV and NetReady.
-.. include::
+.. toctree::
use_cases/shared-service-functions.rst
-.. -> Add references to your use cases here.
-.. -> We can easily sort and structure use cases based on their order of inclusion
+ use_cases/programmable_provisioning.rst
diff --git a/docs/requirements/use_cases/programmable_provisioning.rst b/docs/requirements/use_cases/programmable_provisioning.rst
new file mode 100644
index 0000000..e08775b
--- /dev/null
+++ b/docs/requirements/use_cases/programmable_provisioning.rst
@@ -0,0 +1,38 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+Programmable Provisioning of Provider networks
+----------------------------------------------
+Description
+~~~~~~~~~~~
+In NFV environment the VNFM (consumer of OpenStack IaaS API) have no administrative
+rights, however in this environment provider networks are used in some cases.
+When a provider network is ceated administrative rights are needed what in the
+case of non admin VNFM leeds to manual work.
+It shall be possible to configure provider networks without administrative rights.
+It should be possible to assign the capability to create provider networks to any roles.
+
+Derrived Requirements
+~~~~~~~~~~~~~~~~~~~~~
+ - Possibility to assign the property of provider networks to any role
+ - When the provider network is created it should be checked if the role of the user has the permission to create a provider network.
+
+Northbound API / Workflow
++++++++++++++++++++++++++
+ - TBD
+
+Data model objects
+++++++++++++++++++
+ - TBD
+
+Orchestration
++++++++++++++
+ - TBD
+
+Dependencies on compute services
+++++++++++++++++++++++++++++++++
+ - TBD
+
+Potential implementation
+++++++++++++++++++++++++
+ - TBD