...

...

2023-01-31 (Tuesday)

Integration with AI/ML project: Kserve adapter (mentioned in RSAC), xApp integration, AI/ML performance monitoring (from e-mail)?

Mark your affiliation in https://openprofile.dev  so that statistics are correctly generated.

...

2023-01-

...

17 (Tuesday)

Recording: link to zoom recording

1. 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. Last checked on  Dec-15
      
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
2. 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. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-940 sdlpy missing whitespace → Timo
   2. RIC-939 race conditions in RMR → Abdulwahid
   3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   4. RIC-915 dms_cli for installing xapp not working (raised by James)
   5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   7. RIC-897 SCTP connection fails with Viavi // update with workaround
   8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   9. RIC-894 long idle period (days) causes RMR connection breaks
   10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
       1. 2021-12-21: Trying to get bandwidth for this during F release.
   13. RIC-837 RMR is not forwarding messages from E2T to E2M
   14. RIC-835 → 2021-12-07 news from Viktor
   15. fixed: no new fixes
       
   16. anybody would like to get more familiar with RMR?

4. 2022-12-13, 2023-01-17: Bin Yang asked about O2 for RIC platform deployment and xapp deployment. Need to discuss on this topic. O-cloud is deployed in AT&T and Taiwan lab.

   1. The current platform deployment scripts might not be in line with O2 envisions
   2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
   3. O2-D(MS) is relevant to RIC platform.
   4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Coudl be implemented as second option for deploying xApps.
5. Sunil still to discuss with other team members for other items from subteam-h
   1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
      1. RIC-860 + RIC-878
         
         1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
         2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in
         3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
         4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
         5. 2022-04-26: still open
         6. 2022-05-11: expecting to finalize by May-27
         7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
         8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
         9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
         10. 2022-08-02: SUNIL SINGH to check any news on RIC-860 or RIC-878?
         11. 2022-08-16→2022-08-30->2022-09-13→2022-09-27: no update
         12. : some cleanup is needed first.
             
             1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
             2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
             3. test both if they are actually working
             4. 2022-08-30: team currently busy, but will pick up on this again soon
         13. 2023-01-17: for now remove form agenda and take back if we find someone to work on it.
      2. RIC-641 + RIC-705
         1. RIC-641: done in G
         2. RIC-705: xapp registration still open (for H?) → manage this via H content and don't keep it in the agenda.
6. contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
   1. created on 2022-08-30: Update 2022-09-13 → 2022-09-27: Now hanging with Augu. - waiting for reply
   2. 2023-01-17: no news → we drop this item from the agenda
      
7. James:
   1. 2022-11-08: continues work with keysight (using KPI-mon-go xApp (E2APv1, and older E2SM). hw-go could be used if E2AP2.0 is needed. hw-go does not parse E2SM-parts.
      1. HCL also working on E2APv2.0 xApps.
   2. 2023-01-17: work with keysight completed before thanksgiving weekend (excl. xapp; focus on base E2AP cases). No need to keep this in the agenda.
      
8. H release content
   
   1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
   2. Sprint dates
      1. Sprint H release dev sprint 1: Feb-20´to Mar-12
      2. Sprint H release dev sprint 2: Mar-13 to Apr-2
      3. Sprint H release dev sprint 3: Apr-3 to Apr-23
      4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
      5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
   3. Please prepare for next meeting a rough view on what you might want to work on. Also as input use delayed items from previous release link
9. GRPC vs RMR
   1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
   2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
   3. need to look at Mavenir E2SM-RC proposal.
   4. impact on xapp frameworks will happen as well.
   5. Alexandre mentioned option of using QUIC (grpc over QUIC).
   6. Thoralf to schedule a meeting once a proposal is ready.
   7. 2022-08-16 →2022-08-30 → 2022-09-27 → 2022-10-11: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
   8. 2022-11-08: focus of Nokia proposal will be on scalability (xApps, #E2 connections)
   9. 2022-11-22: WG3 spec for RICAPI available in current train. Worth reading. Defines GRPC, but also SCTP+Protobuf interfaces.
   10. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
10. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2023-01-17: not discussed today.
11. RICAPP agenda: RICAPP Meetings.

...

2023-01-03 (Tuesday)

Recording: Link to zoom recording

...