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
188 - Search for the created VNF using the search box at top right <vnfPackageName>
192 - Click on submit for testing at top right
194 - Log out using the small person icon at top right
196 - Log in with tester role (jm0007)
198 - Select SDC from the application
200 - Search for the created VNF using the search box at top right <vnfPackageName>
202 - Click on Start testing
206 - Log out using the small person icon at top right
209 Design a network service
210 ------------------------
212 The following section design a network service. The prerequisite is that the tested VF package is available.
214 - Log into ONAP portal with designer role (cs0008)
216 - Select SDC from the application
220 - Hoover over the Add icon and select add service
222 - Specify the name of the network service <nsName> (ex. ns_simple_20180526_1)
224 - Specify 123456 ad project code
226 - Specify description
228 - Select Network Service for the category
230 - If the network service is missing from the list
232 - Log in as demo user and select SDC
236 - Click on Composition at left
238 - Search for the created VF using the search box at top left <vnfPackageName>
240 - Drag the VF icon to middle
242 - Wait for the icon to appear at the middle (only drag once)
244 - Click on the icon on the middle
246 - Click on very small pencil icon at top right
248 - Specify the name of the VF
252 - Search for the created NS using the search box at top right <nsName>
254 - Click on the NS icon
256 - Click on Submit for testing
258 - Log out using the small person icon at top right
260 - Log in with tester role (jm0007)
262 - Select SDC from the application
264 - Search for the created VNF using the search box at top right <vnfPackageName>
266 - Click on Start testing
270 - Log out using the small person icon at top right
272 - Log in with tester role (gv0001)
274 - Select SDC from the application
276 - Search for the created VNF using the search box at top right <vnfPackageName>
278 - Click on Approve on top right
280 - Log out using the small person icon at top right
282 - Log in with operation role (op0001)
284 - Select SDC from the application
286 - Search for the created VNF using the search box at top right <vnfPackageName>
288 - Click on Distribute on top right
290 - Click on monitor in an order to verify that the distribution was successful
292 - Click on the small arrow next to the Distribution ID
294 - The list should contain at least two lines staring with sdc and aai-ml
296 - If the list does not contain enough elements it can be refreshed with the small icon at middle right
298 - Each of the two lines should contain a green check sign next to Deployed
300 - Log out using the small person icon at top right
304 Design a VF for the E2E service
305 -------------------------------
307 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
308 a wrapper to be able to treat the created NS as a VF. The prerequisite of this step is that the network service was
309 successfully distributed.
311 - Determine the UUIDs of the created NS in previous step
313 - 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
317 - Set the following values in the Header of the request:
321 - X-ECOMP-InstanceID: VFC
323 - Accept: application/json
325 - Search for the created service by name <nsName> and note the uuid and invariantUUID fields
327 - Log in with designer role (cs0008)
329 - Select SDC from the application
333 - Hoover over the Add icon and select add VF
335 - Specify the name of the VF <vfForNsName> (ex. vf_for_ns_simple_20180526_1_vIMS)
337 - the name must contain the vIMS character sequence (even if this is not an IMS)
339 - Specify something for the Vendor
341 - Specify any numeric value for the Vendor Release
343 - Specify something for description
345 - Select Network Service for the category
347 - Click on Create on top right
349 - Click on Composition at left
351 - Search for the NSD using the search box at top left
353 - Drag the NSD icon to middle
355 - Wait for the icon to appear at the middle (only drag once)
357 - Click on the icon on the middle
359 - Click on very small pencil icon at top right
361 - Specify the name of the NSD (ex. firstNsd ) <nsdName>
363 - Click on the name of the VF next to HOME at top
365 - Select Properties Assignment
367 - Select the check box before providing_service_uuid and providing_service_invariant_uuid properties
369 - Click on Declare at right
371 - Click on Inputs at middle
373 - Specify the UUID of the service (that was determined in previous step) for the <nsdName>_providing_service_uuid property
375 - Specify the invariant UUID of the service (that was determined in previous step) for the <nsdName>_providing_service_invariant_uuid property
381 - Search for the created VF using the search box at top right <vfForNsName>
383 - Click on the VF icon
385 - Click on Submit for testing
387 - Log out using the small person icon at top right
389 - Log in with tester role (jm0007)
391 - Select SDC from the application
393 - Search for the created VNF using the search box at top right <vfForNsName>
395 - Click on Start testing
399 - Log out using the small person icon at top right
405 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
406 wrapping the network service is tested.
408 - Log in with designer role (cs0008)
410 - Select SDC from the application
414 - Hoover over the Add icon and select add Service
416 - Specify the name of the NS <e2eNsName> (ex. e2e_simple_20180526_1)
418 - Specify any numeric value for the Project Code
420 - Specify something for description
422 - Select E2E Service for the category
424 - Click on Create on top right
426 - Click on Composition at left
428 - Search for the created VF using the search box at top left <vfForNsName>
430 - Drag the VF icon to middle
432 - Wait for the icon to appear at the middle (only drag once)
434 - Click on the name of the NS next to HOME at top
438 - Search for the created NS using the search box at top right <e2eNsName>
440 - Click on the NS icon
442 - Click on Submit for testing
444 - Log out using the small person icon at top right
446 - Log in with tester role (jm0007)
448 - Select SDC from the application
450 - Search for the created NS using the search box at top right <e2eNsName>
452 - Click on Start testing
456 - Log out using the small person icon at top right
458 - Log in with tester role (gv0001)
460 - Select SDC from the application
462 - Search for the created VNF using the search box at top right <e2eNsName>
464 - Click on Approve on top right
466 - Log out using the small person icon at top right
468 - Log in with operation role (op0001)
470 - Select SDC from the application
472 - Search for the created VNF using the search box at top right <e2eNsName>
474 - Click on Distribute on top right
476 - Click on monitor in an order to verify that the distribution was successful
478 - Click on the small arrow next to the Distribution ID
480 - The list should contain at least two lines staring with sdc and aai-ml
482 - If the list does not contain enough elements it can be refreshed with the small icon at middle right
484 - Each of the two lines should contain a green check sign next to Deployed
486 - Log out using the small person icon at top right