...
- R8 Service Modeling Requirements
ONAP R8 Modeling High Level Requirements - CNF Modeling
ETSI IFA011 v3.3.1 & v4.1.1 Changes to support OsContainer based VNFs - ETSI NSD IM Update
ETSI IFA014 v2.7.1 NetworkServiceDescriptor integration into ONAP IM - Allotted Resource relationship in Network Slicing
Allotted Resource for Network Slicing
...
- Agenda Bashing
- R8 Service Modeling Requirements
- Suggestion from Michela to add an new item for NSD work.
- Jacqueline Beaulac will check with Ben why CPS model belongs to Service IM domain, what works will be needed at service level.
- CNF Modeling \\ETSI alignment
- There will have an ETSI alignment meeting next Monday to disuss related modeling aspect, time is 1 hour before Resource IM call.
- E2E Network Slicing case will also contain a CNF based solution in H release.
- The impact related to service level is: CNF information has been merged into VNF part, the VNFD, VL and etc. should can be viewed at service level. v 4.1.1 has container based functionalities, details can be found at ETSI IFA011 v3.3.1 & v4.1.1 Changes to support OsContainer based VNFs. Another is the introduction of virtual cpd, container model generally mapps to k8s service, vcpd is a mapping function between k8s service and external cpd in Network Service.Vcpd impacts SDN-C, and may impact the AAI service model. The major work now is how to do onboarding VNFD and ONAP AID modeling mapping that carries container work.
- Suggest to have unified DM in SDC, and onboard 1 kind of package.
- NSD \\ how to differentiate VNF or CNF based in NSD by SO/NFVO?
- 1 question still open to SDC is
- is, should the NSD be shown as a single NS template or as a ONAP Service template. It tends to always be ONAP service and then refers to a NS. The relationship would be complex when having nested NS scenio, this bring chanlleges for SO implementation, these questions need more discussion.
- Allotted Resource relationship in Network Slicing
- Anfd relationship updatePostpone to next meeting to make a decision.