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

Compare with Current View Page History

« Previous Version 699 Next »

Meeting Info

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

Zoom 1 Info:

UTC-timeevery 2nd Tuesday, check from calendar

https://zoom.us/j/9644759813

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

+358 341092129

Delhi (IST // UTC +5:30every 2nd Tuesday, check from calendarTODO


Other international numbers

World Time Zone Map

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

2023-10-24

Recording: TODO

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on 2023-09-26
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/11149 OK, go version update only
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/11234 OK, test case added for IPv6 tests
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11324 PK, test case updated
      4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11733 OK, generated code from API
      5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
  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 2023-05-23:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-1019 xapp-frame - incorrect removal of transmitted rmr message in unsuccessful case (Juha) → DONE
    2. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

    3. RIC-1016 e2t sctp_params structure may not be initialized properly

    4. RIC-1015 e2t too High default message size.

    5. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads.

    6. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

    7. RIC-1012 RMR not working in A1 mediator → DONE (Thoralf also released fixed image in ric-dep recipe of h-release)
    8. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
    9. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
    10. RIC-1001 RMR service should verify route tables - Alexandre will take a look
    11. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
    12. RIC-989 RMR (minor) security issue - Alexandre will take a look
    13. RIC-972 (Naman) URL for A1 mediator to align with spec.
    14. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    15. 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)
    16. RIC-915 dms_cli for installing xapp not working (raised by James)
    17. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    18. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    19. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    20. RIC-894 long idle period (days) causes RMR connection breaks
    21. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    22. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    23. 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.
    24. RIC-837 RMR is not forwarding messages from E2T to E2M
    25. RIC-835 → 2021-12-07 no news from Viktor
    26. fixed: RIC-1019, RIC-1012
  4. James: updates?
    1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
    2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
      1. ODU-high and near-RT RIC (currently using stub).
      2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
      3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
      4. James will check with Sunil on issues he has with the test cases
      5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar coudl be done with OSC.
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22, 2023-09-26 : could not participate
  6. Sunil updates (subteam-h)?
    1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-08-29: no news, other than Naman working on the operator implementation.
    2. 2023-09-12:
      1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
      2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
        1. Thoralf sent instructions to John → DONE
      3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
      4. Naman also works on the operator implementation
    3. 2023-09-26:
      1. kubernetes operator new repo needed or not?
        1. xapp deployment → appmgr or ricdms
        2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
      2. What happened to kserve adapter? → Subhash can check.
  8. Abhijit updates (subteam-ag) ?
    1. 2023-08-22: next release item discussed and RIC-979
    2. 2023-08-29:
      1. created RIC-1004 for release I item.
      2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
        1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
    3. 2023-09-12:
      1. changes related to registration API needed in xapp-frame (problem still to be thought of)
      2. something not working in github: IT-25974 - again related to github replication.
    4. 2023-09-26
      1. Abhijit presented his work on a single near RT RIC helm chart and bringing up the platform on minikube on Ubuntu 22.04. We decided to proceed with this.
      2. github action problem with master vs g release for replication → ticket.
      3. Abhijit wanted to provide a video for new way of ric deployment
    5. 2023-10-10:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0
  9. Cap Gemini updates (subteam-cg)? 
    1. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
      1. Ashish S. (CapGemini) presented this.
      2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
        1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
        2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
        3. additional latency comes only from guidance request
        4. xapp-framework could be extended to automatically do E2 guidance requests
    2. 2023-09-26:
      1. first step of new repo created, but still issues with initial files in repo. Thoralf raised request to LF: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26015 
    3. 2023-10-10:
      1. conflictmgr repo is now ready for commits: https://gerrit.o-ran-sc.org/r/admin/repos/ric-plt/conflictmgr,general
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
  11. Dhiraj (subteam-r)
    1. 2023-08-22:
      1. checking compliance/license issues
      2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
    2. 2023-08-29:
      1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes
  12. Alexandre (subteam-utfpr)
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
  13. Nokia (subteam-n)
    1. Sunil handles today's (Oct-10) meeting as Thoralf is on holiday
  14. I release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I 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. input for release candidates: left overs and generally open items, RSAC
    3. Sprint dates
      1. Sprint I release dev sprint 1: Aug-21 to Sep-10
      2. Sprint I release dev sprint 2: Sep-11 to Oct-1
      3. Sprint I release dev sprint 3: Oct-2 to Oct-22
      4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
    4. Plan (v03 as of 2023-08-18):
      1. I release plan moved to I release page.
  2. RICAPP agenda: RICAPP Meetings.


2023-10-10

no meeting as neither Thoralf nor Sunil were available to host the call

2023-09-26

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-09-26
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/11149 OK, go version update only
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/11234 OK, test case added for IPv6 tests
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11324 PK, test case updated
      4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11733 OK, generated code from API
      5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
  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 2023-05-23:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-1011 (Nokia fixes) E2 error with cause duplicate-error for all subscriptions requests after resource-limit failure - FIXED
    2. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
    3. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
    4. RIC-1001 RMR service should verify route tables - Alexandre will take a look
    5. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
    6. RIC-989 RMR (minor) security issue - Alexandre will take a look
    7. RIC-979 (Abhijit will close this one) Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
    8. RIC-972 (Naman) URL for A1 mediator to align with spec.
    9. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    10. 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)
    11. RIC-915 dms_cli for installing xapp not working (raised by James)
    12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    14. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    15. RIC-894 long idle period (days) causes RMR connection breaks
    16. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    17. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    18. 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.
    19. RIC-837 RMR is not forwarding messages from E2T to E2M
    20. RIC-835 → 2021-12-07 no news from Viktor
    21. fixed: RIC-1011, RIC-979
  4. James: updates?
    1. 2023-08-01:
      1. O2 integration with OSC RIC is still pending with WR.
      2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
    2. 2023-08-22:
      1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
        1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
        2. e.g., existing discussion with John
    3. 2023-08-29: no news
    4. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
    5. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
      1. ODU-high and near-RT RIC (currently using stub).
      2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
      3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
      4. James will check with Sunil on issues he has with the test cases
      5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar coudl be done with OSC.
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22, 2023-09-26 : could not participate
  6. Sunil updates (subteam-h)?
    1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
    2. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-08-01:
      1. E2AP v3.0 → we took a look at what changes are coming 
      2. A1 enhancements
      3. considering upgrade of ubuntu and k8s
      4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
      5. DMS delete PI
      6. E2 reset from ric to e2 node
    2. 2023-08-22: we discussed Jira item priority.
    3. 2023-08-29: no news, other than Naman working on the operator implementation.
    4. 2023-09-12:
      1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
      2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
        1. Thoralf sent instructions to John → DONE
      3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
      4. Naman also works on the operator implementation
    5. 2023-09-26:
      1. kubernetes operator new repo needed or not?
        1. xapp deployment → appmgr or ricdms
        2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
      2. What happened to kserve adapter? → Subhash can check.
  8. Abhijit updates (subteam-ag) ?
    1. 2023-05-23
        1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
        2. testing of subscriptions using hw-rust (facing the E2T problem)
    2. 2023-07-18: no news
    3. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
    4. 2023-08-22: next release item discussed and RIC-979
    5. 2023-08-29:
      1. created RIC-1004 for release I item.
      2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
        1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
    6. 2023-09-12:
      1. changes related to registration API needed in xapp-frame (problem still to be thought of)
      2. something not working in github: IT-25974 - again related to github replication.
    7. 2023-09-26
      1. Abhijit presented his work on a single near RT RIC helm chart and bringing up the platform on minikube on Ubuntu 22.04. We decided to proceed with this.
      2. github action problem with master vs g release for replication → ticket.
      3. Abhijit wanted to provide a video for new way of ric deployment
  9. Cap Gemini updates (subteam-cg)? 
    1. 2023-08-01

      1. Gunja to present conflict management design

      2. thinking about adding support for DU in E2T/E2M/RNIB in I release

    2. 2023-08-22:
      1. Gunja provided reviews for DU support. Nokia to reviewed and merged

        1.  https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and  https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node

      2. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
        1. Ashish S. (CapGemini) presented this.
        2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
          1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
          2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
          3. additional latency comes only from guidance request
          4. xapp-framework could be extended to automatically do E2 guidance requests
    3. 2023-09-26:
      1. first step of new repo created, but still issues with initial files in repo. Thoralf raised request to LF: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26015 
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
    5. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
  11. Dhiraj (subteam-r)
    1. 2023-07-18: IPv6 changes to come as review
    2. 2023-08-01: working on it.
    3. 2023-08-22:
      1. checking compliance/license issues
      2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
    4. 2023-08-29:
      1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes
  12. Alexandre (subteam-utfpr)
    1. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
    2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    3. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
  13. Nokia (subteam-n)
    1. 2023-08-22: want to work on RIC-997
    2. 2023-09-12: Thoralf did changes to readthedocs in all near-RT RIC repos. LF informed (link) these changes are needed because some configuration parameters are being removed. No further changes needed due to this. Example: https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11747. Note, though, that some repos don't currently generate read-the-docs documention. For the "A1" example, though you see a new documentation version in this URL: https://readthedocs.org/projects/o-ran-sc-ric-plt-a1/builds/
    3. Thoralf on holiday on Oct-10. Sunil?
  14. I release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I 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. input for release candidates: left overs and generally open items, RSAC
    3. Sprint dates
      1. Sprint I release dev sprint 1: Aug-21 to Sep-10
      2. Sprint I release dev sprint 2: Sep-11 to Oct-1
      3. Sprint I release dev sprint 3: Oct-2 to Oct-22
      4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
    4. Plan (v03 as of 2023-08-18):
      1. I release plan moved to I release page.

      2. E2 enhancements, incl. conflict mgmt.

        1. RIC-993 (CG): Near-RT RIC conflict management (*)

        2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB

        3. RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)

        4. RIC-994 (S): Support for E2APv3.0

        5. RIC-995 (S): Support for RIC Query

        6. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)

        7. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this)

        8. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup

        9. RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1

      3. Other

        1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))

        2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))

        3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)

        4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR 

        5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces

        6. RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support
  2. RICAPP agenda: RICAPP Meetings.

2023-09-12

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/xapp-frame/+/10923 OK, module version updates only
  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 2023-05-23:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-1011 (Nokia fixes) E2 error with cause duplicate-error for all subscriptions requests after resource-limit failure
    2. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
    3. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
    4. RIC-1001 RMR service should verify route tables - Alexandre will take a look
    5. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
    6. RIC-989 rmr (minor) security issue - Alexandre will take a look
    7. RIC-979 (Abhijit will close this one) Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
    8. RIC-972 (Naman) URL for A1 mediator to align with spec.
    9. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    10. 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)
    11. RIC-915 dms_cli for installing xapp not working (raised by James)
    12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    14. RIC-897 SCTP connection fails with Viavi // update with workaround → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)
    15. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    16. RIC-894 long idle period (days) causes RMR connection breaks
    17. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    18. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    19. 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.
    20. RIC-837 RMR is not forwarding messages from E2T to E2M
    21. RIC-835 → 2021-12-07 no news from Viktor
    22. fixed: ...
  4. James: updates?
    1. 2023-08-01:
      1. O2 integration with OSC RIC is still pending with WR.
      2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
    2. 2023-08-22:
      1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
        1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
        2. e.g., existing discussion with John
    3. 2023-08-29: no news
    4. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22 : could not participate
  6. Sunil updates (subteam-h)?
    1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
    2. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-08-01:
      1. E2AP v3.0 → we took a look at what changes are coming 
      2. A1 enhancements
      3. considering upgrade of ubuntu and k8s
      4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
      5. DMS delete PI
      6. E2 reset from ric to e2 node
    2. 2023-08-22: we discussed Jira item priority.
    3. 2023-08-29: no news, other than Naman working on the operator implementation.
    4. 2023-09-12:
      1. We had a meeting with John and Denis on non-rt RIC compatibilty. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
      2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
        1. Thoralf sent instructions to John
      3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
      4. Naman also works on the operator implementation
  8. Abhijit updates (subteam-ag) ?
    1. 2023-05-23
        1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
        2. testing of subscriptions using hw-rust (facing the E2T problem)
    2. 2023-07-18: no news
    3. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
    4. 2023-08-22: next release item discussed and RIC-979
    5. 2023-08-29:
      1. created RIC-1004 for release I item.
      2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
        1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
    6. 2023-09-12:
      1. changes related to registration API needed in xapp-frame (problem still to be thought of)
      2. something not working in github: IT-25974 - again related to github replication.
  9. Cap Gemini updates (subteam-cg)? 
    1. 2023-08-01

      1. Gunja to present conflict management design

      2. thinking about adding support for DU in E2T/E2M/RNIB in I release

    2. 2023-08-22:
      1. Gunja provided reviews for DU support. Nokia to reviewed and merged

        1.  https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and  https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node

      2. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
        1. Ashish S. (CapGemini) presented this.
        2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
          1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
          2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
          3. additional latency comes only from guidance request
          4. xapp-framework could be extended to automatically do E2 guidance requests
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
    5. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
  11. Dhiraj (subteam-r)
    1. 2023-07-18: IPv6 changes to come as review
    2. 2023-08-01: working on it.s
    3. 2023-08-22:
      1. checking compliance/license issues
      2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
    4. 2023-09-29:
      1. got clarity on license issues and now waiting for internal approval.
  12. Alexandre (subteam-utfpr)
    1. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
    2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
  13. Nokia (subteam-n)
    1. 2023-08-22: want to work on RIC-997
    2. 2023-09-12: Thoralf did changes to readthedocs in all near-RT RIC repos. LF informed (link) these changes are needed because some configuration parameters are being removed. No further changes needed due to this. Example: https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11747. Note, though, that some repos don't currently generate read-the-docs documention. For the "A1" example, though you see a new documentation version in this URL: https://readthedocs.org/projects/o-ran-sc-ric-plt-a1/builds/
  14. I release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I 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. input for release candidates: left overs and generally open items, RSAC
    3. Sprint dates
      1. Sprint I release dev sprint 1: Aug-21 to Sep-10
      2. Sprint I release dev sprint 2: Sep-11 to Oct-1
      3. Sprint I release dev sprint 3: Oct-2 to Oct-22
      4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
    4. Plan (v03 as of 2023-08-18):

      1. E2 enhancements, incl. conflict mgmt.

        1. RIC-993 (CG): Near-RT RIC conflict management (*)

        2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB

        3. RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)

        4. RIC-994 (S): Support for E2APv3.0

        5. RIC-995 (S): Support for RIC Query

        6. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)

        7. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this)

        8. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup

        9. RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1

      2. Other

        1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))

        2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))

        3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)

        4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR 

        5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces

        6. RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support
  2. RICAPP agenda: RICAPP Meetings.


2023-08-29 (back to normal week, therefore only 1 week after previous meeting)

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/xapp-frame/+/10923 OK, module version updates only
  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 2023-05-23:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-1002 Abnormal signaling process cause E2Term crash (this could be a security issue)
    2. RIC-1001 RMR service should verify route tables.
    3. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
    4. RIC-989 rmr (minor) security issue - Alexandre will take a look
    5. RIC-979 Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
    6. RIC-972 URL for A1 mediator to align with spec.
    7. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    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 → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)
    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 no news from Viktor
    20. fixed: ...
  4. James: updates?
    1. 2023-08-01:
      1. O2 integration with OSC RIC is still pending with WR.
      2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
    2. 2023-08-22:
      1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
        1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
        2. e.g., existing discussion with John
    3. 2023-08-29: no news
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22 : could not participate
  6. Sunil updates (subteam-h)?
    1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-08-01:
      1. E2AP v3.0 → we took a look at what changes are coming 
      2. A1 enhancements
      3. considering upgrade of ubuntu and k8s
      4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
      5. DMS delete PI
      6. E2 reset from ric to e2 node
    2. 2023-08-22: we discussed Jira item priority.
    3. 2023-08-29: no news, other than Naman working on the operator implementation.
  8. Abhijit updates (subteam-ag) ?
    1. 2023-05-23
        1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
        2. testing of subscriptions using hw-rust (facing the E2T problem)
    2. 2023-07-18: no news
    3. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
    4. 2023-08-22: next release item discussed and RIC-979
    5. 2023-08-29:
      1. created RIC-1004 for release I item.
      2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
        1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
  9. Cap Gemini updates (subteam-cg)? 
    1. 2023-08-01

      1. Gunja to present conflict management design

      2. thinking about adding support for DU in E2T/E2M/RNIB in I release

    2. 2023-08-22:
      1. Gunja provided reviews for DU support. Nokia to reviewed and merged

        1.  https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and  https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node

      2. Conflict management status? Thoralf checked by e-mail after the meeting. Presentation by Gunja planned for Sep-12
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
    5. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
  11. Dhiraj (subteam-r)
    1. 2023-07-18: IPv6 changes to come as review
    2. 2023-08-01: working on it.
    3. 2023-08-22:
      1. checking compliance/license issues
      2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
    4. 2023-09-29:
      1. got clarity on license issues and now waiting for internal approval.
  12. Alexandre (subteam-utfpr)
    1. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
    2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
  13. Nokia (subteam-n)
    1. 2023-08-22: want to work on RIC-997
  14. I release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I 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. input for release candidates: left overs and generally open items, RSAC
    3. Sprint dates
      1. Sprint I release dev sprint 1: Aug-21 to Sep-10
      2. Sprint I release dev sprint 2: Sep-11 to Oct-1
      3. Sprint I release dev sprint 3: Oct-2 to Oct-22
      4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
    4. Plan (v03 as of 2023-08-18):

      1. E2 enhancements, incl. conflict mgmt.

        1. RIC-993 (CG): Near-RT RIC conflict management (*)

        2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB

        3. RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)

        4. RIC-994 (S): Support for E2APv3.0

        5. RIC-995 (S): Support for RIC Query

        6. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)

        7. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this)

        8. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup

        9. RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1

      2. Other

        1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))

        2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))

        3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)

        4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR 

        5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces

        6. RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support
  2. RICAPP agenda: RICAPP Meetings.

2023-08-22 (exceptionally one week later than normal)

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/xapp-frame/+/10923 OK, module version updates only
  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 2023-05-23:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-1002 Abnormal signaling process cause E2Term crash (this could be a security issue)
    2. RIC-1001 RMR service should verify route tables.
    3. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
    4. RIC-989 rmr (minor) security issue - Alexandre will take a look
    5. new: RIC-988 CLOSED e2 component configuration → Duplicate of fix https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=commit;h=d2f1a29d3f1cc779045148a82729f644e6110776 
    6. RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile DONE
    7. RIC-979 Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
    8. RIC-972 URL for A1 mediator to align with spec.
    9. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    10. 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)
    11. RIC-915 dms_cli for installing xapp not working (raised by James)
    12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    14. RIC-897 SCTP connection fails with Viavi // update with workaround → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)
    15. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    16. RIC-894 long idle period (days) causes RMR connection breaks
    17. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    18. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    19. 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.
    20. RIC-837 RMR is not forwarding messages from E2T to E2M
    21. RIC-835 → 2021-12-07 no news from Viktor
    22. fixed: RIC-986
  4. Himanshu: demo on the OAI CU <--> OSC RIC integration
    1. Himanshu presented the integration of SDRAN-fork of OAI (with SDRAN E2 support added) and how the CU connects to OSC RIC
  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
    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
    5. 2023-05-09:
      1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
        1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
        2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
        3. Input from other subprojects, incl. our near-RT RIC project?
      2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
    6. 2023-05-23 → no news
    7. 2023-07-18: James' focus is currently on OSC & OAI cooperation. Current thinking is to use Taiwan lab to host OAI -based installation over E2AP (2.0). See also https://openairinterface.org/mosaic5g/
      1. usage of robot test cases (from it/test) is still something that James is thinking about.
      2. Himanshu commented that he tried OAI CU/DU with OSC RIC and KPM xApp.
    8. 2023-08-01:
      1. O2 integration with OSC RIC is still pending with WR.
      2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
    9. 2023-08-22:
      1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
        1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
        2. e.g., existing discussion with John
  6. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22 : could not participate
  7. Sunil updates (subteam-h)?
    1. 2023-07-18, 2023-08-01, 2023-08-22: no news
  8. Subhash/Naman updates (subteam-s) ?
    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
    6. 2023-05-09:
      1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
      2. A1 bug fixes being almost ready.
      3. A1 mediator nanobot might be delayed.
      4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
    7. 2023-05-23
      1. E2 reset (from E2 node): done
      2. KServe adapter still being worked on.
      3. nanobot integration still being worked on.
    8. 2023-07-18: no news, planning for I release
    9. 2023-08-01:
      1. E2AP v3.0 → we took a look at what changes are coming 
      2. A1 enhancements
      3. considering upgrade of ubuntu and k8s
      4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
      5. DMS delete PI
      6. E2 reset from ric to e2 node
    10. 2023-08-22: we discussed Jira item priority.
  9. Abhijit updates (subteam-ag) ?
    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.
    6. 2023-05-09
      1. RIC-977 (subscription API) - pls. merge.
      2. RIC-978 pls. try to complete during this week.
      3. issues with E2 simulator → to get in contact with Naman and Subhash
    7. 2023-05-23
      1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
      2. testing of subscriptions using hw-rust (facing the E2T problem)
    8. 2023-07-18: no news
    9. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
    10. 2023-08-22: next release item discussed and RIC-979
  10. Cap Gemini updates (subteam-cg)? 
    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, 2023-05-23: no news.
    3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
    4. 2023-07-18: Cap Gemini (Gunja) conflict management presentation planned for end of July
    5. 2023-08-01

      1. Gunja to present conflict management design

      2. thinking about adding support for DU in E2T/E2M/RNIB in I release

    6. 2023-08-22:
      1. Gunja provided reviews for DU support. Nokia to reviewed and merged

        1.  https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and  https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node

      2. conflit management status?
  11. Himanshu (subteam-gs) would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
  12. Dhiraj (subteam-r)
    1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
    2. 2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed).
    3. 2023-07-18: IPv6 changes to come as review
    4. 2023-08-01: working on it.
    5. 2023-08-22:
      1. checking compliance/license issues
      2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
  13. Alexandre (subteam-utfpr)
    1. 2023-05-23: no news
    2. 2023-06-06:
      1. fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.
      2. seems also to be a bug in interface name solution in RMR. Remember to create a JIRA item (RIC-987)
    3. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
  14. Nokia (subteam-n)
    1. 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, 2023-05-09, 2023-05-23, 2023-07-18: no update
    2. 2023-08-22: want to work on RIC-997
  15. I release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I 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. input for release candidates: left overs and generally open items, RSAC
    3. Sprint dates
      1. Sprint I release dev sprint 1: Aug-21 to Sep-10
      2. Sprint I release dev sprint 2: Sep-11 to Oct-1
      3. Sprint I release dev sprint 3: Oct-2 to Oct-22
      4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
    4. Plan (v03 as of 2023-08-18): link

      1. E2 enhancements, incl. conflict mgmt.

        1. RIC-993 (CG): Near-RT RIC conflict management (*)

        2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB

        3. RIC-994 (S): Support for E2APv3.0

        4. RIC-995 (S): Support for RIC Query

        5. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)

        6. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (dhiraj interested as reviewer, but we had earlier discussion on this)

        7. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup

        8. RIC-963 (GS)modify src code to be more lenient in ordering of IEs in ASN.1

      2. Other

        1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))

        2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))

        3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)

        4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR 

        5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces

        6. Abhijit will create issue and send e-mail
  2. RICAPP agenda: RICAPP Meetings.

2023-08-01

Recording: link to zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on 2023-04-11
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only
  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 2023-05-23:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. new: RIC-991 rmr related (not a duplicate) - Alexandre will take a look
    2. new: RIC-989 rmr (minor) security issue - Alexandre will take a look
    3. new: RIC-988 CLOSED e2 component configuration → Duplicate of fix https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=commit;h=d2f1a29d3f1cc779045148a82729f644e6110776 
    4. RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile
    5. RIC-979 Decode Error with e2sim on e2term Pod - AP-Subhash/Naman add logs
    6. RIC-972 URL for A1 mediator to align with spec.
    7. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    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 no news from Viktor
    20. fixed:
  4. Himanshu: demo on the OAI CU <--> OSC RIC integration
    1. Himanshu presented the integration of SDRAN-fork of OAI (with SDRAN E2 support added) and how the CU connects to OSC RIC
  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
    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
    5. 2023-05-09:
      1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
        1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
        2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
        3. Input from other subprojects, incl. our near-RT RIC project?
      2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
    6. 2023-05-23 → no news
    7. 2023-07-18: James' focus is currently on OSC & OAI cooperation. Current thinking is to use Taiwan lab to host OAI -based installation over E2AP (2.0). See also https://openairinterface.org/mosaic5g/
      1. usage of robot test cases (from it/test) is still something that James is thinking about.
      2. Himanshu commented that he tried OAI CU/DU with OSC RIC and KPM xApp.
    8. 2023-08-01:
      1. O2 integration with OSC RIC is still pending with WR.
      2. OAI was discussed in last week's TOC, and it seems OAI license is not blokcer for using OAI in OSC-labs.
  6. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-04-25:
      1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
      2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
      3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
    2. 2023-05-09
      1. question related to O1 (for stats handling without Vespa) - see RIC-798
    3. 2023-05-23
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11127?usp=search and two more minor ones to be reviewed Naman/Subhash during this week
      2. E2 → Alexandre to review - 2023-06-06: merged
    4. 2023-06-06: Prashant posted in O-RAN WG3 on O1 a question related on the why of notifications + SFTP. No reply yet.
      1. 2023-07-18: feedback was that this is a 3GPP issue. Not further following up on this.
    5. 2023-06-18: Thoralf-AP: remove all items above as they are done
  7. Sunil updates (subteam-h)?
    1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09: no news
    2. 2023-05-23: all items from HCL to be moved to I release.
    3. 2023-07-18, 2023-08-01: no news
  8. Subhash/Naman updates (subteam-s) ?
    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
    6. 2023-05-09:
      1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
      2. A1 bug fixes being almost ready.
      3. A1 mediator nanobot might be delayed.
      4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
    7. 2023-05-23
      1. E2 reset (from E2 node): done
      2. KServe adapter still being worked on.
      3. nanobot integration still being worked on.
    8. 2023-07-18: no news, planning for I release
    9. 2023-08-01:
      1. E2AP v3.0 → we took a look at what changes are coming
      2. A1 enhancements
      3. considering upgrade of ubuntu and k8s
      4. deploying RIC and xapps using k8S operator
      5. DMS delete PI
      6. E2 reset from ric to e2 node
  9. Abhijit updates (subteam-ag) ?
    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.
    6. 2023-05-09
      1. RIC-977 (subscription API) - pls. merge.
      2. RIC-978 pls. try to complete during this week.
      3. issues with E2 simulator → to get in contact with Naman and Subhash
    7. 2023-05-23
      1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
      2. testing of subscriptions using hw-rust (facing the E2T problem)
    8. 2023-07-18: no news
    9. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
  10. Cap Gemini updates (subteam-cg)? 
    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, 2023-05-23: no news.
    3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
    4. 2023-07-18: Cap Gemini (Gunja) conflict management presentation planned for end of July
    5. 2023-08-01

      1. Gunja to present conflict management design

      2. thinking about adding support for DU in E2T/E2M/RNIB in I release

  11. Himanshu (subteam-gs) would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-01: feedback from Anssi on submgr received and incorporating these changes.
  12. Dhiraj (subteam-r)
    1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
    2. 2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed).
    3. 2023-07-18: IPv6 changes to come as review
    4. 2023-08-01: working on it.
  13. Alexandre (subteam-utfpr)
    1. 2023-05-23: no news
    2. 2023-06-06:
      1. fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.
      2. seems also to be a bug in interface name solution in RMR. Remember to create a JIRA item
  14. Nokia(subteam-n)
    1. 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, 2023-05-09, 2023-05-23, 2023-07-18: no update
  15. I release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I 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. input for release candidates: left overs and generally open items, RSAC
    3. Sprint dates
      1. Sprint G release dev sprint 1: Aug-21 to Sep-10
      2. Sprint G release dev sprint 2: Sep-11 to Oct-1
      3. Sprint G release dev sprint 3: Oct-2 to Oct-22
      4. Sprint G release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
    4. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
    5. 2023-07-18: Naman proposed E2APv3.0 update and some A1 changes
      1. E2APv3.0 changes for existing functionality (possible item for release I) - to be sent by e-mail.
        1. Dhiraj to be involved.
      2. Changes for A1 to achieve spec compliance (for the URL change we could do it in a backwards compatible way)
      3. E2 Reset from RIC to RAN
    6. 2023-07-18: (Dhiraj) IPv6 changes
    7. 2023-07-18: (Thoralf) RIC Error indication during E2 setup
    8. 2023-07-18: (Dhiraj) (not committed, but can prepare a list on where dynamic log level change is missing)
    9. 2023-08-01: Summary of plans:

      1. E2-related

        1. Near-RT RIC conflict management

        2. Adding support for DU in E2T/E2M/RNIB

        3. Support for E2APv3.0

        4. Support for RIC Query

        5. Support for Subscription modifications

        6. Support for E2 reset from RIC to RAN

        7. Handling of RIC Error indication _during_ E2 setup.

        8. RIC-963 modify src code to be more lenient in ordering of IEs in ASN.1

      2. Other

        1. K8S operators for deploying xApps

        2. A1 alignment with A1AP (still under investigation. Minimum is using correct URL)

        3. DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli)

        4. IPv6 support for RMR

        5. Support for only-IPv6 in RIC-internal interfaces

  16. RICAPP agenda: RICAPP Meetings.

2023-07-18

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/xapp-frame/+/10923 OK, module version updates only
  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 2023-05-23:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. new: RIC-989 rmr (minor) security issue
    2. new: RIC-988 CLOSED e2 component configuration → Duplicate of fix https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=commit;h=d2f1a29d3f1cc779045148a82729f644e6110776 
    3. RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile
    4. RIC-979 Decode Error with e2sim on e2term Pod - AP-Subhash/Naman add logs
    5. RIC-972 URL for A1 mediator to align with spec.
    6. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    7. 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)
    8. RIC-915 dms_cli for installing xapp not working (raised by James)
    9. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    10. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    11. RIC-897 SCTP connection fails with Viavi // update with workaround
    12. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    13. RIC-894 long idle period (days) causes RMR connection breaks
    14. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    15. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    16. 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.
    17. RIC-837 RMR is not forwarding messages from E2T to E2M
    18. RIC-835 → 2021-12-07 no news from Viktor
    19. fixed:
  4. 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
    5. 2023-05-09:
      1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
        1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
        2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
        3. Input from other subprojects, incl. our near-RT RIC project?
      2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
    6. 2023-05-23 → no news
    7. 2023-07-18: James' focus is currently on OSC & OAI cooperation. Current thinking is to use Taiwan lab to host OAI -based installation over E2AP (2.0). See also https://openairinterface.org/mosaic5g/
      1. usage of robot test cases (from it/test) is still something that James is thinking about.
      2. Himanshu commented that he tried OAI CU/DU with OSC RIC and KPM xApp.
  5. Prashant's work in near-RT RIC
    1. 2023-04-25:
      1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
      2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
      3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
    2. 2023-05-09
      1. question related to O1 (for stats handling without Vespa) - see RIC-798
    3. 2023-05-23
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11127?usp=search and two more minor ones to be reviewed Naman/Subhash during this week
      2. E2 → Alexandre to review - 2023-06-06: merged
    4. 2023-06-06: Prashant posted in O-RAN WG3 on O1 a question related on the why of notifications + SFTP. No reply yet.
      1. 2023-07-18: feedback was that this is a 3GPP issue. Not further following up on this.
    5. 2023-06-18: Thoralf-AP: remove all items above as they are done
  6. Sunil updates?
    1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09: no news
    2. 2023-05-23: all items from HCL to be moved to I release.
    3. 2023-07-18: 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
    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
    6. 2023-05-09:
      1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
      2. A1 bug fixes being almost ready.
      3. A1 mediator nanobot might be delayed.
      4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
    7. 2023-05-23
      1. E2 reset (from E2 node): done
      2. KServe adapter still being worked on.
      3. nanobot integration still being worked on.
    8. 2023-07-18: no news, planning for I release
  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
    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.
    6. 2023-05-09
      1. RIC-977 (subscription API) - pls. merge.
      2. RIC-978 pls. try to complete during this week.
      3. issues with E2 simulator → to get in contact with Naman and Subhash
    7. 2023-05-23
      1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
      2. testing of subscriptions using hw-rust (facing the E2T problem)
    8. 2023-07-18: no news
  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, 2023-04-11, 2023-04-25, 2023-05-23: no news.
    3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
    4. 2023-07-18: Cap Gemini (Gunja) conflict management presentation planned for end of July
  10. Himanshu would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
  11. Dhiraj
    1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
    2. 2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed).
    3. 2023-07-18: IPv6 changes to come as review
  12. Alexandre
    1. 2023-05-23: no news
    2. 2023-06-06:
      1. fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.
      2. seems also to be a bug in interface name solution in RMR. Remember to cretae a JIRA item
  13. I release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I 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. input for release candidates: left overs and generally open items, RSAC
    3. Sprint dates
      1. Sprint G release dev sprint 1: Aug-21 to Sep-10
      2. Sprint G release dev sprint 2: Sep-11 to Oct-1
      3. Sprint G release dev sprint 3: Oct-2 to Oct-22
      4. Sprint G release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint G release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
    4. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
    5. 2023-07-18: Naman proposed E2APv3.0 update and some A1 changes
      1. E2APv3.0 changes for existing functionality (possible item for release I) - to be sent by e-mail.
        1. Dhiraj to be involved.
      2. Changes for A1 to achieve spec compliance (for the URL change we could do it in a backwards compatible way)
      3. E2 Reset from RIC to RAN
    6. 2023-07-18: (Dhiraj) IPv6 changes
    7. 2023-07-18: (Thoralf) RIC Error indication during E2 setup
    8. 2023-07-18: (Dhiraj) (not committed, but can prepare a list on where dynamic log level change is missing)
  14. 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, 2023-05-09, 2023-05-23, 2023-07-18: no update
  15. RICAPP agenda: RICAPP Meetings.

2023-07-04

Since neither Thoralf nor Sunil can host this meeting it is cancelled.

2023-06-20

we did the demo meeting in the timeslot: link

2023-06-06

Recording: partial-only: 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/xapp-frame/+/10923 OK, module version updates only
  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 2023-05-23:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile
    2. RIC-979 Decode Error with e2sim on e2term Pod - AP-Subhash/Naman add logs
    3. RIC-974 done: Errors running example ping/pong application in `xapp-frame-py`, incl. new release of builder image. Can be closed after that.
    4. RIC-972 URL for A1 mediator to align with spec.
    5. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    6. 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)
    7. RIC-915 dms_cli for installing xapp not working (raised by James)
    8. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    9. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    10. RIC-897 SCTP connection fails with Viavi // update with workaround
    11. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    12. RIC-894 long idle period (days) causes RMR connection breaks
    13. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    14. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    15. 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.
    16. RIC-837 RMR is not forwarding messages from E2T to E2M
    17. RIC-835 → 2021-12-07 no news from Viktor
    18. fixed: RIC-974, RIC-980, RIC-981
  4. H release status page: H Release#Near-Real-timeRANIntelligentControllerPlatform(E2Interface)(RICPLT) → 2023-06-06 we checked the status
    1. Thoralf expects everything to be ready by Jun-22
  5. O-RAN SC end of release of near-RT RIC: Demo scheduled for 2 weeks from now: 2023-06-20 Release H
  6. Demo videos (Prashant, Subhash, Gunja) for O-RAN face-to-face to be ready this week: upload video here: Material for O-RAN June f2f in Osaka  Jinri will combine

  7. 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, 2023-05-09, 2023-05-23: no news
  8. 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
    5. 2023-05-09:
      1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
        1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
        2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
        3. Input from other subprojects, incl. our near-RT RIC project?
      2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
    6. 2023-05-23 → no news
  9. Prashant's work in near-RT RIC
    1. 2023-04-25:
      1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
      2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
      3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
    2. 2023-05-09
      1. question related to O1 (for stats handling without Vespa) - see RIC-798
    3. 2023-05-23
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11127?usp=search and two more minor ones to be reviewed Naman/Subhash during this week
      2. E2 → Alexandre to review - 2023-06-06: merged
    4. 2023-06-06: Prashant posted in O-RAN WG3 on O1 a question related on the why of notifications + SFTP. No reply yet.
  10. Sunil updates?
    1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09: no news
    2. 2023-05-23: all items from HCL to be moved to I release.
  11. 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
    6. 2023-05-09:
      1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
      2. A1 bug fixes being almost ready.
      3. A1 mediator nanobot might be delayed.
      4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
    7. 2023-05-23
      1. E2 reset (from E2 node): done
      2. KServe adapter still being worked on.
      3. nanobot integration still being worked on.
  12. 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.
    6. 2023-05-09
      1. RIC-977 (subscription API) - pls. merge.
      2. RIC-978 pls. try to complete during this week.
      3. issues with E2 simulator → to get in contact with Naman and Subhash
    7. 2023-05-23
      1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
      2. testing of subscriptions using hw-rust (facing the E2T problem)
  13. 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, 2023-05-23: no news.
    3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
  14. Himanshu would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
  15. Dhiraj
    1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
    2. 2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed). 
  16. Alexandre
    1. 2023-05-23: no news
    2. 2023-06-06:
      1. fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.
      2. seems also to be a bug in interface name solution in RMR. Remember to cretae a JIRA item.
  17. 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
  18. 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, 2023-05-09, 2023-05-23: no update
  19. RICAPP agenda: RICAPP Meetings.


2023-05-23

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/xapp-frame/+/10923 OK, module version updates only
  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 2023-05-23:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-980 new-and-doneNaman Reading Configuration for rmr from config file
    2. RIC-981 new-and-doneNaman Missing health check checking the Db connection through SDL even when the a1 name space is not present in db
    3. RIC-979 Decode Error with e2sim on e2term Pod - AP-Subhash/Naman add logs
    4. RIC-974 done: Errors running example ping/pong application in `xapp-frame-py`, incl. new release of builder image. Can be closed after that.
    5. RIC-972 URL for A1 mediator to align with spec.
    6. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    7. 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)
    8. RIC-915 dms_cli for installing xapp not working (raised by James)
    9. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    10. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    11. RIC-897 SCTP connection fails with Viavi // update with workaround
    12. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    13. RIC-894 long idle period (days) causes RMR connection breaks
    14. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    15. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    16. 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.
    17. RIC-837 RMR is not forwarding messages from E2T to E2M
    18. RIC-835 → 2021-12-07 no news from Viktor
    19. fixed: RIC-974, RIC-980, RIC-981

  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, 2023-05-09, 2023-05-23: no news
  5. Prashant's work in near-RT RIC
    1. 2023-04-25:
      1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
      2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
      3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
    2. 2023-05-09
      1. question related to O1 (for stats handling without Vespa) - see RIC-798
    3. 2023-05-23
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11127?usp=search and two more minor ones to be reviewed Naman/Subhash during this week
      2. E2 → Alexandre to review
  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
    5. 2023-05-09:
      1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
        1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
        2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
        3. Input from other subprojects, incl. our near-RT RIC project?
      2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
    6. 2023-05-23 → no news
  7. Sunil updates?
    1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09: no news
    2. 2023-05-23: all items from HCL to be moved to I release.
  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
    6. 2023-05-09:
      1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
      2. A1 bug fixes being almost ready.
      3. A1 mediator nanobot might be delayed.
      4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
    7. 2023-05-23
      1. E2 reset (from E2 node): done
      2. KServe adapter still being worked on.
      3. nanobot integration still being worked on.
  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.
    6. 2023-05-09
      1. RIC-977 (subscription API) - pls. merge.
      2. RIC-978 pls. try to complete during this week.
      3. issues with E2 simulator → to get in contact with Naman and Subhash
    7. 2023-05-23
      1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
      2. testing of subscriptions using hw-rust (facing the E2T problem)
  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, 2023-05-23: no news.
    3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
  11. Himanshu would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
  12. Dhiraj
    1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
  13. Alexandre
    1. 2023-05-23: no news
  14. 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
  15. 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, 2023-05-09, 2023-05-23: no update
  16. RICAPP agenda: RICAPP Meetings.


2023-05-09

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/xapp-frame-rust/+/10906 OK tests included
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/10907 OK, tests included
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11023 OK, tests included
      4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10918 OK, as files are generated
  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-974 Errors running example ping/pong application in `xapp-frame-py`, incl. new release of builder image. Can be closed after that.
    2. RIC-972 URL for A1 mediator to align with spec.
    3. DONE: RIC-971 Fix potential segfaults and double free corruption (in E2T)
    4. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    5. 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)
    6. RIC-915 dms_cli for installing xapp not working (raised by James)
    7. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    8. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    9. RIC-897 SCTP connection fails with Viavi // update with workaround
    10. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    11. RIC-894 long idle period (days) causes RMR connection breaks
    12. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    13. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    14. 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.
    15. RIC-837 RMR is not forwarding messages from E2T to E2M
    16. RIC-835 → 2021-12-07 no news from Viktor
    17. fixed: RIC-971

  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, 2023-05-09: no news
  5. Prashant's work in near-RT RIC
    1. 2023-04-25:
      1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
      2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
      3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
    2. 2023-05-09
      1. question related to O1 (for stats handling without Vespa) - see RIC-798
  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
    5. 2023-05-09:
      1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
        1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
        2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
        3. Input from other subprojects, incl. our near-RT RIC project?
      2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
  7. Sunil updates?
    1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25: no news
    2. 2023-05-09 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
    6. 2023-05-09:
      1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
      2. A1 bug fixes being almost ready.
      3. A1 mediator nanobot might be delayed.
      4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
  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.
    6. 2023-05-09
      1. RIC-977 (subscription API) - pls. merge.
      2. RIC-978 pls. try to complete during this week.
      3. issues with E2 simulator → to get in contact with Naman and Subhash
  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.
    3. 2023-05-09 no news.
  11. Himanshu would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
  12. 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
  13. 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, 2023-05-09: no update
  14. RICAPP agenda: RICAPP Meetings.

Older meeting minutes

check from here: Project meetings (old)



  • No labels