Versions Compared

Key

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

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Meeting Minutes 

Table of Contents
maxLevel2

...

  • Review our Calendar - Decision to setup CNF Task Force call every Tuesday at 2pm UTC until Daylight saving time will end in March
  • Review (and refine if necessary) this taskforce goals. Other than the on-going work, what is the next big thing we want to tackle as a taskforce?

...

  • Continue discussion between Aarna and SO team to figure out if some of the Aarna work can be re-used by SO
  • Any topic we want to submit for the February DDF event?
    • What will be ONAP priorities to remain in alignment with Industry/Standards?
    • What would be our ONAP 2021 CNF Task Force priorities (after Honolulu) - brainstorming?
    • Video Guilin CNF?
    • CNF Task Force Office Hours

...

...

April 8th, 2021 at 1pm UTC

...

...

    • The Honolulu release has important updates to support cloud native network functions (CNF). The functionality includes configuration of Helm based CNFs and seamless day 1, 2 operations. The Configuration API allows a user to create, modify and delete Kubernetes (K8s) resource templates and their base parameters and the Profile API allows for sophisticated day 0 configuration. The Query API gathers filtered status of the CNF and the HealthCheck API executes dedicated health check jobs to verify the status of a CNF. This new functionality is implemented in the Controller Design Studio (CDS) component using dedicated templates called Controller Blueprint Archives (CBA). 

    • DCAE simplifies microservice deployment via Helm charts and includes a new KPI microservice. The VES-OpenAPI-Manager allows easier validation of new xNF types against supported VES StndDefined domain improving compliance with 3GPP and O-RAN
    • Application Programming Interface (APIs) 

    • Logs are redirected to SDTOUT
    • ONAP Components are containerized and are deployed on virtual, shared and elastic infrastructure.
    • Built based on DevOps Toolchain (CI/CD, Gating, etc.)

Additional separated key messaging: Support ORAN SC SMO + Support Enterprise business (E2E Network Slicing, etc.)

...

June 24th, 2021 at 1pm UTC

...

...

...