...
- Ref: to last 2 meetings.
- Ref: Friday meeting Minutes & Recording from last week : https://wiki.onap.org/display/Meetings/2021-06-25+Meeting+notes)
INFO provided by from Christophe - 2021-06-30: (Presented by Martial)
Just a few notes:
- We have agreed with ONAP and other members of O-RAN SC to keep an ad-hoc call on Friday to discuss technical details for now (will remove this meeting once all details are sorted out and use the joint meeting to report status)
- Main comment from John is that we cannot consider an SMO deployment without having a way to deploy Non-RT-RIC as well as ONAP components (hence a debate on how this should materialize : extend OOM? )
- We have progressed on the POC in the meanwhile, Sebastien had an idea and has pushed a small repository on github to show what we are doing for now to create a unique installation for O-RAN, trying to implement the following idea:
- Started from IT/DEP repo, containing some Helm charts for ORAN (including Non-RT-RIC)
- Seems an embryo of using ONAP charts to deploy SMO components but sounded like a fork of ONAP charts
- Instead of copy pasting OOM charts, he create a git submodule referring to oom ONAP charts repo (to keep ONAP untouched)
- Rework the ORAN charts to map them to the OOM structure (like OOM'ized O-RAN charts)
- Try and build (created some makefiles, inspired from ONAP) then push them to a single chart repository
- Merged ONAP override and ORAN override to have a single file
- Created an Install script to deploy the charts in a single Namespace
- … it worked more or less
We plan to show that maybe on Friday call
- Initial (private) Github repo to have info from both ONAP & OSC - testing this approach.
- Copies & modifies scripts from OOM and OSC for now. (Git submodule)
- Will share link at Friday meeting
- Will probably move to ONAP OOM eventually
- No focus yet on CNFs etc yet.
- Relationship with ONAP CNFs & O2 is not clear yet.
After the Call: ONAP Release progress (David McBride )
- ONAP Intanbul M2 passed in ONAP TSC.