Primary ONAP Contacts: Catherine Lefevre Amar Kapadia Seshu Kumar Mudiganti Ranny Haiby Srinivasa AddepalliFernando Oliveira Byung-Woo Jun Lukasz Rajewski Kanagaraj Manickam
1. Describe the Information Element in words
2.Define the properties (e.g., attributes, known relationships, etc.)
3.Where does this information come from? (i.e. originator)
4.Who uses this information inside & outside of ONAP? (i.e. consumers) and how do they use it?
5.Who updates this information inside & outside of ONAP? (i.e. producers)
6.Where will this information stored and maintained in ONAP? (i.e. steward)
7.Perform UML Modeling (including mapping to existing concepts)
8.Prioritization for ONAP Releases
9.Identify impacted ONAP schemas & APIs, Are there existing schemas be used or extended?
10.Develop implementation schema (identify component impacts on schema changes)
Presentation during LFN Event - Day 2 April 22nd, 2020 - 2.30pm UTC: CNF Task Force - CNF Orchestration based on CNTT Requirements
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 is submitting a proposal to enhance their application to support CNFs.
Additional links:
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)