diff options
| author |   Gerald Kunzmann <kunzmann@docomolab-euro.com> | 2016-01-29 09:42:34 +0000 |
|---|---|---|
| committer | Gerald Kunzmann <kunzmann@docomolab-euro.com> | 2016-01-29 09:42:34 +0000 |
| commit | 72b61bf2e993c4e8890174faaffe6c5dc6c4a9b4 (patch) | |
| tree | fe2c56c550398cd9eece1da4016173714e5112cd /requirements/resource_management/01-intro.rst | |
| parent | 6b64af495bf2f0e6f9f9e78411540a186d89b368 (diff) | |
Revert "Add requirement doc"
This reverts commit 6b64af495bf2f0e6f9f9e78411540a186d89b368.
Change-Id: Ib8c14a8b02d2eb77e4c124f61df72c8e4e79647b
Diffstat (limited to 'requirements/resource_management/01-intro.rst')
| -rw-r--r-- | requirements/resource_management/01-intro.rst | 37 |
1 files changed, 0 insertions, 37 deletions
diff --git a/requirements/resource_management/01-intro.rst b/requirements/resource_management/01-intro.rst deleted file mode 100644 index fdceaf1..0000000 --- a/requirements/resource_management/01-intro.rst +++ /dev/null @@ -1,37 +0,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 [5], 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 [5] and is required in network operation. |