1 .. This work is licensed under a Creative Commons Attribution 4.0
3 .. http://creativecommons.org/licenses/by/4.0
6 Instantiate Service, VNF, VF modules and Network
7 ================================================
13 Using VID with A-La-Carte method means that the user needs to performed
14 by himself the instantiation of each object: service, VNF(s), VF module(s),
17 ONAP to VIM interactions will occurs when instantiating/deleting VF module(s)
18 or Network(s). In case of an Openstack VIM, Heat Stack(s) will
21 In the following description, the service model in SDC was composed of 1 VF
22 and 1 Virtual Link (Generic Neutron Network)
25 For doing this make sure that while Service Design drag the created VF and Generic NetronNet Virtual Link (under Generic/Network Elemntes list) from the
26 Elements palette to the canvas then connect as mentoned in Create Service section of Service Design under Composition
28 To be able to instantiate VF-module or Network object, some data need to be
29 declared in ONAP SDNC using SDNC Rest API. It is the place where to put
30 the instance specific values such as an IP address value specific
31 to the VNF instance for example.
33 In VID, terminologies are sometimes different than in other components:
35 VNF in VID = VF in SDC
37 Node instance = VF in SDC
39 Network = Virtual Link in SDC
45 Pre-instantiation operations must have been performed in AAI and VID,
46 via Rest API, to declare some values for:
48 - Subscriber Name (= customer in AAI)
49 - Service Type or product family (= service subscription in AAI)
54 - LCP Region (= CloudOwner/RegionId in AAI)
57 See, in the ONAP User Guides, section about adding a CloudSite
58 and section about pre-instantiation Operations
61 Robot demo script will be used to populate demo models automatically with Demonstration as Subscriber Name in VID by running "demo-k8s.sh onap init"
66 .. figure:: images/onap-portal.png
71 .. figure:: images/vid-icon-on-portal.png
75 Here after, the VID Home page starts
77 .. figure:: images/home.png
84 Select the API for "A-la-carte"
86 There are two choices:
88 - VNF_API (old) : VID will use the (old) "VNF" SDNC API
89 to get/check some parameters
90 - GR_API (new) : VID will use the "Generic Resource"
91 SDNC API to get/check some parameters
93 .. figure:: images/API_selection.png
98 Instantiate Service in "A-la-carte" mode
99 ----------------------------------------
101 Click Browse SDC Service Models and search for the service to instantiate.
103 The view show only service models in the DISTRIBUTED state.
105 .. figure:: images/browse-service-models.png
109 Select a service and click Deploy.
111 A dialog box displays.
113 Complete the fields indicated by the red star and click Confirm.
115 .. figure:: images/create-service-instance-alacarte.png
118 A status box appears that shows the ONAP SO instantiation progress
119 as well as any messages associated with the process.
121 .. figure:: images/create-service-instance-alacarte-success.png
124 A Service object is created in ONAP.
126 Click Close and next screen should appear.
127 It will allow to declare VNF(s) and Network(s)
128 that are part of the service model composition.
130 .. figure:: images/create-service-instance-alacarte-VNF-network.png
137 From previous screen, it is possible to declare a VNF: click on
138 "Add node instance" and select the VNF you want to instantiate in the list
140 The following screen should appear:
142 .. figure:: images/create-vnf-instance-alacarte.png
145 Complete the fields indicated by the red star and click Confirm.
147 A VNF object will be declared in ONAP.
149 Once, ONAP SO process is finished, click on close button.
151 The following screen then should appear:
154 .. figure:: images/create-service-instance-alacarte-after-vnf-instantiated.png
158 Warning: a this step, no VNF instance (e.g. VM) is created on the Cloud Platform.
160 Click on "i" blue button to obtain VNF instance display information.
162 From this screen, it will be possible to get:
164 - the service instance id value
167 Those information will be necessary for the "SDNC preload" step
168 to instantiate the VF module
173 Instantiate VF Module
174 ---------------------
176 It is now possible to declare a VF Module: click on
177 "Add VF-Module" and select the VF-module you want to instantiate in the list
179 The following screen should appear:
181 .. figure:: images/create-vfmodule-instance-alacarte.png
184 From this screen, it will be possible to get:
188 At this step, with this "A-La-Carte" method, it is necessary to declare
189 some information in ONAP SDNC.
191 SDNC needs to be aware about the VNF before trying to use ONAP SO
192 to instantiate the VF-module.
194 This group of data is usually called "SDNC preload" and will contain:
196 - vf-module instance Name
198 - service instance id
199 - the list of vnf parameters with values, when not using the default values
202 Get all the required vnf-parameters values as listed in HEAT package and populate all the key-values in an example SDNC preload curl command to run
204 Some of the vnf-parameters in SDNC preload are related to openstack.
205 Follow the below steps on openstack to get the values and update those values in SDNC preload template accordingly.
207 - download the image from cloud images (ubuntu-14.04 as per HEAT env) and create an image
208 - create the flavor with m1.medium (suggested as per HEAT env)
209 - create OAM_NETWORK ID & OAM_SUBNET ID (use subnet range from base_vfw.env file)
210 - execute openstack security group rule to open all ports for onap
212 Here is an example of SDNC preload for VNF, using "curl" tool
213 to push those data using SDNC Rest API:
218 https://sdnc.api.simpledemo.onap.org:30267/restconf/operations/VNF-API:preload-vnf-topology-operation \
219 -H 'Accept: application/json' \
220 -H 'Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==' \
221 -H 'Content-Type: application/json' \
222 -H 'X-FromAppId: API client' \
223 -H 'X-TransactionId: 0a3f6713-ba96-4971-a6f8-c2da85a3176e' \
224 -H 'cache-control: no-cache' \
227 "request-information": {
228 "notification-url": "onap.org",
230 "order-version": "1",
231 "request-action": "PreloadVNFRequest",
234 "sdnc-request-header": {
235 "svc-action": "reserve",
236 "svc-notification-url": "http:\/\/onap.org:8080\/adapters\/rest\/SDNCNotify",
237 "svc-request-id": "test"
239 "vnf-topology-information": {
241 "availability-zones": [],
247 "vnf-parameter-name": "oam_net_id",
248 "vnf-parameter-value": "oam_network_tXWW"
251 "vnf-topology-identifier": {
252 "generic-vnf-name": "my-vnf-instance-01",
253 "generic-vnf-type": "Service-model-with-VNF-and-Virtual-Link/FreeRadius_VF 0",
254 "service-type": "09f9ffad-1069-43fa-97e8-da7b9a439601",
255 "vnf-name": "my_vf_module-instance-01",
256 "vnf-type": "FreeradiusVf..base_freeRadius..module-0"
263 Data mapping between ONAP SDNC terminology and ONAP SO
265 - "generic-vnf-name" value must be equal to the VNF instance name value
266 (see VNF instance detail screen)
267 - "generic-vnf-type" value must be equal to VNF Type value
268 (see VNF instance detail screen)
269 - "service-type" value must be equal to the service instance id value
270 (see VNF instance detail screen)
271 - "vnf-name" value must be equal to the VF module instance name value
272 - "vnf-type" value must be equal to the "Model Name" value
273 (see create VF module screen)
276 If there is a need for an instance specific value
277 of a VNF parameter (for example : an OAM network id value,
278 specific to this VNF instance),
279 the "vnf-parameters" must be completed with a list of name/value.
281 Once the "SDNC preload" is completed, send it to SDNC using any Rest API Tool.
283 Then, continue on VID and complete the fields indicated by the red star
286 Warning : be very careful to use exactly the same VF module instance name
287 on this screen and in the "SDNC preload"
289 Wait for success and close the popup screen.
291 The following screen should appear:
293 .. figure:: images/create-service-instance-alacarte-after-vfmodule-instantiated.png
296 At that point, the VNF is now instantiated in the cloud platform.
302 Instantiating a network is quite similar to vf-module instantiation
303 (there is also the need for a "SDNC preload")
305 Click on "Add Network" and select the Network you want
306 to instantiate in the list
308 The following screen should appear:
310 .. figure:: images/create-network-instance-alacarte.png
314 Prepare the "SDNC preload" with:
316 - "network-role": provide any value,
317 - "network-technology": use "neutron" as this example will instantiate
318 a network using openstack neutron application
319 - "service-type": value must be equal to "Service Name"
320 (=service model name) displayed on VID screen
321 - "network-name": value must be equal to the desired network instance name,
322 - "network-type": value must be equal to "Model Name""Generic NeutronNet"
323 displayed on VID screen
327 - in "provider-network-information" section, it is possible to indicate
328 some network characteristics
329 - it is possible to add a section about "subnets"
331 Here after, an "SDNC preload" example that can be use for Network
337 https://sdnc.api.simpledemo.onap.org:30267/restconf/operations/VNF-API:preload-network-topology-operation \
338 -H 'Accept: application/json' \
339 -H 'Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==' \
340 -H 'Content-Type: application/json' \
341 -H 'X-FromAppId: API client' \
342 -H 'X-TransactionId: 0a3f6713-ba96-4971-a6f8-c2da85a3176e' \
343 -H 'cache-control: no-cache' \
346 "request-information": {
347 "request-id": "postman001",
348 "notification-url": "http://so.onap.org",
349 "order-number": "postman001",
350 "request-sub-action": "SUPP",
351 "request-action": "PreloadNetworkRequest",
353 "order-version": "1.0"
355 "network-topology-information": {
356 "network-policy": [],
357 "route-table-reference": [],
359 "network-topology-identifier": {
360 "network-role": "integration_test_net",
361 "network-technology": "neutron",
362 "service-type": "Service-model-with-VNF-and-Virtual-Link",
363 "network-name": "my-network-instance-001",
364 "network-type": "Generic NeutronNet"
366 "provider-network-information": {
367 "is-external-network": "false",
368 "is-provider-network": "false",
369 "is-shared-network": "false"
373 "subnet-name": "my-sub_network-instance-001",
374 "subnet-role": "OAM",
375 "start-address": "192.168.90.0",
379 "dhcp-start-address": "",
380 "dhcp-end-address": "",
381 "gateway-address": "192.168.90.1",
386 "sdnc-request-header": {
387 "svc-action": "reserve",
388 "svc-notification-url": "http://so.onap.org",
389 "svc-request-id": "postman001"
395 Once the "SDNC preload" is completed, send it to SDNC using any Rest API Tool.
397 Then, continue on VID and complete the fields indicated by the red star
400 Warning : be very careful to use exactly the same network instance name
401 on this screen and in the "SDNC preload"
403 Wait for success and close the popup screen.
405 The following screen should appear:
407 .. figure:: images/create-network-instance-alacarte-after-instantiated.png
410 At that point, the Network and subnets are now instantiated
411 in the cloud platform.
413 Also, all those network information are available in ONAP AAI,
414 under the terminology
415 "l3-network", with the "neutron-network-id" and the "neutron-subnet-id"
417 the openstack platform.
420 Deleting Network, VF module, VNF, Service
421 -----------------------------------------
423 To delete a service instance using VID, it is necessary to delete objects
424 in the following sequence:
426 - delete VF module(s)
427 - delete VNF instance(s)
429 - delete service instance
431 To proceed those deletion, from VID Home screen
433 - search for existing service instance
434 - edit/view the service instance you want to delete
435 - click on red button with white cross and confirm for each object