Page Comparison

...

1. Network Slicing model proposal
   1. Basic introduction
      Chuyi: In R6, we focus on how to model NSMF and NSSMF in ONAP, take CSMF as a stretch goal. Then there will be 4 layers (Slicing Communication Service,  Network Slicing Service, Network Slicing Subnet, Network Service) of Slicing service model, SDC supports 4 of them, SO consumes 3 of them.
   2. Mapping
      Andy:  Slicing Communication Service is a composite service, we need an example to show what kind of attributes will hold in Slicing Communication Service layer and Network Slicing Service layer, and how to handle mappings between multiple layers.
      BorislaveBorislav: SDC is doing the mapping job in R6, then you only need to provide one input for the properties, it can be connected to different layers. You can give the values to each layer of models or receive the value after instantiation as an output or the configuration activity. ONAP is supposed to leave this decision to the designers and anyone can add its needs.  
      Xu: Slicing Communication Service and Network Slicing Service don't define topology for detailed resources, it is what NSSMF cares more about, SO needs to do 2 things: mapping and instantiation, if we use VFC to do NSSMF, then VFC handles NSSMF with Network Service.
   3. End-to-end slicing management
      When considerking considering this structure, how to deal with PNF/Network service inside if it is shared across use cases?
      Suggest to build model considering to support across use cases, think about how to combine them and how they will affect each other, Chuyi will add this dedicated topic in the wiki page. We should have a common model structure to be used by all the cases, not only the slicing service, current proposal need to be generalized.
2. DynamicParameter
   1. New upated part will be discussed after updating the wiki page.

...