From 7381fa56501f8a1c51b13e511f4bd6c44977a4d2 Mon Sep 17 00:00:00 2001 From: Ryota MIBU Date: Mon, 20 Apr 2015 09:29:54 +0900 Subject: Add requirement doc Change-Id: Ibfd83f84ae47291ece09150af9f35d38ef3a1288 JIRA: PROMISE-1 Signed-off-by: Ryota MIBU --- requirements/resource_management/01-intro.rst | 37 +++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 requirements/resource_management/01-intro.rst (limited to 'requirements/resource_management/01-intro.rst') diff --git a/requirements/resource_management/01-intro.rst b/requirements/resource_management/01-intro.rst new file mode 100644 index 0000000..fdceaf1 --- /dev/null +++ b/requirements/resource_management/01-intro.rst @@ -0,0 +1,37 @@ + +============ +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. -- cgit 1.2.3-korg