Versions Compared

Key

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

...

#2 Have an adapter for the magma in ONAP Service Orchestrator and use it as a resource orchestrator for the specific jobs.      DisadvantageDisadvantage: create something specific

...

  • Feedback from Swaminathan Seetharaman about future scope/functionalities/roadmap supported by CSMF (Communication Communication Service Management Function)

With ref. to the roadmap for CSMF, there is nothing planned for Istanbul release. Anything beyond it will depend on the interest from use case contributors and/or community.

...

#2 Having different service priorities, e.g., resulting in pre-emption (when needed) during service fulfilment and during operation, for services having a higher priority


  • Integration with Magma Controller/GW

#1 Can we conclude Magma is an IMS.#2 Review the 4 ONAP/Magma action items identified on 4/14/2021 - Feedback from Amar Kapadia, Prabhjot Singh Sethi (prabhjot@aarnanetworks.com)
       
Magma Controller REST Interface - magma | 1.0.0 | karthiksubraveti | SwaggerHub

        Magma Controller = orc8R = magma/orc8r at master · magma/magma · GitHub

        Doc web site: Introduction · Magma Documentation

        There is no Magma GW documentation at this stage

Magma GW = to be considered as CNF (by June 2021); currently available as PNF/VNF

Magma Controller= CNF


#2 Currently the goal is to interact with the Magma Controller as a first step directly.

     As part of the roadmap, we should also investigate if there is a way to interact directly with the Magma GW (reduce 1 overhead layer between Magma/ONAP)

     Additional information are required about Magma Controller to finalize the right architecture.


#3 Currently the scaling of GW is manual (sad)  and triggered by the user.

     Magma Controller is also manual so both (Controller/Magma) can be orchestrated via ONAP

     Opportunity for ONAP  to automate the scaling of Magma GW (Control Loop)


#3 Can we conclude Magma is an EMS? YES#3 Deep Dive Magma/ONAP ITFs to determine what need to be implemented on top of what has been developed in ONAP

#4 5G Blueprint based on Guilin/Honolulu? Magma release is scheduled by June 2021 therefore let's consider ONAP Honolulu release

#6 Is there any Security Magma requirement? based on HTTPS, Mesh? Not yet available.

     Currently used DockerCompose, next step will be used Helm v3.0.

#7 Any information about Magma packaging, modeling requirement?

Recommendations: TOSCA descriptor pointing to HELM (in alignment with ETSI specs)


  • Byung-Woo Jun  - Next on ONAP CNF Task Force - every Thursday at 1pm UTC
    • Initial analysis about Magma integration will be shared on CNF Task force on April 29th, 2021
    • CNF packaging/modeling recommendations on May 6th, 2021 

Meeting Minutes - 5/12/2021 @7am PST 

  • Amar KapadiaPrabhjot Singh Sethi, Byung-Woo Jun will team up and present potential alternatives to onboard Magma Controller based on SDN-C (TBC)
  • Amar Kapadia  - Provide additional information about Magma Security requirements

Action Items (In Progress)

...