DRAFT VERSION
...
Initial POC/Guilin Requirements (excluding ONAP Tooling i.e. VVP/VNFSDK/VTP tracked under WS03-Labs and Tooling)
#1
...
Initial experimentations with basic CNF(s) in order to validate onboarding, instantiation of multiple CNFs, monitoring processes Bin Yang, Srinivasa Addepalli , Lukasz Rajewski, Seshu Kumar Mudiganti
Presentation during LFN Event - Day 2 April 22nd, 2020 - 2.30pm UTC: CNF Task Force - CNF Orchestration based on CNTT Requirements
cFW POC (in progress)
In Dublin (4th ONAP Release), we showcased deploying CNFs & VNFs (firewall use case) and normal applications on the same cluster from ONAP.
Also, Akraino ICN project is bundling ONAP4K8s.
In Frankfurt (6th ONAP Release), the vFW CNF CDS use case shows how to instantiate multiple CNF instances similar way as VNFs bringing CNFs closer to first class citizens in ONAP.
In Guilin (7th ONAP Release), Service Orchetrator will be enhanced in order to support CNFs
Additional links:
#2 ETSI CNF path Fernando Oliveira , Byung-Woo Jun
#3 Service Orchestrator Enhancements to support CNFs Seshu Kumar Mudiganti
...
#3 ONAP Cloud Native Security Krzysztof Opasiak , Sylvain Desbureaux
Additional presentation during LFN Event - Day 2 April 22nd, 2020 - 1.30pm UTC: Service Mesh analysis as alternative for part of ONAP AAF (policy enforcement)
