Versions Compared

Old Version 3

changes.mady.by.user Michela Bevilacqua

Saved on

compared with

New Version 4

changes.mady.by.user Michela Bevilacqua

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


The scope of this page is to explore the use of the Allotted Resource model at Design Time and Run Time in the context of the Network Slicing. 

This analysis is based on a Presentation, User Operation Guidance for E2E Network Slicing Use case, from LIN MENG,  Swaminathan S,  Chuanyu Chen shared during the latest LFNetworking virtual Event in Aprile 2020 (https://wiki.lfnetworking.org/display/LN/2020+April+Technical+Event+Schedule)


The best understanding of the design time model today is reported below :


NOTEs:

1) CST chain of objects and NST chain do not have any relation at DT. 

  • Alloted resource is used to tell express the relationship open relations that will shall be defined closed at Run Time. The NST will be selected at runtime. 

2) The VF:NSTAR is defined as an VF of categoy allotted Resource (see step 3) and it is composed by the Allotted Resource v1.0 template. 

Allotted Resource v1.0 is a default template already present in ONAP SDC, it is NOT an object created by a user.

3) Analyzing the ServiceProfile TOSCA descriptor, allottedresource_providing_service_uuid and allottedresource_providing_service_inviariant_uuid are defined as input parameters. 

The operator at, service instantiation time needs to provide the type of service (the service type uuids)  is expected to be associated to the CST and Service Profile service 


Image Added


Image Added

4) Analyzing the node template and node types defined in the TOSCA descriptors   

  • Allotted Resource 0 is of type org.openecomp.resource.vfc.AllottedResource,
    • used for substitution mapping of org.openecomp.resource.vf.Nstar
    • org.openecomp.resource.vfc.AllottedResource derived from org.openecomp.tosca.nodes.Root
  • NSTAR 0 is of type resource.vf.NStar,
    • used for substitution mapping of org.openecomp.service.ServiceProfile

    • org.openecomp.resource.vf.Nstar derived from org.openecomp.resource.abstract.nodes.VF

    • service.ServiceProfile is derived from resource.abstract.nodes.services








----

Only relevant slides for the modeling discussion have been capture in the next pages.

...

Answer: Providing_service_invariant_uuid and providing_service_uuid are declared input paramenters in SDC but NOT filled in at DT, which will be filled in the runtime with the selected NST service invariant id and service id.

...