diff options
| author |   Ryota MIBU <r-mibu@cq.jp.nec.com> | 2015-12-02 00:35:21 +0900 |
|---|---|---|
| committer | Ryota MIBU <r-mibu@cq.jp.nec.com> | 2015-12-04 22:07:22 +0900 |
| commit | a90c29deddc599027822dd1ee61b8cd58021f651 (patch) | |
| tree | 7212038536434d02f10a6ec394a2e7b009a4256e /requirements/01-intro.rst | |
| parent | 2f1d84a7879c5db5e974c4482e40734abb062657 (diff) | |
change dirs to use new opnfv doc build script
Change-Id: Ifbf8a881d0e1a962f2e3cf276fe3942b1f03d3ee
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
Diffstat (limited to 'requirements/01-intro.rst')
| -rw-r--r-- | requirements/01-intro.rst | 37 |
1 files changed, 0 insertions, 37 deletions
diff --git a/requirements/01-intro.rst b/requirements/01-intro.rst deleted file mode 100644 index 6738df2..0000000 --- a/requirements/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 [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. |