...

2022-03-15

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).
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. not done this time.
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   2. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   3. RIC-835 → 2021-12-07 news from Viktor
   4. RIC-837 RMR is not forwarding messages from E2T to E2M
   5. RIC-840 Unable to deploy E2Term on Dawn release
   6. 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.
   7. fixed: no new fixes since last meeting.
   8. 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.
   2. Sangeetha working on RIC-860, done, but code still to be checked in.
      
   3. Sangeetha working on RIC-878, status see Jira item
      
   4. Subhash asked for documentation of nanobot from Sunil.
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-01-27 (Mail sent)
      
   2. 2022-02-15: resending with the right David
      
   3. 2022-03-01: workshop to be planned (James in discussion with David)
   4. in last weeks SMO+RSAC meeting this was discussed as well. It would be good to have a test case that just verifies successful deployment of teh RIC platform, workshop still to be scheduled.
   5. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
6. Progress on E2APv2.0?
   1. in ric platform and simulators?
      1. Any first code/design review request that Arun and Dhiraj should review?
      2. progress, subhash: simulator adapted. E2T changes internally ready.
      3. Subhash&co did not plan to do any testing on xApp side.
      4. thoralf to sent invitation to Subhash &co for Friday → DONE
         
         1. agreed on configuration transfer to be handled similar to function definitions as E2APv2.0 now defines configuration updates as replacing instead of updating existing component configuration entries.
         2. E2 reset to be handled as new state that xApps see: "connected---transition1-->connected-but-under-reset---transition2-->connected". We use a timer, instead of strict xapp and submgr confirmation that all has been cleaned up. xApps shall resubscribe only after transition2. xapps can assume that submgr has removed all subscriptions (in its view of the world) and that the E2 node has removed them (in its view of the world)
         3. Subhash will send slideset for this during this week
         4. E2 implementation status?
   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.
            
         2. in same mail thread there's another issue - to be discussed over mail.
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
   3. in DU
      1. 2022-02-23 user-30c9d reported in TOC that this work is done.
7. anybody working on this RIC-705 Alexandre wants to know.
   1. 2022-02-15: Thoralf sent mail to E & A.
   2. 2022-02-21: Alexandre agree to work on RIC-705. Might also later work on RIC-641. To keep track of things, I (Thoralf) took the liberty to give Alexandre a separate subteam tag in Jira: “subteam-utfpr” and marked RIC-705 as per the convention. I updated the links in §7.2 accordingly in Jira usage conventions.
8. RICAPP agenda: RICAPP Meetings.

2022-03-01

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. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7610 OK
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7587 OK redis client from v7 to v8 and adapting to changes in interface.
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. not done this time.
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   2. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   3. RIC-835 → 2021-12-07 news from Viktor
   4. RIC-837 RMR is not forwarding messages from E2T to E2M
   5. RIC-840 Unable to deploy E2Term on Dawn release
   6. 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.
   7. fixed: no new fixes since last meeting.
   8. anybody would like to get more familiar with RMR?
4. Cross-check with A. if he has updated the instructions to point to helm3.
   1. A. can look on this on Jan-31 and update here: new section here - https://docs.o-ran-sc.org/projects/o-ran-sc-it-dep/en/latest/installation-guides.html
   2. 2022-02-14: there's a review for this documentation change (change 7638). The review fails in LF CI/Jenkins in SMO/non-rt RIC related parts. Asked help from James by e-mail. James raised a request to LF: IT-23628
   3. 2022-02-16: merged and DONE.
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.
   2. Sangeetha working on RIC-860, done, but code still to be checked in.
      
   3. Sangeetha working on RIC-878, status see Jira item
      
   4. Subhash asked for documentation of nanobot from Sunil.
6. 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-01-27 (Mail sent)
      
   2. 2022-02-15: resending with the right David
      
   3. 2022-03-01: workshop to be planned (James in discussion with David)
   4. in last weeks SMO+RSAC meeting this was discussed as well. It would be good to have a test case that just verifies successful deployment of teh RIC platform, workshop still to be scheduled.
   5. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
7. Progress on E2APv2.0?
   1. in ric platform and simulators?
      1. Any first code/design review request that Arun and Dhiraj should review?
      2. progress, subhash: simulator adapted. E2T changes internally ready.
      3. Subhash&co did not plan to do any testing on xApp side.
      4. thoralf to sent invitation to Subhash &co for Friday → DONE
         
         1. agreed on configuration transfer to be handled similar to function definitions as E2APv2.0 now defines configuration updates as replacing instead of updating existing component configuration entries.
         2. E2 reset to be handled as new state that xApps see: "connected---transition1-->connected-but-under-reset---transition2-->connected". We use a timer, instead of strict xapp and submgr confirmation that all has been cleaned up. xApps shall resubscribe only after transition2. xapps can assume that submgr has removed all subscriptions (in its view of the world) and that the E2 node has removed them (in its view of the world)
         3. Subhash will send slideset for this during this week
   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.
            
         2. in same mail thread there's another issue - to be discussed over mail.
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
   3. in DU
      1. 2022-02-23 user-30c9d reported in TOC that this work is done.
8. anybody working on this RIC-705 Alexandre wants to know.
   1. 2022-02-15: Thoralf sent mail to E & A.
   2. 2022-02-21: Alexandre agree to work on RIC-705. Might also later work on RIC-641. To keep track of things, I (Thoralf) took the liberty to give Alexandre a separate subteam tag in Jira: “subteam-utfpr” and marked RIC-705 as per the convention. I updated the links in §7.2 accordingly in Jira usage conventions.
9. RICAPP agenda: RICAPP Meetings.

...