Versions Compared

Old Version 13

changes.mady.by.user Thoralf Czichy

Saved on

compared with

New Version 14

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.

2023-04-25

Recording: link to zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on 2023-04-11
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/10803 OK, bug fixed for dynamic log level change
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10675 OK, tests 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-11-22, 2023-03-28, 2023-04-11:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-972 URL for A1 mediator to align with spec.
    2. RIC-971 Fix potential segfaults and double free corruption (in E2T)
    3. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    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:

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

    1. The current platform deployment scripts might not be in line with O2 envisions
    2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    3. O2-D(MS) is relevant to RIC platform.
    4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    5. 2023-01-31: No news yet
    6. 2023-02-14: No news yet, Thoralf received e-mail on this from James. Still to check.
    7. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
    8. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.
    9. 2023-03-28:no news
    10. 2023-04-11: Tacker team provided ideas on SMO architecture (in context of RSAC). No immediate action items for Near-RT RIC platform project
    11. 2023-04-25: we did not discuss
  5. Prashant's work in near-RT RIC
    1. 2023-04-25:
      1. Prashant updated call flow for A1. Will send it for review RIC-973
      2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975
      3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976
  6. James: updates?
    1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
        1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
        2. Tacker-based deployment needs to be checked.
    2. 2023-03-14, 2023-03-28 : no news
    3. 2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.
    4. 2023-04-25: no updates
  7. Sunil updates?
    1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25: no news
  8. Subhash/Naman updates?
    1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
      1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
        1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
          1. Thoralf to create JIRA item for this
          2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
          3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
          4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
        2. Integration with AI/ML project: kserve_adapter
          1. data pipeline (Hoejoo's e-mail)
            1. 2023-01-31 not discussed in today's meeting
    2. 2023-03-14:
      1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
      2. A1 mediator nanobot integration still under work
    3. 2023-03-28: work continues
    4. 2023-04-11: E2 reset work in submgr is now under work.
    5. 2023-04-25: Naman working on E2 reset (submgr part), ricdms not too much progress. no update on kserve
  9. Abhijit updates?
    1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
      1. Thoralf raised support request to LF. Reminders sent. Still no solution.
    2. 2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
    3. 2023-03-28: working on RIC-969 and part of RIC-957
    4. 2023-04-11:
      1. RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).
      2. hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.
    5. 2023-04-25
      1. working on RNIB support in rust (https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10906) and next step hw-rust.
  10. Cap Gemini updates?
    1. 2023-03-14
      1. RIC-851 done
      2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
    2. 2023-03-28, 2023-04-11, 2023-04-25: no news.
  11. H release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
      1. Sprint H release dev sprint 1: Feb-20´to Mar-12
      2. Sprint H release dev sprint 2: Mar-13 to Apr-2
      3. Sprint H release dev sprint 3: Apr-3 to Apr-23
      4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
      5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
  12. GRPC vs RMR
    1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25: no update
  13. Himanshu would like to work on RIC-963 → ok.
  14. Anybody ever tried RIC platform with IPv6? E2T should work with IPv6 for E2. Rest Thoralf does not know.
  15. RICAPP agenda: RICAPP Meetings.

2023-04-11

Recording: link to zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on 2023-04-11
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/10803 OK, bug fixed for dynamic log level change
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10675 OK, tests 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-11-22, 2023-03-28, 2023-04-11:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-972 URL for A1 mediator to align with spec.
    2. RIC-971 Fix potential segfaults and double free corruption (in E2T)
    3. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    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-962, RIC-961, RIC-964, RIC-966, RIC-968, RIC-939, RIC-940. RIC-970

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

    1. The current platform deployment scripts might not be in line with O2 envisions
    2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    3. O2-D(MS) is relevant to RIC platform.
    4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    5. 2023-01-31: No news yet
    6. 2023-02-14: No news yet, Thoralf received e-mail on this from James. Still to check.
    7. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
    8. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.
    9. 2023-03-28:no news
    10. 2023-04-11: Tacker team provided ideas on SMO architecture (in context of RSAC). No immediate action items for Near-RT RIC platform project
  5. Prashant's work in near-RT RIC
    1. Example of additional work needed: A1 - registry and "policystatusobject" (defined in spec, but not implemented in OSC near-RT RIC)
      1. best approach is to create a JIRA item and attach document to it
      2. link to JIRA item
      3. Another issue was related to SCTP in E2. Prashant will write an e-mail on the topic (incl Alexandre )
    2. Naman/subhash commented that e-mail is maybe good enough.
  6. James:updates?
    1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
        1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
        2. Tacker-based deployment needs to be checked.
    2. 2023-03-14, 2023-03-28 : no news
    3. 2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.
  7. Sunil updates?
    1. 2023-03-14, 2023-03-28, 2023-04-11: no news
  8. Subhash/Naman updates?
    1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
      1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
        1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
          1. Thoralf to create JIRA item for this
          2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
          3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
          4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
        2. Integration with AI/ML project: kserve_adapter
          1. data pipeline (Hoejoo's e-mail)
            1. 2023-01-31 not discussed in today's meeting
    2. 2023-03-14:
      1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
      2. A1 mediator nanobot integration still under work
    3. 2023-03-28: work continues
    4. 2023-04-11: E2 reset work in submgr is now under work.
  9. Abhijit updates?
    1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
      1. Thoralf raised support request to LF. Reminders sent. Still no solution.
    2. 2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
    3. 2023-03-28: working on RIC-969 and part of RIC-957
    4. 2023-04-11:
      1. RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).
      2. hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.
  10. Cap Gemini updates?
    1. 2023-03-14
      1. RIC-851 done
      2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
    2. 2023-03-28, 2023-04-11: no news.
  11. H release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
      1. Sprint H release dev sprint 1: Feb-20´to Mar-12
      2. Sprint H release dev sprint 2: Mar-13 to Apr-2
      3. Sprint H release dev sprint 3: Apr-3 to Apr-23
      4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
      5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
  12. GRPC vs RMR
    1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11: no update
  13. RICAPP agenda: RICAPP Meetings.

2023-03-28 (Tuesday)

Recording: link to zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on 2023-02-28
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/10666 OK
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/10287 OK
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10405 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
        1. 2023-02-28: Abhijit worked with Matt and Sridhar from LF on this. Jobs are now running, but they fail. There's a credential issue. Abhijit to remind Sridhar. Once this is fixed, we can change Dockerfile to install prerequisites.
        2. 2023-03-28: This is OK and is now closed.
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2022-05-27, 2022-11-22, 2023-03-28:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link

    1. new bug report RIC-962

    2. RIC-961 (fixed already)

    3. RIC-964 (fixed already)

    4. RIC_966 (fixed already)

    5. RIC-968 (fixed already)

    6. RIC-940 sdlpy missing whitespace → Timo
    7. RIC-939 race conditions in RMR → Abdulwahid
    8. 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)
    9. RIC-915 dms_cli for installing xapp not working (raised by James)
    10. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    11. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    12. RIC-897 SCTP connection fails with Viavi // update with workaround
    13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    14. RIC-894 long idle period (days) causes RMR connection breaks
    15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    17. 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.
    18. RIC-837 RMR is not forwarding messages from E2T to E2M
    19. RIC-835 → 2021-12-07 news from Viktor
    20. fixed: no new fixes
    21. anybody would like to get more familiar with RMR?

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

    1. The current platform deployment scripts might not be in line with O2 envisions
    2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    3. O2-D(MS) is relevant to RIC platform.
    4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    5. 2023-01-31: No news yet
    6. 2023-02-14 No news yet, Thoralf received e-mail on this from James. Still to check.
    7. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
    8. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.
    9. 2023-03-28: no news
  5. James:updates?
    1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
        1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
        2. Tacker-based deployment needs to be checked.
    2. 2023-03-14, 2023-03-28: : no news
  6. Sunil updates?
    1. 2023-03-14, 2023-03-28: : no news
  7. Subhash/Naman updates?
    1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
      1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
        1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
          1. Thoralf to create JIRA item for this
          2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
          3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
          4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
        2. Integration with AI/ML project: kserve_adapter
          1. data pipeline (Hoejoo's e-mail)
            1. 2023-01-31 not discussed in today's meeting
    2. 2023-03-14:
      1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
      2. A1 mediator nanobot integration still under work
    3. 2023-03-28: work continues
  8. Abhijit updates?
    1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
      1. Thoralf raised support request to LF. Reminders sent. Still no solution.
    2. 2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
    3. 2023-03-28: working on RIC-969 and part of RIC-957
  9. Cap Gemini updates?
    1. 2023-03-14
      1. RIC-851 done
      2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
    2. 2023-03-28: no news.
  10. H release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
      1. Sprint H release dev sprint 1: Feb-20´to Mar-12
      2. Sprint H release dev sprint 2: Mar-13 to Apr-2
      3. Sprint H release dev sprint 3: Apr-3 to Apr-23
      4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
      5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
  11. GRPC vs RMR
    1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28 : no update
  12. RICAPP agenda: RICAPP Meetings.

2023-03-14 (Tuesday)

Recording: link to zoom recording

We stick to the 4pm Helsinki time slot for this meeting. Note that Europe will switch to summer time on March-26. So, for people not doing the switch at the same time, the meetings after March-26 start one hour earlier. Reminder for participants from the US: The US already switched to summer time on Mar-12.

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on 2023-02-28
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10405 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
        1. 2023-02-28: Abhijit worked with Matt and Sridhar from LF on this. Jobs are now running, but they fail. There's a credential issue. Abhijit to remind Sridhar. Once this is fixed, we can change Dockerfile to install prerequisites.
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/10287 → waiting for test cases, Gunja know and will update test case.
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link

    1. new bug report RIC-962

    2. RIC-961 (fixed already)

    3. RIC-964 (fixed already)

    4. RIC_966 (fixed already)

    5. RIC-968 (fixed already)

    6. RIC-940 sdlpy missing whitespace → Timo
    7. RIC-939 race conditions in RMR → Abdulwahid
    8. 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)
    9. RIC-915 dms_cli for installing xapp not working (raised by James)
    10. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    11. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    12. RIC-897 SCTP connection fails with Viavi // update with workaround
    13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    14. RIC-894 long idle period (days) causes RMR connection breaks
    15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    17. 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.
    18. RIC-837 RMR is not forwarding messages from E2T to E2M
    19. RIC-835 → 2021-12-07 news from Viktor
    20. fixed: no new fixes
    21. anybody would like to get more familiar with RMR?

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

    1. The current platform deployment scripts might not be in line with O2 envisions
    2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    3. O2-D(MS) is relevant to RIC platform.
    4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    5. 2023-01-31: No news yet
    6. 2023-02-14 No news yet, Thoralf received e-mail on this from James. Still to check.
    7. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
    8. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.
  5. James:updates?
    1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
        1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
        2. Tacker-based deployment needs to be checked.
    2. 2023-03-14: no news
  6. Sunil updates?
    1. 2023-03-14: no news
  7. Subhash/Naman updates?
    1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
      1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
        1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
          1. Thoralf to create JIRA item for this
          2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
          3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
          4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
    2. 2023-03-14:
      1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
      2. A1 mediator nanobot integration still under work.
  8. Abhijit updates?
    1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
      1. Thoralf raised support request to LF. Reminders sent. Still no solution.
    2. 2023-03-14: now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
  9. Cap Gemini updates?
    1. 2023-03-14
      1. RIC-851 done
      2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
  10. H release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
      1. Sprint H release dev sprint 1: Feb-20´to Mar-12
      2. Sprint H release dev sprint 2: Mar-13 to Apr-2
      3. Sprint H release dev sprint 3: Apr-3 to Apr-23
      4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
      5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
  11. GRPC vs RMR
    1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14: no update
  12. Integration with AI/ML project: kserve_adapter
    1. data pipeline (Hoejoo's e-mail)
      1. 2023-01-31 not discussed in today's meeting
  13. Gunja and Sachin (CapGemini) presented changes that were done for RIC subscription delete required as per RIC-851. Thoralf to start a mail thread with Nitin, Subhash, Gunja, Sachin on how xapps can be notified of subscription changes. link to the presentation 2023-03-14: Discussion done and resulted in RIC-967.
  14. RICAPP agenda: RICAPP Meetings.

2023-02-28 (Tuesday)

Recording: link to zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on 2023-02-28
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10405 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
        1. 2023-02-28: Abhijit worked with Matt and Sridhar from LF on this. Jobs are now running, but they fail. There's a credential issue. Abhijit to remind Sridhar. Once this is fixed, we can change Dockerfile to install prerequisites.
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/10287 → waiting for test cases, Gunja know and will update test case.
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-940 sdlpy missing whitespace → Timo
    2. RIC-939 race conditions in RMR → Abdulwahid
    3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
    4. RIC-915 dms_cli for installing xapp not working (raised by James)
    5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    7. RIC-897 SCTP connection fails with Viavi // update with workaround
    8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    9. RIC-894 long idle period (days) causes RMR connection breaks
    10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
      1. 2021-12-21: Trying to get bandwidth for this during F release.
    13. RIC-837 RMR is not forwarding messages from E2T to E2M
    14. RIC-835 → 2021-12-07 news from Viktor
    15. fixed: no new fixes
    16. anybody would like to get more familiar with RMR?

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

    1. The current platform deployment scripts might not be in line with O2 envisions
    2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    3. O2-D(MS) is relevant to RIC platform.
    4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    5. 2023-01-31: No news yet
    6. 2023-02-14 No news yet, Thoralf received e-mail on this from James. Still to check.
    7. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
  5. James:updates?
    1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
        1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
        2. Tacker-based deployment needs to be checked.
    2. 2023-02-14: no updates
    3. 2023-02-28: no updates (James did not participate).
  6. Sunil updates?
    1. 2023-02-28: no updates
  7. Subhash/Naman updates?
    1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
      1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
        1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
          1. Thoralf to create JIRA item for this
          2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
          3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
          4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
  8. Abhijit updates?
    1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
      1. Thoralf raised support request to LF. Reminders sent. Still no solution.
  9. H release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
      1. Sprint H release dev sprint 1: Feb-20´to Mar-12
      2. Sprint H release dev sprint 2: Mar-13 to Apr-2
      3. Sprint H release dev sprint 3: Apr-3 to Apr-23
      4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
      5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
  10. GRPC vs RMR
    1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2. 2023-01-31, 2023-02-14, 2023-02-28: no update
  11. Integration with AI/ML project: kserve_adapter
    1. data pipeline (Hoejoo's e-mail)
      1. 2023-01-31 not discussed in today's meeting
  12. Gunja and Sachin CapGemini) presented changes that were done for RIC subscription delete required as per RIC-851. Thoralf to start a mail thread with Nitin, Subhash, Gunja, Sachin on how xapps can be notified of subscription changes. link to the presentation
  13. RICAPP agenda: RICAPP Meetings.

2023-02-14 (Tuesday)

Recording: link to zoom recording

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

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

    1. The current platform deployment scripts might not be in line with O2 envisions
    2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    3. O2-D(MS) is relevant to RIC platform.
    4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    5. 2023-01-31: No news yet
    6. 2023-02-14 No news yet, Thoralf received e-mail on this from James. Still to check.
  5. Sunil still to discuss with other team members for other items from subteam-h
    1. 2023-02-14: Sunil provided list with four items.
  6. James:updates?
    1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
        1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
        2. Tacker-based deployment needs to be checked.
    2. 2023-02-14: not updates
  7. H release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
      1. Sprint H release dev sprint 1: Feb-20´to Mar-12
      2. Sprint H release dev sprint 2: Mar-13 to Apr-2
      3. Sprint H release dev sprint 3: Apr-3 to Apr-23
      4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
      5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
  8. GRPC vs RMR
    1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2. 2023-01-31: no update
    3. 2023-02-14: no update
  9. Johannes/Bryan: RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2023-01-31: Abhijit wanted to merge something. pls. contact Thoralf.
      1. no news from Johannes/Bryan
    2. 2023-02-14:
      1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
      2. Thoralf to raise support request to LF
  10. Integration with AI/ML project: kserve_adapter
    1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
      1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
        1. Thoralf to create JIRA item for this
        2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
        3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
    2. data pipeline (Hoejoo's e-mail)
      1. 2023-01-31 not discussed in today's meeting
  11. CapGemini to present to project meeting changes that were done for RIC subscription delete required
  12. RICAPP agenda: RICAPP Meetings.


2023-01-31 (Tuesday)

Recording: link to zoom recording

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

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

    1. The current platform deployment scripts might not be in line with O2 envisions
    2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    3. O2-D(MS) is relevant to RIC platform.
    4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    5. 2023-01-31: No news yet
  6. Sunil still to discuss with other team members for other items from subteam-h
    1. 2023-01-31: no news yet. HCL still in internal discussion on what open-src items to work on in 1H2023
  7. James:updates?
    1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
        1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
        2. Tacker-based deployment needs to be checked.
  8. H release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
      1. Sprint H release dev sprint 1: Feb-20´to Mar-12
      2. Sprint H release dev sprint 2: Mar-13 to Apr-2
      3. Sprint H release dev sprint 3: Apr-3 to Apr-23
      4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
      5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
  9. GRPC vs RMR
    1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2. 2023-01-31: no update
  10. Johannes/Bryan: RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2023-01-31: Abhijit wanted to merge something. pls. contact Thoralf.
      1. no news from Johannes/Bryan
  11. Integration with AI/ML project: kserve_adapter
    1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
      1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
        1. Thoralf to create JIRA item for this
        2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. BUt also ok if only in one.
    2. data pipeline (Hoejoo's e-mail)
      1. 2023-01-31 not discussed in today's meeting
  12. RICAPP agenda: RICAPP Meetings.


2023-01-17 (Tuesday)

Recording: link to zoom recording

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

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

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


2023-01-03 (Tuesday)

Recording: Link to zoom recording

Sunil kindly agreed to host also the RIC platform part of this week's project meeting.

We will discuss the plans for the H release in the next meeting. As before, items that were delayed from the previous release and leftover items are prime candidates to work on. Left overs: link

2022-12-06 (Tuesday)

Recording:  Link to zoom recording

The meeting was hosted by Sunil.

Updates on RICP.

  1. Updates (from Subhash)
    1. RIC-385: first part done defining the E2 messages in golang, but actual Reset implementation still needed.  Rest goes to release H
    2. RIC-714: dms Rest interface. Instructions still missing
    3. RIC-914+RIC-849: done (helm charts and jenkins job still coming)
    4. RIC-911: done
  2. Updates (from Sunil)
    1. RIC-860 and RIC-878 code for REST subscriptiopn API is now actively being worked on.
  3. Updates (from Johannes)
    1. still struggling with CI, but likely to "formally" release RMR part of RUST framework.
  4. RICAPP agenda: RICAPP Meetings.

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

  4. demo day? Suggestion: Dec-20. Add demo topic here: 2022-12-20 Release G

  5. Sunil still to discuss with other team members for other items from subteam-h
    1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
      1. RIC-860 + RIC-878
        1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05& 2022-07-19 update:  - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
        2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in
        3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
        4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
        5. 2022-04-26: still open
        6. 2022-05-11: expecting to finalize by May-27
        7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
        8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
        9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
        10. 2022-08-02: SUNIL SINGH to check any news on RIC-860 or RIC-878?
        11. 2022-08-16→2022-08-30->2022-09-13→2022-09-27: no update
        12. : some cleanup is needed first.
          1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
          2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
          3. test both if they are actually working
          4. 2022-08-30: team currently busy, but will pick up on this again soon
      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.
  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 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.
  7. G release content wrap up
    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)

    3. link to G Release summary. Try to finalize all work by Dec-6 so we can generate the release images in the week of Dec-6

  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.
    8. 2022-11-08: focus of Nokia proposal will be on scalability (xApps, #E2 connections)
    9. 2022-11-22: WG3 spec for RICAPI available in current train. Worth reading. Defines GRPC, but also SCTP+Protobuf interfaces.
  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
      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.
  10. Update from Samsung side
    1. news discussed in G release content section
  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-11-08 demo (5-10min)
    5. 2022-11-22. Thoralf to ask for status
  12. RICAPP agenda: RICAPP Meetings.

2022-11-08 (Tuesday)

Recording: link to zoom recording

...