Meeting Info

RIC project meetings are open to the public and held on Tuesdays at 2pm UTC (winter) and 1pm UTC (summer).  World Time Zone Map

Zoom 1 Info:

• Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/9644759813
• Meeting ID for dial-in: 9644759813

2022-05-11 (exceptionally Wednesday)

Recording: TODO

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. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/8127 ok
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/stslgo/+/8112 ok
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8136 ok
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/8147 ok - as only files only moved from other repo
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8196 ok
   6. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8215 ok
   7. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8218 ok
   8. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7592 ok
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. We did not do this today.
      
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   2. RIC-903 new (from PW) DefaultUser setup fails when authentication is enabled for InfluxDB. 2022-05-11: fixed
   3. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   4. RIC-897 SCTP connection fails with Viavi // update with workaround
   5. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   6. RIC-894 long idle period (days) causes RMR connection breaks
   7. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail. 2022-05-11: fixed
      
      1. could be staging repo related (10004) vs release repo (10002) for the base image
   8. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   9. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   10. 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.
   11. RIC-837 RMR is not forwarding messages from E2T to E2M
   12. RIC-835 → 2021-12-07 news from Viktor
   13. fixed: RIC-903, RIC-890, RIC-891, RIC-892
       
   14. anybody would like to get more familiar with RMR?
4. 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. Sangeetha working on RIC-860, done, but code still to be checked in.
      2. Sangeetha working on RIC-878, status see Jira item, code still to be 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
5. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
   1. 2022-04-12
      1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
      2. actual workshop planned for RSAC on Apr-21 9am EDT.
      3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
   2. 2022-04-26
      1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
         
      2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
   3. 2022-05-11:
      1. Currently in the hands of OTF team (Alex)
      2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
6. Progress on E2APv2.0?
   1. in ric platform and simulators?
      1. 2022-04-26
         1. subscription manager change for E2APv2.0 is now in E2APv2.0 branch
         2. config update message support coming this week.
         3. after this cleanup of small things here and there that are still needed.
      2. 2022-05-10
         1. thoralf suggests May-13 as day for moving E2AP branch to master
            1. Subhash agrees. So let's aim for that.
            2. Subhash to list which Config transfer failure cases move into next release (just left-over create JIRA item)
         2. Nokia has already tested some E2APv2.0 procedures with Nokia simulator (like E2 setup, subscription success case)
         3. Subhash still working on simulator in sim project
   2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
      1. kpimon
      2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
         1. hw-go issue with old xapp frame lib used. - needs to be updated.
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
         1. done, but not yet open for review.
   3. in DU
      1. 2022-02-23 user-30c9d reported in TOC that this work is done.
7. RIC-641 Sandeep (HCL) is working on this. Work is progressing.
   
   1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
   2. 2022-04-26: working on it
   3. 2022-05-11: news? Could be handled as exception to be worked on during May-15 to Jun-5 so we can still include this into F.
8. F release wrap up
   1. see §6 in Jira usage conventions
   2. Thoralf to go through JIRA and check status of items. Thoralf might send e-mails to get current status.
   3. Thoralf to organize sprint demos for May-24, at 9am ET in an extended timeslot of the project meeting.
      1. See demo page: 2022-05-24 Release F
9. New contribution proposals: Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
   1. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
      1. 2022-04-26:
         1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
         2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
         3. Thoralf to schedule another meeting end of May (after F).
10. Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
11. RICAPP agenda: RICAPP Meetings.

Older meeting minutes

check from here: Project meetings (old)