Versions Compared

Old Version 12

changes.mady.by.user Thoralf Czichy

Saved on

compared with

New Version 13

changes.mady.by.user Thoralf Czichy

Saved on

Key

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

...

Note that the links to the recordings before 2021-03-16 where mp4 files. They broke when copying the text into this archive page. You can still find them as attachments to the original meetings page Project meetings -> click on the three dots in the upper right corner and select “Attachments” from the menu.


2022-11-08 (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. 2022-10-11+2022-11-08
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automatec 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-08: 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: RIC-943 (alarm-go), RIC-944 + RIC-945 (E2term)
    16. anybody would like to get more familiar with RMR?

  4. Suggestion: for the next meeting, as over the last two years, let's stick to the EET 4pm time slot even as the US and most parts of Europe change back from DST.

  5. demo day? Suggestion: Dec-20

  6. 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
      2. 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
      3. RIC-641 Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
          1. RIC-642 (python) done
          2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
        3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
        4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
        5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
        6. 2022-08-16: any news?
          1. one optinion is to cleanup CI first with the approach in RIC-912
          2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
        7. 2022-08-30  Waiting for Anh Nguyen to come fully back to work.
        8. 2022-09-13→ 2022-09-27: no update, but Anh Nguyen is now back and in discussion with Anssi
        9. 2022-10-11: Anh Nguyen to pick up again. Thoralf fixed CI issues via sandbox, minor change in CI job definition and it commit.
  7. 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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
    5. 2022-07-19: James is working on it with LF
    6. 2022-08-02: any updates?
      1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
      2. James working Sridhar on xTesting.
    7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
    8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
    9. 2022-09-13: kubectl version used in testing doesn't match expectations. Work in progress
    10. 2022-09-27: Demo is in the RSAC meeting from last week. Instructions are here: Automated Testing via XTesting And also watch the RSAC video recording from last week: link (fast forward to minute 9:00).
      1. next step: promote this to all OSC subprojects via TOC.
      2. James trying to run robot test cases in it/test.
    11. 2022-10-11: still work in progress. Second demonstration with updated scripts: https://wiki.o-ran-sc.org/download/attachments/3604609/XTesting-demo.mp4?api=v2
    12. 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.
  8. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G 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 G release dev sprint 1: Aug-22 to Sep-11
      2. Sprint G release dev sprint 2: Sep-12 to Oct-2
      3. Sprint G release dev sprint 3: Oct-3 to Oct-23
      4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
  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)
  10. In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
    1. 2022-09-13: likely the way we go forward - Subhash and Thoralf will handle
      1. 2022-09-27: Thoralf to create presentation material and send to subhash
      2. 2022-10-11: Material shared and sent to RSAC
      3. 2022-11-08: DONE
    2. FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place) - Thoralf will present on the O-RAN day
      1. 2022-11-08: DONE
      2. Thoralf talked about the RIC in the presentation "Panel 3 - The RIC: How to over-deliver on the promise". The panel 3 recording starts at 1:46:00 into the youtube video: https://youtu.be/W1i6EPQ1wzo?t=6370 Thoralf also talked in the breakout panel discussion "Unpacking the intelligence of RIC: optimization and automation of complexity" (no video)
      3. James organized a video loop for the OSC video recordings and James (CMCC) and and Ramesh (HCL) talked in the breakout panel discussion "Accelerating O-RAN adoption through open source"
      4. OAI planning to support E2SM-KPM/E2SM-RC in CU/DU/gNB
      5. ns-3 E2 adapter (GPL) is now published in OSC.
  11. Update from Samsung side
    1. A1 - golang - Naman used RMR from E2 manager (not from xapp-framework).
    2. DMS REST server - Remote-API-equivalent to dmscli.
  12. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-08-02
      1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
      2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
    2. 2022-09-13: working is progressing. end of September first commits should come.
    3. 2022-09-27: first commit likely coming this week. Johannes could demo in two weeks from now.
    4. 2022-10-11: first commit under review.
      1. 2022-10-11 Johannes to look into CI (and module tests) for Rust
        1. status: basic framework ready (ping-pong dmeo works between two xapps). next step SDL.
      2. 2022-11-08 demo (5-10min)
  13. RICAPP agenda: RICAPP Meetings.

2022-10-25 (Tuesday)

CANCELLED due to conference participation and sick leave.

2022-10-11 (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. 2022-10-11
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how module testing can be done is to be discussed // also need to discuss CI
  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-10-11: 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. 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
      2. 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
      3. RIC-641 Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
          1. RIC-642 (python) done
          2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
        3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
        4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
        5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
        6. 2022-08-16: any news?
          1. one optinion is to cleanup CI first with the approach in RIC-912
          2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
        7. 2022-08-30  Waiting for Anh Nguyen to come fully back to work.
        8. 2022-09-13→ 2022-09-27: no update, but Anh Nguyen is now back and in discussion with Anssi
        9. 2022-10-11: Anh Nguyen to pick up again. Thoralf fixed CI issues via sandbox, minor change in CI job definition and it commit.
  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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
    5. 2022-07-19: James is working on it with LF
    6. 2022-08-02: any updates?
      1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
      2. James working Sridhar on xTesting.
    7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
    8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
    9. 2022-09-13: kubectl version used in testing doesn't match expectations. Work in progress
    10. 2022-09-27: Demo is in the RSAC meeting from last week. Instructions are here: Automated Testing via XTesting And also watch the RSAC video recording from last week: link (fast forward to minute 9:00).
      1. next step: promote this to all OSC subprojects via TOC.
      2. James trying to run robot test cases in it/test.
    11. 2022-10-11: still work in progress. Second demonstration with updated scripts: https://wiki.o-ran-sc.org/download/attachments/3604609/XTesting-demo.mp4?api=v2
  6. 2022-10-11: last remaining demo from F-release
    1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → middle of Sept → (updated 2022-09-27): now scheduled for 2022-10-11 (Erkki)
  7. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G 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 G release dev sprint 1: Aug-22 to Sep-11
      2. Sprint G release dev sprint 2: Sep-12 to Oct-2
      3. Sprint G release dev sprint 3: Oct-3 to Oct-23
      4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
  8. 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.
  9. In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
    1. 2022-09-13: likely the way we go forward - Subhash and Thoralf will handle
      1. 2022-09-27: Thoralf to create presentation material and send to subhash
      2. 2022-10-11: Material shared and sent to RSAC
    2. FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place) - Thoralf will present on the O-RAN day
  10. Update from Samsung side
    1. A1 - golang - Naman used RMR from E2 manager (not from xapp-framework). Need module label - Thoralf to check. Add Alexandre to mail chain.
    2. DMS REST server - Remote-API-equivalent to dmscli. Abukar + Abdulwahid-team and Samsung team on reviewing DMS server implementation. TODO-Thoralf
  11. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-08-02
      1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
      2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
    2. 2022-09-13: working is progressing. end of September first commits should come.
    3. 2022-09-27: first commit likely coming this week. Johannes could demo in two weeks from now.
    4. 2022-10-11: first commit under review.
      1. 2022-10-11 Johannes to look into CI (and module tests) for Rust
        1. status: basic framework ready (ping-pong dmeo works between two xapps). next step SDL.
      2. 2022-10-25 demo
  12. host for 2022-10-25? - Sunil
  13. RICAPP agenda: RICAPP Meetings.

2022-09-27 (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. 2022-09-27
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/9006 → https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/9020 OK, (influx update) only deployment changes. So ok with test case.
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/stslgo/+/9010 → https://gerrit.o-ran-sc.org/r/c/ric-plt/stslgo/+/9047 OK, (influx update) test cases included.
  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-08-30, 2022-09-13, 2022-09-27: we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. 2022-09-27: one new bug: RIC-940 → Timo
    2. RIC-940 sdlpy missing whitespace → Timo
    3. RIC-939 race conditions in RMR → Abdulwahid
    4. 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)
    5. RIC-915 dms_cli for installing xapp not working (raised by James)
    6. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    7. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    8. RIC-897 SCTP connection fails with Viavi // update with workaround
    9. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    10. RIC-894 long idle period (days) causes RMR connection breaks
    11. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    12. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    13. 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.
    14. RIC-837 RMR is not forwarding messages from E2T to E2M
    15. RIC-835 → 2021-12-07 news from Viktor
    16. fixed: no new fixes.
    17. 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. 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
      2. 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
      3. RIC-641 Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
          1. RIC-642 (python) done
          2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
        3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
        4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
        5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
        6. 2022-08-16: any news?
          1. one optinion is to cleanup CI first with the approach in RIC-912
          2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
        7. 2022-08-30  Waiting for Anh Nguyen to come fully back to work.
        8. 2022-09-13→ 2022-09-27: no update, but Anh Nguyen is now back and in discussion with Anssi
  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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
    5. 2022-07-19: James is working on it with LF
    6. 2022-08-02: any updates?
      1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
      2. James working Sridhar on xTesting.
    7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
    8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
    9. 2022-09-13: kubectl version used in testing doesn't match expectations. Work in progress
    10. 2022-09-27: Demo is in the RSAC meeting from last week. Instructions are here: Automated Testing via XTesting And also watch the RSAC video recording from last week. TODO
      1. next step: promote this to all OSC subprojects via TOC.
      2. James trying to run robot test cases in it/test.
  6. 2022-07-05: still one remaining demos.
    1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → middle of Sept → (updated 2022-09-27): now scheduled for 2022-10-11 (Erkki)
  7. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G 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 G release dev sprint 1: Aug-22 to Sep-11
      2. Sprint G release dev sprint 2: Sep-12 to Oct-2
      3. Sprint G release dev sprint 3: Oct-3 to Oct-23
      4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
  8. 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: 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.
  9. In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
    1. 2022-09-13: likely the way we go forward - Subhash and Thoralf will handle
    2. FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place)
    3. 2022-09-27: Thoralf to create presentation material and send to subhash
  10. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-08-02
      1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
      2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
    2. 2022-09-13: working is progressing. end of September first commits should come.
    3. 2022-09-27: first commit likely coming this week. Johannes could demo in two weeks from now.
  11. RICAPP agenda: RICAPP Meetings.

2022-09-13 (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. 2022-09-13 
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/9006 OK, (influx update) only deployment changes. So ok with test case.
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/stslgo/+/9010 OK, (influx update) test cases included.
  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-08-30, 2022-09-13: we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. 2022-09-13: one new bug: RIC-939
    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. 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. 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: 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. 2022-08-30: contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
        1. 2022-09-13: Now hanging with Augu. - waiting for reply
  5. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
    6. 2022-08-16: any news?
      1. one optinion is to cleanup CI first with the approach in RIC-912
      2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
    7. 2022-08-30  Waiting for Anh Nguyen to come fully back to work.
    8. 2022-09-13: now update, but Anh Nguyen is now back and in discussion with Anssi
  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-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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
    5. 2022-07-19: James is working on it with LF
    6. 2022-08-02: any updates?
      1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
      2. James working Sridhar on xTesting.
    7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
    8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
    9. 2022-09-13: kubectl version used in testing doesn't mahc expectations. Work in progress
  7. 2022-07-05: still one remaining demos.
    1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → (update 2022-08-16) middle of Sept (Erkki)
  8. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G 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 G release dev sprint 1: Aug-22 to Sep-11
      2. Sprint G release dev sprint 2: Sep-12 to Oct-2
      3. Sprint G release dev sprint 3: Oct-3 to Oct-23
      4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
  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-13: 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.
  10. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
    1. 2022-08-30: Subhash presented the results of the discussion - material is here https://wiki.o-ran-sc.org/display/RICP/E2AP+2.0+Design 
  11. In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
    1. 2022-09-13: likely the way we go forward - Subhash and Thoralf will handle
    2. FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place)
  12. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-08-02
      1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
      2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
    2. 2022-09-13: working is progressing. end of September first commits should come.
  13. 2022-09-13: Joseph Thaliath &  Sandeep J to present plans of OSC AI/ML subproject
    1. slideset: https://wiki.o-ran-sc.org/download/attachments/57377183/AIMLFW-KickOffMeeting.pdf?api=v2
  14. RICAPP agenda: RICAPP Meetings.

2022-08-30 (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. 2022-08-30  We did not check this 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. Thoralf did this last on May-27-2022. 2022-08-30 we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. 2022-08-30: TODO
    2. 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)
    3. RIC-915 dms_cli for installing xapp not working (raised by James)
    4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    6. RIC-897 SCTP connection fails with Viavi // update with workaround
    7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    8. RIC-894 long idle period (days) causes RMR connection breaks
    9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    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. RIC-837 RMR is not forwarding messages from E2T to E2M
    13. RIC-835 → 2021-12-07 news from Viktor
    14. fixed: no new fixes.
    15. 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. 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: 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
      12. 2022-08-30: contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
  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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
    5. 2022-07-19: James is working on it with LF
    6. 2022-08-02: any updates?
      1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
      2. James working Sridhar on xTesting.
    7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
    8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
  6. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
    6. 2022-08-16: any news?
      1. one optinion is to cleanup CI first with the approach in RIC-912
      2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
    7. 2022-08-30  Waiting for Any Nguyen to come fully back to work.
  7. 2022-07-05: still one remaining demos.
    1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → (update 2022-08-16) middle of Sept (Erkki)
  8. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G 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 G release dev sprint 1: Aug-22 to Sep-11
      2. Sprint G release dev sprint 2: Sep-12 to Oct-2
      3. Sprint G release dev sprint 3: Oct-3 to Oct-23
      4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
  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 no news yet
  10. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
    1. 2022-04-26: 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).
    4. 2022-06-07: Thoralf will schedule a meeting for week after next week
    5. 2022-06-21→2022-07-05: This has to wait for end of July
    6. 2022-08-02: meeting scheduled for 2022-08-04
    7. 2022-08-30: Subhash presented the results of the discussion - material is here https://wiki.o-ran-sc.org/display/RICP/E2AP+2.0+Design 
  11. In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
  12. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-08-02
      1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
      2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
  13. RICAPP agenda: RICAPP Meetings.

2022-08-16 (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. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/8824 → OK, as only new swagger yaml file for which nothing is implemented yet.
  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 May-27-2022. 2022-08-16 we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. 2022-08-16: TODO
    2. RIC-936 change from gcr.io → ghcr.io in master and f-release DONE
    3. RIC-935 flannel namespace change. fixed in master and f-release DONE
    4. 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)
    5. RIC-915 dms_cli for installing xapp not working (raised by James)
    6. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    7. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    8. RIC-897 SCTP connection fails with Viavi // update with workaround
    9. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    10. RIC-894 long idle period (days) causes RMR connection breaks
    11. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    12. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    13. 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.
    14. RIC-837 RMR is not forwarding messages from E2T to E2M
    15. RIC-835 → 2021-12-07 news from Viktor
    16. fixed: RIC-935, RIC-936
    17. 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. 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: 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
  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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
    5. 2022-07-19: James is working on it with LF
    6. 2022-08-02: any updates?
      1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
      2. James working Sridhar on xTesting.
    7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
  6. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
    6. 2022-08-16: any news?
      1. one optinion is to cleanup CI first with the approach in RIC-912
      2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
  7. 2022-07-05: still one remaining demos.
    1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → (update 2022-08-16) middle of Sept (Erkki)
  8. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G 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 G release dev sprint 1: Aug-22 to Sep-11
      2. Sprint G release dev sprint 2: Sep-12 to Oct-2
      3. Sprint G release dev sprint 3: Oct-3 to Oct-23
      4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
  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 no news yet
  10. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
    1. 2022-04-26: 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).
    4. 2022-06-07: Thoralf will schedule a meeting for week after next week
    5. 2022-06-21→2022-07-05: This has to wait for end of July
    6. 2022-08-02: meeting scheduled for 2022-08-04
    7. 2022-08-16: Subhash to present results of discussion in next meeting on 2022-08-30
  11. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-08-02
      1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
      2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
    2. 2022-08-16: repo is now created ->Closed
  12. RICAPP agenda: RICAPP Meetings.

2022-08-02 (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. 2022-08-02: no large commits
  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 May-27-2022. 2022-08-02 we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. 2022-08-02: no new bugs, no new fixes
    2. 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)
    3. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
    4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    6. RIC-897 SCTP connection fails with Viavi // update with workaround
    7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    8. RIC-894 long idle period (days) causes RMR connection breaks
    9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    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. RIC-837 RMR is not forwarding messages from E2T to E2M
    13. RIC-835 → 2021-12-07 news from Viktor
    14. fixed:no new fixes
    15. 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. 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?
  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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
    5. 2022-07-19: James is working on it with LF
    6. 2022-08-02: any updates?
      1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
      2. James working Sridhar on xTesting.
  6. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
  7. 2022-07-05: still one remaining demos.
    1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
  8. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G 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 G release dev sprint 1: Aug-22 to Sep-11
      2. Sprint G release dev sprint 2: Sep-12 to Oct-2
      3. Sprint G release dev sprint 3: Oct-3 to Oct-23
      4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
  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 scheduke a meeting once a proposal is ready.
  10. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
    1. 2022-04-26: 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).
    4. 2022-06-07: Thoralf will schedule a meeting for week after next week
    5. 2022-06-21→2022-07-05: This has to wait for end of July
    6. 2022-08-02: meeting scheduled for 2022-08-04
  11. 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.
    1. 2022-07-19 no news
    2. 2022-08-02 → move to bug sections (Thoralf added this as comment to RIC-894)
  12. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-08-02
      1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
      2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
  13. RICAPP agenda: RICAPP Meetings.

2022-07-19 (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).2022-07-19:
        we did not do this 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. Thoralf did this last on May-27-2022. 2022-07-19 we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. 2022-07-19: we did not check this this time.
    2. 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)
    3. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
    4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    6. RIC-897 SCTP connection fails with Viavi // update with workaround
    7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    8. RIC-894 long idle period (days) causes RMR connection breaks
    9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    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. RIC-837 RMR is not forwarding messages from E2T to E2M
    13. RIC-835 → 2021-12-07 news from Viktor
    14. fixed:no new fixes
    15. 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. 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.
  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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: XTesting proposed as alternative to OTF
    5. 2022-07-19: James is workin on it with LF
  6. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
  7. 2022-07-05: still two remaining demos.
    1.  2022-07-19: RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Shobha)
      1. new function in https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/nodeb-rnib.git;a=blob;f=reader/rNibReader.go -> GetRanFunctionDefinition()
      2. C version via creader (see https://packagecloud.io/o-ran-sc/release/packages/debian/stretch/rnib_1.2.5_all.deb)
      3. play video "RIC_888.mp4" from tmp folder (remember ... → "share sound")
    2. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
    3. 2022-07-19: Thoralf uploaded demo on deploying RIC, connecting the simulator project's E2 (node) simulator, Nokia simulator and deploy the hw-go xapp as well: 2022-05-24 Release F
  8. F release wrap up
    1. 2022-07-05 & 2022-07-19: F release. See demo page: Release criteria checklist - Release F, Near-RT RIC (F release) = image list, F Release = summary, 2022-05-24 Release F = demos.
  9. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G 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 G release dev sprint 1: Aug-22 to Sep-11
      2. Sprint G release dev sprint 2: Sep-12 to Oct-2
      3. Sprint G release dev sprint 3: Oct-3 to Oct-23
      4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
  10. 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).
  11. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
    1. 2022-04-26: 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).
    4. 2022-06-07: Thoralf will schedule a meeting for week after next week
    5. 2022-06-21→2022-07-05: This has to wait for end of July
  12. 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.
    1. 2022-07-19 no news
  13. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-07-19 TOC approved ric-plt/xapp-frame-rust is ready for content. ric-app/hw-rust still to be created
    2. 2022-07-19 go through commit steps
  14. RICAPP agenda: RICAPP Meetings.

2022-07-05 (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).2022-07-05:
        we did not do this 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. Thoralf did this last on May-27-2022. 2022-07-05 we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. 2022-07-05: we did not check this this time.
    2. 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)
    3. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
    4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    6. RIC-897 SCTP connection fails with Viavi // update with workaround
    7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    8. RIC-894 long idle period (days) causes RMR connection breaks
    9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    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. RIC-837 RMR is not forwarding messages from E2T to E2M
    13. RIC-835 → 2021-12-07 news from Viktor
    14. fixed:no new fixes
    15. 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. 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
  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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: Xtesting proposed as alternative to OTF
    5. 2022-07-05: Any news from James?
  6. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-py) out of the F release. Which means they are likely early G release features.
  7. 2022-07-05: still two remaining demos.
    1. No demo today (plan for 2022-07-19) 5 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Manoj)
    2. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
    3. 2022-07-05: Thoralf uploaded demo on deploying RIC, connecting the simulator project's E2 (node) simulator, Nokia simulator and deploy the hw-go xapp as well: 2022-05-24 Release F
  8. F release wrap up
    1. 2022-07-05 & 2022-07-19: F release. See demo page: Release criteria checklist - Release F, Near-RT RIC (F release) = image list, F Release = summary, 2022-05-24 Release F = demos.
  9. 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).
      4. 2022-06-07: Thoralf will schedule a meeting for week after next week
    2. 2022-06-21→2022-07-05: This has to wait for end of July
  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.
    1. 2022-07-05 no news
  11. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-06-21: We had a meeting on this last week and proposal for TOC is in the making. Two new components: ric-plt/xapp-frame-rust and ric-app/hw-rust)
    2. 2022-07-05:
      1. addition of ric-plt/xapp-frame-rust and ric-app/hw-rust was approved by TOC on Jun-23-2022.
      2. Thoralf to create the repos once back from holiday (mid July)
  12. RICAPP agenda: RICAPP Meetings.


2022-06-21 (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. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/8368 OK cleanup of ric-dep and it-dep (only copied code)
    2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493 OK
    3. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/8569 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. Thoralf did this last on May-27-2022. Not done this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. 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)
    2. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
    3. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    4. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    5. RIC-897 SCTP connection fails with Viavi // update with workaround
    6. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    7. RIC-894 long idle period (days) causes RMR connection breaks
    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-920 (gNB ID fix)
    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
      7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
  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.
        1. 2022-05-30: Thoralf comment in RIC-915
    4. 2022-06-21: Xtesting proposed as alternative to OTF
  6.  Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (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-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
  7. 2022-06-21: demo held on 2022-07-06. Remaining demos planned for 2022-06-21
    1. No demo today (plan for 2022-07-19) 5 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Manoj)
    2. 10min RIC-916 new reconnect timer in E2 to reject new connect for x seconds (dhiraj)
    3. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
  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).
        4. 2022-06-07: Thoralf will schedule a meeting for week after next week
        5. 2022-06-21: This has to wait for end of July
  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. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-06-21: We had a meeting on this last week and proposal for TOC is in the making. Two new components: ric-plt/xapp-frame-rust and ric-app/hw-rust)
    2. Approved by the TOC.
  12. RICAPP agenda: RICAPP Meetings.

2022-06-07 (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. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/8324  OK (commit of previously reviewed files in e2ap branch)
    2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8303 OK (commit of previously reviewed files in e2ap branch)
    3. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/8323 OK (commit of previously reviewed files in e2ap branch)
    4. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/8332 OK (change in proto file that caused changes in generated files)
    5. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/8368 OK (lots of code moved from it/dep repo)
  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 on May-27-2022 - no surprises
    4. ric-plt/alarm-go 0,0 // no bugs (2021-11-22 → 2022-02-13 → 2022-05-26)
    5. ric-plt/appmgr 19,3 // 1 major bug (2022-01-30 → 2022-02-13 → 2022-05-26)
    6. ric-plt/e2mgr 88,6 → 87,7 // no bugs (2021-11-18 → 2022-02-14 → 2022-05-27)
    7. ric-plt/lib/rmr 86,1 // no bugs (2021-11-23 → 2022-02-08 → 2022-05-24)
    8. ric-plt/sdlgo 90,2 → 90,5 // no bugs (2022-01-31 → 2022-02-14 → 2022-05-27)
    9. ric-plt/submgr 51,4 // no bugs (2022-01-30 → 2022-02-13 → 2022-05-27)
    10. ric-plt/tracelibcpp 0,0 // 1 major bug (2022-01-25 → 2022-02-08 → 2022-05-24)
    11. ric-plt/tracelibgo 96,2 //0 bugs (2022-01-30 → 2022-02-13 → 2022-05-27)
    12. ric-plt/xapp-frame 0,0 // no bugs (2021-11-22 → 2022-02-13 → 2022-05-26)
    13. ric-plt/xapp-frame-cpp 95,6 → 96,3 // no blocker bugs (2022-01-26 → 2022-02-00 → 2022-05-25)
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
    2. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    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-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    8. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    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. RIC-837 RMR is not forwarding messages from E2T to E2M
    11. RIC-835 → 2021-12-07 news from Viktor
    12. fixed: no new fixes
    13. 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
      7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
  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.
        1. 2022-05-30: Thoralf comment in RIC-915
  6. Progress on E2APv2.0?
    1. 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.
        2. 2022-05-30: Simulator worked fine, but thoralf raised SIM-99 for supporting source-address binding in the simulator
      5. 2022-05-31: as we're not ready with RIC-641 (cpp) and RIC-642 (python) we decided to still keep RMR enabled as interface provided by the subscription manager. RIC-642 is almost ready, and I understand RIC-641 is also being worked on.  07-06-2022 - RIC-641 HCL team is working on this.   
      6. 07-06-2022: E2APv2.0 - Code merged
    2. 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.
    4. 2022-06-07: Any news?
  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
      2. 2022-07-06 demo held. Remaining demos planned for 2022-06-21
        1. 5 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Manoj)
        2. 10min RIC-916 new reconnect timer in E2 to reject new connect for x seconds
  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).
        4. 2022-06-07: Thoralf will schedule a meeting for week after next week
  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. Note - 6-7-2022 : Matti send a mail on this.  RUST as a language for xApps and framework. Will take this in the details in next meeting.
  12. RICAPP agenda: RICAPP Meetings.

2022-05-24

we used this slot as demo meeting for the F release. Demo recording: 2022-05-24 Release F

2022-05-11 (exceptionally Wednesday)

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/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. 2022-06-07: We plan to release in June. Thoralf will coordinate creation of container images by e-mail.
    1. F release tasks for releasing the container images: Near-RT RIC (F release)
    2. F release status: F Release
    3. F release criteria checklist (filled in by Thoralf): Release criteria checklist - Release F
  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. 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
  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-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.
  7. 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.
  8. 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.
  9. 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
  10. 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).
  11. 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.
  12. RICAPP agenda: RICAPP Meetings.

2022-04-26

Recording: link to zoom recording

...