Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

CNF Taskforce Meeting Minutes

...

1.1.1 Evolving from VNFs to CNFs

1.1.2 ONAP as a CNFO

  • Hybrid services CNF/VNF/PNF, leveraging open-source
    and standards
    • Support Greenfield and Brownfield environment
    • E.g., CNF on bare-metal, CNF on VM, VNF on VM, PNF
  • Day 0/1/2 configuration
    • Not just infrastructure orchestration
    • Configuration and Update
  • Standard alignment (ETSI, 3GPP) and beyond (ASD)
    • Evolve existing investment, no need to start from scratch
    • Common Infrastructure for model/package onboarding, design and distribution
    • Support both ETSI-Aligned and Cloud Native Orchestration
    • 5G slicing use case – 3GPP compliant


Image Modified

1.2 ONAP as a Cloud Native application

...

  • documentation
  • Jira items in progress for the current release

4.2 Demos

5. FAQ

Q: What is the value-add of ONAP for CNF orchestration (CNFO)? What does it provide on top of K8S?

...

  • Call for developers to implement in Jakarta new features:
    • CNF Control Loop 
    • Integration with XGVela
    • Merging Native Helm/ETSI flows
    • Entreprise use cases
    • etc
  • Istanbul CNF Orchestrator Requirements:  REQ-627 - ONAP CNF orchestration - Istanbul Enhancements DONE
  • Those are the short term goals. Have a great deal more in the backlog for future released. refer to 2021-06-09 - ONAP TSC Taskforce: Cloud Native (Roadmap)

...