...
- ETSI Alignment
- ETSI Network Service for 5G Network Slicing Fernando Oliveira
ETSI Network Service for 5G Network Slicing - R8 E2E Network Slicing case modeling work guochuyi
Modeling enhancements in Honolulu
Modeling enhancements
Minutes
- Agenda Bashing
- postpone second topic ETSI Network Service for 5G Network Slicing to discuss at next week's DTF
- AAI instance model in Guilin for E2E Network Slicing case A&AI Instance Modeling in Guilin
- ETSI Alignment
Discussion relates to how SDC package supporting CNF, the usage of helm chart, impact on internal model, and how SO workflow supports.- CNF helm chart has the deployment related information. The question is, when onboarding package with helm chart, is SDC going to generate an internal VNFD automatically with the helm chart to be used by SO? For CNF, they may be different onboarding process, so can't be called VNFD, there has equivalent process for generate corresponding internal model. In ONAP, the solution is heat-based, and the whole solution, especially the helm chart, needs more discussion with SO team.
- As for ETSI contribution, it may need further thinking if helm charts can instead of some TOSCA form in SOL 004.
- Plan to call for approval for current IM proposal in H release.
- ETSI Network Service for 5G Network Slicing (Postpone)
- R8 E2E Network Slicing case modeling work (No comments or questions received)
- AAI instance model in Guilin for E2E Network Slicing case
- Allotted resource in AAI instance model has 2 kinds of usage situation, one is for service profile instance and NSI relationship, one representes TransportSliceNetwork of IETF model.
- Chuyi's understanding of Nodes in IETF model is for transport logical nodes, like UNI ports in ONAP, and can be mapped to physical ports of transport network, however, Guilin release doesn't import nodes into ONAP.
- some attributes in service/slice profile will be found at service/slice profile service instance, for example, value of sst is written in attribute serviceType
...