Versions Compared

Key

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

...

  1. Anybody new who wants to introduce him/herself?
  2. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7017 ok
    2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7074 ok
    3. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7088 ok
    4. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/7087 ok
    5. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7103 ok
  3. every second time: Review code coverage stats and blocker code smells
      1. We take a look at the two links in the beginning of this page: Code coverage reports..
      2. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    ...
    1. Anybody willing to work on them?
  4. Every time: Check if there are new bug reports in JIRA: link
  5. Action items
    1. SCCL update - Matti will check with Tracy
      1. still discussion within O-RAN-SC still ongoing
      2. publication of O-RAN specs of July train should happen any time now.
    2. E2 simulator seeing E2 setups not passing through: Wiki page updated but no word from Nokia - trying 100 subscriptions - testing still in progress, will check with Amit if bug has been filed (nokia waiting for test case being run in newer cloud environment). Amit raised RIC-852 for this.
    3. James (INT PTL): Sent email to PTLs on what is needed. Need automation of testing for all projects.
      1. Any comments?
      2. VES alarm events, for example (James)
      3. James: non-rt RIC - near-RT RIC integration A1. Discuss With Sunil/Matti/James, e.g. TS xApps has disabled code for this.
      4. A1-EI could also be integrated (Subhash raised this)
      5. Ramesh - resue E2 simulator
      6. TODO thoralf to start mail thread on this.
  6. Expected that we stop development end of November. In Dec-7 meeting we will do status check and after this only exceptional (specially managed) commits to near-RT RIC for the rest of December.
  7. Subhash (sent this before the meeting)
    1. E2AP v1.1 support [RIC-640 and RIC-638] : We are working on implementation of RIC-640 and RIC-638. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/6931 https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/7041 https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/7050

    2. A1 mediator (Could be moved to F release) (RIC-647): partial implementation is done to support A1-P API which is not enabled yet.

    3. RICDMS (Could be moved to F release) [RIC-714] : Implementation is not yet started only we have finalized the API.

    4. RICCTL (Could be moved to F release) [RIC-445] : Pushed some sample commands for A1-P related operations. We are discussing with our internal team to use code from ONAP community which is taking little time.

  8. Preliminary planning for the F release
    1. likely not completed in E release (spill over into F): RIC-647, and all from this list.
    2. Candidate list for F release (priority column as per Thoralf's best understanding) https://jira.o-ran-sc.org/issues/?jql=(fixVersion%20in%20(ZZZ_future)%20or%20fixVersion%20in%20(F)%20)AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20%20ORDER%20BY%20component%20ASC
    3. we will discuss this again in two weeks from now.
  9. Do we update to golang 1.16 (in go.mod) in all repos? Juha now updated golang version in Ubuntu base image along with Ubuntu image update to 20.04.
    1. A1-Med is using 1.16; others need to be checked
  10. RICAPP agenda: RICAPP Meetings.

...