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/intro.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/intro.rst')
-rw-r--r-- | docs/requirements/intro.rst | 39 |
1 files changed, 0 insertions, 39 deletions
diff --git a/docs/requirements/intro.rst b/docs/requirements/intro.rst deleted file mode 100644 index 654fdf9..0000000 --- a/docs/requirements/intro.rst +++ /dev/null @@ -1,39 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -============ -Introduction -============ - -Resource reservation is a basic function for the operation of a virtualized -telecom network. In resource reservation, VIM reserves resources for a certain -period as requested by the NFVO. A resource reservation will have a start time -which could be into the future. Therefore, the reserved resources shall be -available for the NFVO requested purpose (e.g. for a VNF) at the start time for -the duration asked by NFVO. Resources include all three resource types in an -NFVI i.e. compute, storage and network. - -Besides, NFVO requires abstracted NFVI resource capacity information in order -to take decisions on VNF placement and other operations related to the virtual -resources. VIM is required to inform the NFVO of NFVI resource state -information for this purpose. Promise project aims at delivering the detailed -requirements on these two features defined in ETSI NFV MAN GS [NFVMAN]_, -the list of gaps in upstream projects, potential implementation architecture -and plan, and the VIM northbound interface specification for resource -reservation and capacity management. - -Problem description -=================== - -OpenStack, a prominent candidate for the VIM, cannot reserve resources for -future use. OpenStack requires immediate instantiation of Virtual Machines -(VMs) in order to occupy resources intended to be reserved. Blazar can reserve -compute resources for future by keeping the VMs in shelved mode. However, such -reserved resources can also be used for scaling out rather than new VM -instantiation. Blazar does not support network and storage resource reservation -yet. - -Besides, OpenStack does not provide a northbound interface through which it can -notify an upper layer management entity e.g. NFVO about capacity changes in its -NFVI, periodically or in an event driven way. Capacity management is a feature -defined in ETSI NFV MAN GS [NFVMAN]_ and is required in network operation. |