4 The following section describes how to create an E2E service.
9 The following section will create a license model. The license model is required for onboarding a VNF.
11 - Log into ONAP portal with designer role (cs0008)
13 - Select SDC from the application
17 - Click on CREATE NEW VLM
19 - Specify the name of the license <licenseName>
21 - Specify the description of the license
23 - Select Entitlement pools from left
25 - Click on ADD ENTITLEMENT POOL on right
27 - Specify the name (can be anything)
31 - Select License key groups from left
33 - Click on ADD LICENSE KEY GROUP
35 - Specify the name (can be anything)
37 - Select universal type
41 - Select Feature groups from left
43 - Click on ADD FEATURE GROUP
45 - Specify the name (can be anything) <featureGroup>
47 - Set 123456 as part number
49 - Set 123456 as manufacturer reference number
51 - Click on entitlement pools in middle
53 - Add previously created entitlement pool with arrow button
55 - Click on license key groups in middle
57 - Add previously created license key group with arrow button
61 - Select License agreements from left
63 - Click on ADD LICENSE AGREEMENT on right
65 - Specify the name (can be anything)
67 - Select unlimited license term
69 - Click on feature groups
71 - Add previously created feature group with arrow button
73 - Click on the submit button on top right
75 Prepare the ETSI configuration JSON
76 -----------------------------------
78 The ETSI configuration of VF is the information gap that is required to instantiate a VNF, but this information is not
79 provided by the VF-C component to the VNFM. The ETSI configuration is a JSON serialized into a string, which is specified
80 as a VF property during VF design time.
82 The JSON has the following root elements:
84 - vimType: The type of the VIM
86 - instantiationLevel: The initial instantiation level of the VNF.
88 - computeResourceFlavours: The collection of compute flavors.
90 - zones: The collection of availability zones.
92 - softwareImages: The collection of software images.
94 - extManagedVirtualLinks: The collection of externally managed virtual links.
96 - externalConnectionPointAddresses: Addresses of the external connection points.
98 - extVirtualLinks: The collection of external virtual links.
100 - extensions: The collection of VNF properties
102 - additionalParams: Additional parameters passed during instantiation to the VNFM.
104 - domain: The domain of the OpenStack cloud (only available in Amsterdam)
110 The following section requires the CSAR and the ETSI configuration of the VNF to be available as a prerequisite.
112 - Log into ONAP portal with designer role (cs0008)
114 - Select SDC from the application
118 - Click on CREATE NEW VSP
120 - Specify a the name of the VNF <vnfPackageName> (ex. vnf_simple_20180526_1)
122 - Select the previously created license model as vendor
124 - Select Database (General) for the category. It is important to select a category that has been linked to the customer.
126 - Select network package for onboarding procedure
128 - Specify description
132 - Click on SELECT FILE from SOFTWARE PRODUCT ATTACHMENTS and upload the CSAR file
134 - Click on General on the left
136 - Select 1.0 as for licensing version under LICENSES
138 - Select the previously created license agreement <licenseName>
140 - Select the previously created feature group <featureGroup>
142 - Click on save icon at top right
144 - Click on Submit icon at top right
146 - Select HOME using the small arrow left from ONBOARD at top
148 - Hoover over the import icon and select Import VSP
150 - Select the created VSP from the list by name <vnfPackageName>
152 - Click on import VSP icon
154 - Set the CBAM VNF package identifier as the Vendor model number on left bottom
156 - Click on create on top right
158 - Click on Properties assignment on left
162 - Specify NokiaSVNFM for the nf_type property
164 - Click on Save on the middle
168 - Specify the ETSI configuration JSON for the etsi_config property
170 - If the ETSI configuration is larger than the maximal allowed value for a field
172 - Instead of specifying it using a property click on Deployment Artifact at left
174 - Click on Add other artifact at bottom middle
176 - Specify etsiConfig as Artifact Label
178 - Choose OTHER for type
180 - Specify anything for Description
182 - Select the ETSI configuration file using Browse
184 - the name of the file on the local file system must be etsi_config.json
190 - Search for the created VNF using the search box at top right <vnfPackageName>
194 - Click on submit for testing at top right
196 - Log out using the small person icon at top right
198 - Log in with tester role (jm0007)
200 - Select SDC from the application
202 - Search for the created VNF using the search box at top right <vnfPackageName>
204 - Click on Start testing
208 - Log out using the small person icon at top right
211 Design a network service
212 ------------------------
214 The following section design a network service. The prerequisite is that the tested VF package is available.
216 - Log into ONAP portal with designer role (cs0008)
218 - Select SDC from the application
222 - Hoover over the Add icon and select add service
224 - Specify the name of the network service <nsName> (ex. ns_simple_20180526_1)
226 - Specify 123456 ad project code
228 - Specify description
230 - Select Network Service for the category
232 - If the network service is missing from the list
234 - Log in as demo user and select SDC and create the Network Service category
238 - Click on Composition at left
240 - Search for the created VF using the search box at top left <vnfPackageName>
242 - Drag the VF icon to middle
244 - Wait for the icon to appear at the middle (only drag once)
246 - Click on the icon on the middle
248 - Click on very small pencil icon at top right
250 - Specify the name of the VF
254 - Search for the created NS using the search box at top right <nsName>
256 - Click on the NS icon
258 - Click on Submit for testing
260 - Log out using the small person icon at top right
262 - Log in with tester role (jm0007)
264 - Select SDC from the application
266 - Search for the created VNF using the search box at top right <vnfPackageName>
268 - Click on Start testing
272 - Log out using the small person icon at top right
274 - Log in with tester role (gv0001)
276 - Select SDC from the application
278 - Search for the created VNF using the search box at top right <vnfPackageName>
280 - Click on Approve on top right
282 - Log out using the small person icon at top right
284 - Log in with operation role (op0001)
286 - Select SDC from the application
288 - Search for the created VNF using the search box at top right <vnfPackageName>
290 - Click on Distribute on top right
292 - Click on monitor in an order to verify that the distribution was successful
294 - Click on the small arrow next to the Distribution ID
296 - The list should contain at least two lines staring with sdc and aai-ml
298 - If the list does not contain enough elements it can be refreshed with the small icon at middle right
300 - Each of the two lines should contain a green check sign next to Deployed
302 - Log out using the small person icon at top right
306 Design a VF for the E2E service
307 -------------------------------
309 This step is only required if the UUI is planed to be used to manage the E2E service. The VF of the E2E service is
310 a wrapper to be able to treat the created NS as a VF. The prerequisite of this step is that the network service was
311 successfully distributed.
313 - Determine the UUIDs of the created NS in previous step
315 - Using a REST client of your choice, send a request to the following URL: https://sdc.api.simpledemo.onap.org:8443/sdc/v1/catalog/services
319 - Set the following values in the Header of the request:
323 - X-ECOMP-InstanceID: VFC
325 - Accept: application/json
327 - Search for the created service by name <nsName> and note the uuid and invariantUUID fields
329 - Log in with designer role (cs0008)
331 - Select SDC from the application
335 - Hoover over the Add icon and select add VF
337 - Specify the name of the VF <vfForNsName> (ex. vf_for_ns_simple_20180526_1_vIMS)
339 - the name must contain the vIMS character sequence (even if this is not an IMS)
341 - Specify something for the Vendor
343 - Specify any numeric value for the Vendor Release
345 - Specify something for description
347 - Select Network Service for the category
349 - Click on Create on top right
351 - Click on Composition at left
353 - Search for the NSD using the search box at top left
355 - Drag the NSD icon to middle
357 - Wait for the icon to appear at the middle (only drag once)
359 - Click on the icon on the middle
361 - Click on very small pencil icon at top right
363 - Specify the name of the NSD (ex. firstNsd ) <nsdName>
365 - Click on the name of the VF next to HOME at top
367 - Select Properties Assignment
369 - Select the check box before providing_service_uuid and providing_service_invariant_uuid properties
371 - Click on Declare at right
373 - Click on Inputs at middle
375 - Specify the UUID of the service (that was determined in previous step) for the <nsdName>_providing_service_uuid property
377 - Specify the invariant UUID of the service (that was determined in previous step) for the <nsdName>_providing_service_invariant_uuid property
383 - Search for the created VF using the search box at top right <vfForNsName>
385 - Click on the VF icon
387 - Click on Submit for testing
389 - Log out using the small person icon at top right
391 - Log in with tester role (jm0007)
393 - Select SDC from the application
395 - Search for the created VNF using the search box at top right <vfForNsName>
397 - Click on Start testing
401 - Log out using the small person icon at top right
407 This step is only required if the UUI is planed to be used to manage the E2E service. The prerequisite of this step is that the VF
408 wrapping the network service is tested.
410 - Log in with designer role (cs0008)
412 - Select SDC from the application
416 - Hoover over the Add icon and select add Service
418 - Specify the name of the NS <e2eNsName> (ex. e2e_simple_20180526_1)
420 - Specify any numeric value for the Project Code
422 - Specify something for description
424 - Select E2E Service for the category
426 - Click on Create on top right
428 - Click on Composition at left
430 - Search for the created VF using the search box at top left <vfForNsName>
432 - Drag the VF icon to middle
434 - Wait for the icon to appear at the middle (only drag once)
436 - Click on the name of the NS next to HOME at top
440 - Search for the created NS using the search box at top right <e2eNsName>
442 - Click on the NS icon
444 - Click on Submit for testing
446 - Log out using the small person icon at top right
448 - Log in with tester role (jm0007)
450 - Select SDC from the application
452 - Search for the created NS using the search box at top right <e2eNsName>
454 - Click on Start testing
458 - Log out using the small person icon at top right
460 - Log in with tester role (gv0001)
462 - Select SDC from the application
464 - Search for the created VNF using the search box at top right <e2eNsName>
466 - Click on Approve on top right
468 - Log out using the small person icon at top right
470 - Log in with operation role (op0001)
472 - Select SDC from the application
474 - Search for the created VNF using the search box at top right <e2eNsName>
476 - Click on Distribute on top right
478 - Click on monitor in an order to verify that the distribution was successful
480 - Click on the small arrow next to the Distribution ID
482 - The list should contain at least two lines staring with sdc and aai-ml
484 - If the list does not contain enough elements it can be refreshed with the small icon at middle right
486 - Each of the two lines should contain a green check sign next to Deployed
488 - Log out using the small person icon at top right