You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Topic Leader(s)

Topic Overview

This session will be an interactive one. The leaders of this activity will provide a quick recap of the work done so far, and then open the floor for questions and suggestions. The Taskforce is very much interested in the priorities of the community with regards for making ONAP orchestrate Cloud Native network functions. Anyone who is interested Cloud Native Network Functions (CNF) is welcome to join this session and share their thoughts on this subject.

Slides & Recording

Agenda

Awesome presentation

Minutes

  • Live demonstration of our CNF Orchestrator based on ONAP Service Orchestrator (SO):
    • Onboarding of CNF package via ONAP Service Design & Creation (SDC)
    • Update/Configuration Helm Package
  • Presentation of SDC (Onboarding/Design) ETSI Alignment Enhancements (SOL004/SOL007), package distribution for CNF, Alignment with CNF/O-RAN O2, SO NFVO (SOL003)- Adapter refactoring
  • Clarifications about K8s Orchestrator and ONAP Orchestrator added-value


Q&A

  • @Seshu, We used to have SDC Client in Multi-Cloud project to get notified whenever NS/VNF package is onboarded in SDC, and if it is Helm related NS/VNF package, then it used to upload that in "Multi Cloud K8s plugin". With the CNF adapter in SO, is that SDC Client still required?
    Srini Addepalli (Intel) to Everyone (5:39 AM)
  • @Seshu, Second question: Does CNF adapter call Multicloud-k8s APIs directly or the flow is still via Multi Cloud APIs & Multi Cloud broker?
    SaiSeshu MUDIGANTI (Huawei) to Everyone (5:39 AM)
  • Yes Srini, the notification is still there in place as of Guilin to keep the backward compatibility
  • @Srini, we make the direct API call
    its not through MC
    we intent to extend it further it to the V2 API in future

Action Items

  • No labels