1 ============================================
2 High level architecture and general features
3 ============================================
8 .. figure:: images/figure1.png
12 Resource Reservation Architecture
14 :numref:`figure1` shows the high level architecture for the resource
15 reservation use cases. Reserved resources are guaranteed for a given
16 user/client for the period expressed by start and end time. User/client
17 represents the requestor and the consequent consumer of the reserved
18 resources and correspond to the NFVO or VNFM in ETSI NFV terminology.
20 Note: in this document only reservation requests from NFVO are considered.
25 This section provides a list of features that need to be developed in the
28 * Resource capacity management
30 * Discovery of available resource capacity in resource providers
31 * Monitoring of available resource capacity in resource providers
32 * Update available resource capacity as a result of new or expired
33 reservations, addition/removal of resources. Note: this is a VIM internal
34 function, not an operation in the VIM northbound interface.
36 * Resource reservation
38 * Set start time and end time for allocation
39 * Increase/decrease reserved resource's capacity
40 * Update resource reservations, e.g. add/remove reserved resources
41 * Terminate an allocated resource due to the end time of a reservation
43 * VIM northbound interfaces
45 * Receive/Reply resource reservation requests
46 * Receive/Reply resource capacity management requests
47 * Receive/Reply resource allocation requests for reserved resources when
49 * Subscribe/Notify resource reservation event
51 * Notify reservation error or process completion prior to reservation start
52 * Notify remaining time until termination of a resource due to the end time
54 * Notify termination of a resource due to the end time of a reservation
56 * Receive/Reply queries on available resource capacity
57 * Subscribe/Notify changes in available resource capacity
59 High level northbound interface specification
60 =============================================
62 Resource Capacity Management
63 ----------------------------
65 .. figure:: images/figure2.png
69 Resource capacity management message flow: notification of capacity change
71 :numref:`figure2` shows a high level flow for a use case of resource capacity
72 management. In this example, the VIM notifies the NFVO of capacity change after
73 having received an event regarding a change in capacity (e.g. a fault
74 notification) from the NFVI. The NFVO can also retrieve detailed capacity
75 information using the Query Capacity Request interface operation.
77 .. figure:: images/figure3.png
81 Resource capacity management message flow: query of capacity density
83 :numref:`figure3` shows a high level flow for another use case of resource
84 capacity management. In this example, the NFVO queries the VIM about the
85 actual capacity to instantiate a certain resource according to a certain
86 template, for example a VM according to a certain flavor. In this case
87 the VIM responds with the number of VMs that could be instantiated according
88 to that flavor with the currently available capacity.
93 .. figure:: images/figure4.png
97 Resource reservation flow
99 :numref:`figure4` shows a high level flow for a use case of resource
103 * The NFVO sends a resource reservation request to the VIM using the Create
104 Resource Reservation Request interface operation.
105 * The NFVO gets a reservation identifier reservation associated with this
106 request in the reply message
107 * Using the reservation identifier reservation, the NFVO can
108 query/update/terminate a resource reservation using the corresponding
110 * The NFVO is notified that the resource reservation is terminated due to the
111 end time of the reservation
117 Resource Capacity Management
118 ----------------------------
120 Notify Capacity Change Event
121 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
123 The notification change message shall include the following information
126 ============================ ========== =====================================
127 Name Type Description
128 ============================ ========== =====================================
129 Notification Identifier Identifier issued by the VIM for the
130 capacity change event notification
131 Zone Identifier Identifier of the zone where capacity
133 Used/Reserved/Total Capacity List Used, reserved and total capacity
134 information regarding the resource
135 items subscribed for notification for
136 which capacity change event occurred
137 ============================ ========== =====================================
139 Query Resource Capacity Request
140 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
142 The capacity management query request message shall include the following
143 information elements:
145 ========== ========== ======================================================
146 Name Type Description
147 ========== ========== ======================================================
148 Zone Identifier Identifier of the zone where capacity is requested
149 Attributes List Attributes of resource items to be notified regarding
150 capacity change events
151 Resources List Identifiers of existing resource items to be queried
152 regarding capacity info (such as images, flavors,
153 virtual containers, networks, physical machines, etc.)
154 ========== ========== ======================================================
156 The capacity management query request message may also include the following
159 ====== ========== ==========================================================
160 Name Type Description
161 ====== ========== ==========================================================
162 Flavor Identifier Identifier that is passed in the request to obtain
163 information of the number of virtual resources that can be
164 instantiated according to this flavor with the available
166 ====== ========== ==========================================================
168 Query Resource Capacity Reply
169 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
171 The capacity management query reply message shall include the following
172 information elements:
174 ============================ ========== =====================================
175 Name Type Description
176 ============================ ========== =====================================
177 Zone Identifier Identifier of the zone where capacity
179 Used/Reserved/Total Capacity List Used, reserved and total capacity
180 information regarding each of the
181 resource items requested to check for
183 ============================ ========== =====================================
185 The detailed specification of the northbound interface for Capacity Management
186 in provided in section 5.1.1.
191 Create Resource Reservation Request
192 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
194 The create resource reservation request message shall include the following
195 information elements:
197 ========== ========== =========================================================
198 Name Type Description
199 ========== ========== =========================================================
200 Start Timestamp Start time for consumption of the reserved resources
201 End Timestamp End time for consumption of the reserved resources
202 Expiry Timestamp If not all reserved resources are allocated between start
203 time and expiry, the VIM shall release the corresponding
205 Amount Number Amount of the resources per resource item type (i.e.
206 compute/network/storage) that need to be reserved
207 Zone Identifier The zone where the resources need(s) to be reserved
208 Attributes List Attributes of the resources to be reserved such as DPDK
209 support, hypervisor, network link bandwidth, affinity
211 Resources List Identifiers of existing resource items to be reserved
212 (such as images, flavors, virtual containers, networks,
213 physical machines, etc.)
214 ========== ========== =========================================================
216 .. [#expiry] Expiry is a period around start time within which, the allocation
217 process must take place. If allocation process does not start
218 within the expiry period, the reservation becomes invalid and VIM
219 should release the resources
221 Create Resource Reservation Reply
222 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
224 The create resource reservation reply message shall include the following
225 information elements:
227 =========== ========== =======================================================
228 Name Type Description
229 =========== ========== =======================================================
230 Reservation Identifier Identification of the reservation instance. It can be
231 used by a consumer to modify the reservation later, and
232 to request the allocation of the reserved resources.
233 Message Text Output message that provides additional information
234 about the create resource reservation request (e.g. may
235 be a simple ACK if the request is being background
236 processed by the VIM)
237 =========== ========== =======================================================
239 Notify Reservation Event
240 ^^^^^^^^^^^^^^^^^^^^^^^^
242 The notification reservation event message shall include the following
243 information elements:
245 ============ ========== =====================================================
246 Name Type Description
247 ============ ========== =====================================================
248 Reservation Identifier Identification of the reservation instance triggering
250 Notification Identifier Identification of the resource event notification
252 Message Text Message describing the event
253 ============ ========== =====================================================
255 The detailed specification of the northbound interface for Resource Reservation
256 is provided in section 5.1.2.