Page Comparison

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 April 2020 (https://wiki.lfnetworking.org/display/LN/2020+April+Technical+Event+Schedule)

The best understanding of the design time model is reported below :DESIGN TIME MODEL

NOTEs:

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

...

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 Modified

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

Additional Reference Material :

Design Service Templates

RUN TIME MODEL

Image Added

Additional Reference Material: 

Rel 6:

1) A&AI Impacts

----

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

...