You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 467 Next »

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:

UTC-timeevery 2nd Tuesday, check from calendar

https://zoom.us/j/9644759813

New York (EDT / UTC-4 during DST (-5 in the winter))every 2nd Tuesday, check from calendar+1 669 900 6833 // +1 646 558 8656 // 855 880 1246 (Toll Free) // 877 369 0926 (Toll Free)
Paris (CEST / UTC+1 in the winter (+2 during DST))every 2nd Tuesday, check from calendar+33 7 5678 4048 // +33 1 8288 0188 // 805 082 588 (Toll Free)
Beijing (CST / UTC+8)every 2nd Tuesday, check from calendar+86 10 87833177 // +86 10 53876330 // 400 616 8835 (Toll Free) // 400 669 9381 (Toll Free)
Tokyo (JST / UTC+9) every 2nd Tuesday, check from calendar+81 524 564 439 // +81 3 4578 1488 // 0 800 100 5040 (Toll Free)
Helsinki  (EEST / UTC+2 in the winter (+3 during DST))every 2nd Tuesday, check from calendar

+358 341092129

Delhi (IST // UTC +5:30every 2nd Tuesday, check from calendarTODO
Other international numbersWorld Time Zone Map

International numbers available: https://zoom.us/u/acyy3hylQi


2022-03-29

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. ...
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail.
    2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    3. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    4. RIC-835 → 2021-12-07 news from Viktor
    5. RIC-837 RMR is not forwarding messages from E2T to E2M
    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. 2022-03-01_
      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.
      4. Subhash asked for documentation of nanobot from Sunil. almost done.
    3. 2022-03-15: status Sangeetha?
  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:
      1. workshop to be planned (James in discussion with David)
      2. 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 the RIC platform, workshop still to be scheduled.
      3. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
      4. 2022-03-15: James creating a E release profile for powder
    4. 2022-03-15: workshop still to be held (was moved by two weeks (Mar-24))
  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 and reviews coming?
      5. 2022-03-15 any news?
        1. do we need an E2APv2.0 branch (submgr used/uses e2ap-v02.00)
          1. if we create a E2 branch now we can do the review in that branch. E2T, E2M, and RNIB. submgr already has branch.
          2. Subhash to ask from Alex Stancu for branch in E2 sim
        2. Already initial versions of the work? Dhiraj and Arun are available for reviewing.
        3. updated design: E2AP 2.0 Design
        4. Could provide initial version in which config handling (IE in E2 Setup) is just ignored.
        5. AP: Subhash to present he E2AP2.0 slides (15min)
        6. A1 mediator work proceeding (two more APIs)
      6. 2022-03-29
        1. smulator code updated to E2Apv2.0: https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/7971
        2. ...
    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.
        3. 2022-03-15: Still open corner case where registration is not done yet, but sub requests are already sent. Thoralf to ask from Nune.
      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.
  8. New contribution proposals
    1. E2 RESET handling
    2. Influx-DB Wrapper
    3. O1-NetConf Enhancements
    4. Stability Issues
  9. RICAPP agenda: RICAPP Meetings.

2022-03-15

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. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7944 OK
    2. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlpy/+/7945 OK
    3. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/7946 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. 2022-03-15: Thoralf went through the list → no updates.
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail.
    2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    3. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    4. RIC-835 → 2021-12-07 news from Viktor
    5. RIC-837 RMR is not forwarding messages from E2T to E2M
    6. RIC-840 Unable to deploy E2Term on Dawn release
    7. 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.
    8. fixed: no new fixes since last meeting. We marked RIC-840 as done because in E it seems to work.
    9. 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. 2022-03-01_
      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.
      4. Subhash asked for documentation of nanobot from Sunil. almost done.
    3. 2022-03-15: status Sangeetha?
  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:
      1. workshop to be planned (James in discussion with David)
      2. 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 the RIC platform, workshop still to be scheduled.
      3. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
      4. 2022-03-15: James creating a E release profile for powder
    4. 2022-03-15: workshop still to be held (was moved by two weeks (Mar-24))
  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 and reviews coming?
      5. 2022-03-15 any news?
        1. do we need an E2APv2.0 branch (submgr used/uses e2ap-v02.00)
          1. if we create a E2 branch now we can do the review in that branch. E2T, E2M, and RNIB. submgr already has branch.
          2. Subhash to ask from Alex Stancu for branch in E2 sim
        2. Already initial versions of the work? Dhiraj and Arun are available for reviewing.
        3. updated design: E2AP 2.0 Design
        4. Could provide initial version in which config handling (IE in E2 Setup) is just ignored.
        5. AP: Subhash to present he E2AP2.0 slides (15min)
        6. A1 mediator work proceeding (two more APIs)
    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.
        3. 2022-03-15: Still open corner case where registration is not done yet, but sub requests are already sent. Thoralf to ask from Nune.
      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. Alexandre started work on RIC-705
  8. RIC-641 Sandeep (HCL) is working on this.
  9. RICAPP agenda: RICAPP Meetings.

2022-03-01

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. 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.

2022-02-15

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. not done this time.
  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. ric-plt/alarm-go 0,0 // no bugs (2021-11-22 → 2022-02-13 )
    4. ric-plt/appmgr 19,3 // 1 major bug (2022-01-30 → 2022-02-13)
    5. ric-plt/e2mgr 88,6 // no bugs (2021-11-18 → 2022-02-14)
    6. ric-plt/lib/rmr 86,2 // no bugs (2021-11-23 → 2022-02-08)
    7. ric-plt/sdlgo 25,2 → 90,2// no bugs (2022-01-31 → 2022-02-14) → RIC-887 fixed reporting job issue
    8. ric-plt/submgr 51,2 // no bugs (2022-01-30 → 2022-02-13)
    9. ric-plt/tracelibcpp 0,0 // 1 major bug (2022-01-25 → 2022-02-08)
    10. ric-plt/tracelibgo 96,2 //0 bugs (2022-01-30 → 2022-02-13)
    11. ric-plt/xapp-frame 0,0 // no bugs (2021-11-22 → 2022-02-13)
    12. ric-plt/xapp-frame-cpp 95,6 // no blocker bugs (2022-01-26 → 2022-02-09)
  3. Every time: Check if there are new bug reports in JIRA: link
    1. new RIC-885, RIC-887 (sdlgo) → fixed
    2. new RIC-883 xappframe-cpp → Alexandre fixed this
    3. RIC-872 → Alexandre fixed this
    4. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    5. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    6. RIC-835 → 2021-12-07 news from Viktor
    7. RIC-837 RMR is not forwarding messages from E2T to E2M
    8. RIC-840 Unable to deploy E2Term on Dawn release
    9. 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.
    10. fixed: RIC-872, RIC-883, RIC-885, RIC-887
    11. 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
  5. Sunil still to discuss with other team members for other items from subteam-h
    1. 2022-02-15 done and clarified
      1. RIC-878 - A1 mediator testing in nanobot
      2. RIC-860 xapp testing nanobot enhancements: wider coverage of functionality, e.g., Subscription deletion
      3. RICAPP-176 adapting bouncer xapp to REST subscription interface.
      4. Other tickets CI/CD and Code coverage tickets, I am still looking for the resources to work on that.
  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
  7. Progress on E2APv2.0?
    1. in ric platform and simulators?
      1. any questions/comments on Arun's slideset in RIC-722 ?
      2. Any first code/design review request that Arun and Dhiraj should review?
      3. progress, subhash: simulator adapted. E2T changes internally ready.
      4. config xapp and E2 manager interface.
      5. discuss E2 reset
      6. thoralf to sent invitation to Subhash &co for Friday
      7. Subhash&co did not plan to do any testing on xApp side.
    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
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
    3. in DU?
  8. anybody working on this RIC-705 Alexandre wants to know.
    1. 2022-02-15: Thoralf sent mail to E & A.
  9. RICAPP agenda: RICAPP Meetings.

2022-02-01

Recording: link to zoom recording

  1. Thoralf-TODO-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. 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/+/7450 ok
    2. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/7465 ok
    3. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7481 ok
    4. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/7515 ok
    5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7592 ok (note this is the E2APv2.0 support in submgr in subbranch "e2ap-02.00" - only to be merged with other E2APv2.0 changes)
    6. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7587 ok
    7. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7610 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. 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. ric-plt/alarm-go 0,0 // no bugs (2021-11-22 → 2022-01-30 )
    4. ric-plt/appmgr 17,5 → 19,3 // 1 major bug (2021-11-22 → 2022-01-30)
    5. ric-plt/e2mgr 88,6 // no bugs (2021-11-18 → 2022-01-30)
    6. ric-plt/lib/rmr 70,4 → 86,2 // no bugs (2021-11-23 → 2022-01-25)
    7. ric-plt/sdlgo 47,4 → 32.4 → 25,2 // no bugs (2021-11-23 → 2022-01-31) → raise bug
    8. ric-plt/submgr 44,8  → 47,4 → 51,2 // no bugs (2021-11-22 → 2022-01-30)
    9. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-11-16 → 2022-01-25)
    10. ric-plt/tracelibgo 94,7 → 96,2 //0 bugs (2021-11-22 → 2022-01-30)
    11. ric-plt/xapp-frame 0,0 // no bugs (2021-09-30 → 2021-11-22) - same as before.
    12. ric-plt/xapp-frame-cpp 96,3 → 95,6 // still 2 blocker bugs → 0 blocker bugs (fix) (2021-11-17 → 2022-01-26)
  4. Every time: Check if there are new bug reports in JIRA: link
    1. new: RIC-872 needs someone to fix. → Alexandre working it. Discussion in revies
    2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    3. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    4. RIC-835 → 2021-12-07 news from Viktor
    5. RIC-837 RMR is not forwarding messages from E2T to E2M
    6. RIC-840 Unable to deploy E2Term on Dawn release
    7. 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.
    8. fixed: RIC-880, RIC-875, RIC-873, RIC-869, RIC-862
    9. anybody would like to get more familiar with RMR?
  5. F release
    1. schedule
      1. Sprint F release dev sprint 1: Feb-21 to Mar-13 (as per Releases)
      2. Sprint F release dev sprint 2: Mar-14 to Apr-3
      3. Sprint F release dev sprint 3: Apr-4 to Apr-24
      4. Sprint F release dev sprint 4: Apr-25 to May-15 (last planned development sprint)
      5. Sprint F release dev sprint5: May-16 to Jun-5 (only for unplanned last-minute development items)
    2. Filter All RICP items: F release only (links copied from Jira usage conventions)
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-s and all teams.
      2. committed items only: all teams (committed)
      3. items that are known to require work, but are currently not in F release: link
    3. update 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
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
    4. Sunil still to discuss with other team members for other items from subteam-h
    5. James: RSAC recommended incorporating OTF in testing (David K. can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James. 2022-01-27 (Mail sent)
  6. James had a meeting with Powderlab in UofU on using their lab setup for testing. They have earlier tested OSC D release (and others). James is thinking about using this. Low hanging fruit would be to see if we can run our end-2-end robot test cases in this lab.
    1. POWDER testbed ORAN demo submission at MWC 2022: https://oranalliance.atlassian.net/wiki/spaces/OAH/pages/2330100360/PROCESSING+MWC-B-22-14+University+of+Utah
  7. Needed: overview of what is in golang and what in python and what in c++ and what is missing →
    1. Added this as RIC-882 (F release)
  8. RICAPP agenda: RICAPP Meetings.

2022-01-18

Recording: RIC platform meeting, demo on OID support in RIC, RIC xApp meeting, demo on hello-world python xapp

  1. Thoralf-TODO-cross-check with Abdulwahid if he has updated the instructions to point to helm3.
  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. we did not do this this time.
  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)
    3. We did not do this this time
    Anybody willing to work on them?
  4. Every time: Check if there are new bug reports in JIRA: link
    1. new: RIC-872 needs someone to fix. → Alexandre fixed this.
    2. RIC-875 thoralf to gheck with timo if fixed already.
    3. All others thoralf still to gpo thporugh if any news on them.
    4. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build

    5. RIC-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak) → Alexandre → DONE

    6. RIC-861 re-enable RMR libary's module tests

    7. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    8. RIC-835 → 2021-12-07 news from Viktor
    9. RIC-837 RMR is not forwarding messages from E2T to E2M
    10. RIC-840 Unable to deploy E2Term on Dawn release
    11. 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.
    12. fixed: RIC-862, RIC-828, RIC-836, RIC-858, RIC-859, RIC-863, RIC-865
    13. anybody would like to get more familiar with RMR?
  5. F release
    1. schedule
      1. Sprint F release dev sprint 1: Feb-21 to Mar-13 (as per Releases)
      2. Sprint F release dev sprint 2: Mar-14 to Apr-3
      3. Sprint F release dev sprint 3: Apr-4 to Apr-24
      4. Sprint F release dev sprint 4: Apr-25 to May-15 (last planned development sprint)
      5. Sprint F release dev sprint5: May-16 to Jun-5 (only for unplanned last-minute development items)
    2. Filter All RICP items: F release only (links copied from Jira usage conventions)
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-s and all teams.
      2. committed items only: all teams (committed)
      3. items that are known to require work, but are currently not in F release: link
    3. update 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
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
    4. Sunil still to discuss with other team members for other items from subteam-h
    5. James: RSAC recommended incorporating OTF in testing (David K. can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
  6. Needed: overview of what is in golang and what in python and what in c++ and what is missing
  7. E-release Demo for E2APv1.1 and support for OID in function definitions (Naman)
  8. RICAPP agenda: RICAPP Meetings.

2022-01-04

Recording: link to zoom recording

  1. no near-rt RIC platform issues on the agenda. If anything to discuss, pls. discuss. If not, move on to point 2.
  2. RMR related bug raised by Erkki RIC-872, Matti assigned it to Alexander, who will work on it.
  3. RICAPP agenda: RICAPP Meetings.


2021-12-21

Recording: link to zoom recording

  1. We will have the E-release demo in one hour from now: 2021-12-21 Release E
  2. next meeting: Jan-4-2022 focus will be the ric xapp project. After this the next one is on Jan-18 which will again handle xapp and ric platform combined.
    1. Any input for F release, pls. send to Thoralf (back in office on Jan-10)
  3. 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/ricdms/+/6964 ok, not relevant as only API definition
    2. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7151 ok
    3. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7152 ok
    4. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6712 ok, as a test tool.
    5. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7398 ok
    6. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7428 ok
    7. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7290 ok
  4. 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)
    3. We did not do this this time
    Anybody willing to work on them?
  5. 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-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak) → Alexandre

    3. RIC-861 re-enable RMR libary's module tests

    4. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    5. RIC-835 → 2021-12-07 news from Viktor
    6. RIC-837 RMR is not forwarding messages from E2T to E2M
    7. RIC-840 Unable to deploy E2Term on Dawn release
    8. 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.
    9. fixed: RIC-828, RIC-836, RIC-858, RIC-859, RIC-863, RIC-865
    10. anybody would like to get more familiar with RMR?
  6. 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.
      3. O-RAN specs of July train have been released. Need to check if any parts have been put under SCCL
    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.
      1. 2021-12-21 no news from Nokia side. → see RIC-852 above
  7. E release
    1. E release images test-deployed. E2 Setup works, xApp deployment. All manual checks.
    2. TOC approved E release on Dec-15. Release images are here: Near-RT RIC (E release)
    3. 2021-12-21 Thoralf double-checked that branch "e-release" has been created in all components and also updated release checklist (all OK now): Release criteria checklist - Release E. All criteria "ok"
  8. Preliminary planning for the F release
    1. Not completed in E release (spill over into F): RIC-849, 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 the next meeting.
    4. Thoralf to send a reminder.
  9. Nitin: submgr subscription REST interface: https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/xapp-frame.git;a=tree;f=api
  10. RICAPP agenda: RICAPP Meetings.

2021-12-07

Recording: link to zoom recording

  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. we did not do this this time.
  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)
    3. We did not do this this time
    Anybody willing to work on them?
  4. Every time: Check if there are new bug reports in JIRA: link

    1. RIC-865 → Done fix unit tests in xapp-frame-py

    2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build

    3. RIC-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak)

    4. RIC-861 re-enable RMR libary's module tests

    5. RIC-858 → Done
    6. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    7. RIC-835 → 2021-12-07 news from Viktor
    8. RIC-836 → Done
    9. RIC-837
    10. RIC-840
    11. RIC-852
    12. anybody would like to get more familiar with RMR?
    13. Can Alexandre help with the RMR bug RIC-858?
  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.
      3. O-RAN specs of July train have been released. Need to check if any parts have been put under SCCL
    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.
      1. 2021-12-07 no news from Nokia side.
  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.
    1. reverting a commit related to simulator in https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/7253
    2. E release images test-deployed. E2 Setup works, xApp deployment. All manual checks.
  7. 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.
    4. Thoralf to send a reminder.
  8. Thoralf to arrange release demo for Dec-21: Release Demo with e.g. OID, submgr changes and E release example deployment
  9. RICAPP agenda: RICAPP Meetings.

2021-11-23

Recording: link to zoom recording

  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)
    3. ric-plt/alarm-go 0,0 // no bugs (2021-09-30 → 2021-11-22)
    4. ric-plt/appmgr 0,0 → 17,5 // 1 major bug ( 2021-09-30 → 2021-11-22)
    5. ric-plt/e2mgr 88,0 // no bugs (2021-09-28 → 2021-11-18)
    6. ric-plt/lib/rmr 86,1->70,4 // no bugs (2021-09-07 → 2021-11-23) → raise bug
    7. ric-plt/sdlgo 47,4 → 32.4// no bugs (2021-09-28 → 2021-11-23) → raise bug
    8. ric-plt/submgr 44,8  → 47,4// no bugs (2021-09-30 → 2021-11-22)
    9. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-08-10 → 2021-11-16)
    10. ric-plt/tracelibgo 94,7//0 bugs (2021-09-30 → 2021-11-22)
    11. ric-plt/xapp-frame 0,0 // no bugs (2021-09-30 → 2021-11-22) - same as before.
    12. ric-plt/xapp-frame-cpp 96,3 // still 2 blocker bugs (2021-09-22->2021-11-17)
    Anybody willing to work on them?
  4. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-858 → new
    2. RIC-835
    3. RIC-836 → Done
    4. RIC-837
    5. RIC-840
    6. RIC-852
    7. RIC-857
    8. anybody would like to get more familiar with RMR?
    9. Can Alexandre help with the RMR bug RIC-858?
  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. DONE-2021-11-23 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. DONE-2021-11-23: 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
    2. I understand that we updated this together with the Ubuntu 20.04 update during the last two weeks.
  10. Nitin: installation using helm3.
    1. Sangeetha: this should be possible since Cherry. Helm charts are the same.
  11. Calico should also work.
  12. Sangeetha asked for bug reports if any help is needed. Thoralf commented that before starting to work check with Thoralf if already someone working on the item.
  13. RICAPP agenda: RICAPP Meetings.


2021-11-09

Recording: link to zoom recording

  1. Anybody new who wants to introduce him/herself?
    1. GG (Parallel Wireless): wants to participate and possible contribute
    2. Viktor (contractor for globallogic/ARM) working on the ARM64 port
  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/+/6887 ok
    2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/6832 ok
    3. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/6939 ok
    4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6966 ok
    5. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricctl/+/6963 ok, yaml only
    6. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6915 ok
    7. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/6931 ok, asn1c output only
    8. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/6964 ok, yaml only
    9. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/6958 ok
    10. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7006 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
    1. RIC-835
    2. RIC-836 → Done
    3. RIC-837
    4. RIC-840
    5. RIC-852
    6. RIC-857
    7. anybody would like to get more familiar with RMR?
      1. Alexandre offered to help a bit and would like to get familiar with RMR.
  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.
      3. no news (2021-11-23)
    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.
      1. 2021-11-23: still open as we focus on RMR - E2T case
    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.
      7. 2021-11-23: Thoralf to send
  6. Thoralf recorded a 24min step-by-step video on how to deploy the Dawn release: 2021-11-05 Demo video release Dawn
    1. anybody has time to do part of the demo with public E2 simulator?
  7. 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.
  8. Arm port (do we need Jenkins CI jobs?)
    1. new merge requests
    2. RIC-835 - Viktor offered possibility of access to ARM hardware if needed (Subhash said restarting the componet helps)
  9. 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
  10. We did not discuss this today: 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
  11. RICAPP agenda: RICAPP Meetings.

Older meeting minutes

check from here: Project meetings (old)

  • No labels