Latest meeting minutes

Broken links to meeting recordings

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

2023-10-24

Recording: link to zoom recording

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 OK, 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)
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
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
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 could be done with OSC.
3. 2023-10-24
  1. updates from O-RAN f-2-f:
    1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
    2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
      1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
      2. more discussion coming at the joint OSC/OAI workshop in Boston
    3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
  2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22, 2023-09-26 : could not participate
Sunil updates (subteam-h)?
1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
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.
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 → DONE~~
  3. ~~Abhijit wanted to provide a video for new way of ric deployment (2023-10-24: did not find time to finally do this)~~
5. 2023-10-24:
  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 → still to be made 1.0.0
  2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743
  3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it.
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. 2~~023-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
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".
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
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
Nokia (subteam-n)
1. ...
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.
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

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)
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
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
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.
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22, 2023-09-26 : could not participate
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.
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.
Abhijit updates (subteam-ag) ?
1. ~~2023-05-23~~
  1. 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
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
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".
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
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
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?
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~~
RICAPP agenda: RICAPP Meetings.

2023-09-12

Recording: link to zoom recording

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
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
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: ...
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.
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22 : could not participate
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.
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
Abhijit updates (subteam-ag) ?
1. 2023-05-23
  1. 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.
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
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".
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.
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
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/
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
RICAPP agenda: RICAPP Meetings.

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

Recording: link to zoom recording

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
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
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: ...
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
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22 : could not participate
Sunil updates (subteam-h)?
1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
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.
Abhijit updates (subteam-ag) ?
1. 2023-05-23
  1. 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
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
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".
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.
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
Nokia (subteam-n)
1. 2023-08-22: want to work on RIC-997
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
RICAPP agenda: RICAPP Meetings.

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

Recording: link to zoom recording

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
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
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
~~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~~
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
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22 : could not participate
Sunil updates (subteam-h)?
1. 2023-07-18, 2023-08-01, 2023-08-22: no news
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)~~
        ~~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.
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
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?
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.
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).
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."
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
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
RICAPP agenda: RICAPP Meetings.

2023-08-01

Recording: link to zoom recording

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
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
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:
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
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.
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
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
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)
        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
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)
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
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.
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.
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
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
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
RICAPP agenda: RICAPP Meetings.

2023-07-18

Recording: link to zoom recording

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

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
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
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
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
O-RAN SC end of release of near-RT RIC: Demo scheduled for 2 weeks from now: 2023-06-20 Release H
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
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
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
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.
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.
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)
        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.
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)
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
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.
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).
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.
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
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
RICAPP agenda: RICAPP Meetings.

2023-05-23

Recording: link to zoom recording

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
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
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
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
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
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
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.
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)
        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.
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)
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
Himanshu would like to work on RIC-963
1. code changes, but difficult to test as difficult to change order of IEs in message.
Dhiraj
1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
Alexandre
1. 2023-05-23: no news
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
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
RICAPP agenda: RICAPP Meetings.

2023-05-09

Recording: link to zoom recording

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
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
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
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
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
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.
Sunil updates?
1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25: no news
2. 2023-05-09 no news
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)
        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.
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
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.
Himanshu would like to work on RIC-963
1. code changes, but difficult to test as difficult to change order of IEs in message.
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
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
RICAPP agenda: RICAPP Meetings.

2023-04-25

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. Last checked on 2023-04-11
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/10803 OK, bug fixed for dynamic log level change
  2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10675 OK, tests included
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
Every time: Check if there are new bug reports in JIRA: link
1. RIC-972 URL for A1 mediator to align with spec.
2. RIC-971 Fix potential segfaults and double free corruption (in E2T)
3. RIC-965 RMR wormhole connections uses stale endpoints to make connections
4. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
5. RIC-915 dms_cli for installing xapp not working (raised by James)
6. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
7. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
8. RIC-897 SCTP connection fails with Viavi // update with workaround
9. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
10. RIC-894 long idle period (days) causes RMR connection breaks
11. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
12. RIC-857 sporadically RMR takes multiple minutes before being "ready"
13. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
14. RIC-837 RMR is not forwarding messages from E2T to E2M
15. RIC-835 → 2021-12-07 news from Viktor
16. fixed:
2022-12-13, 2023-01-17: Bin Yang asked about O2 for RIC platform deployment and xapp deployment. Need to discuss on this topic. O-cloud is deployed in AT&T and Taiwan lab.
1. The current platform deployment scripts might not be in line with O2 envisions
2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
3. O2-D(MS) is relevant to RIC platform.
4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
5. 2023-01-31: No news yet
6. 2023-02-14: No news yet, Thoralf received e-mail on this from James. Still to check.
7. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
8. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.
9. 2023-03-28: no news
10. 2023-04-11: Tacker team provided ideas on SMO architecture (in context of RSAC). No immediate action items for Near-RT RIC platform project
11. 2023-04-25: we did not discuss
Prashant's work in near-RT RIC
1. 2023-04-25:
  1. Prashant updated call flow for A1. Will send it for review RIC-973
  2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975
  3. Prashant, pls. create JIRA item for the SCTP E2 timeout change. RIC-976
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
Sunil updates?
1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25: no news
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)
        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
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.
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.
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
GRPC vs RMR
1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25: no update
Himanshu would like to work on RIC-963 → ok.
Anybody ever tried RIC platform with IPv6? E2T should work with IPv6 for E2. Rest Thoralf does not know.
RICAPP agenda: RICAPP Meetings.

2023-04-11

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. Last checked on 2023-04-11
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/10803 OK, bug fixed for dynamic log level change
  2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10675 OK, tests included
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
Every time: Check if there are new bug reports in JIRA: link
1. RIC-972 URL for A1 mediator to align with spec.
2. RIC-971 Fix potential segfaults and double free corruption (in E2T)
3. RIC-965 RMR wormhole connections uses stale endpoints to make connections
4. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
5. RIC-915 dms_cli for installing xapp not working (raised by James)
6. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
7. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
8. RIC-897 SCTP connection fails with Viavi // update with workaround
9. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
10. RIC-894 long idle period (days) causes RMR connection breaks
11. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
12. RIC-857 sporadically RMR takes multiple minutes before being "ready"
13. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
14. RIC-837 RMR is not forwarding messages from E2T to E2M
15. RIC-835 → 2021-12-07 news from Viktor
16. fixed: RIC-962, RIC-961, RIC-964, RIC-966, RIC-968, RIC-939, RIC-940. RIC-970
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
Prashant's work in near-RT RIC
1. Example of additional work needed: A1 - registry and "policystatusobject" (defined in spec, but not implemented in OSC near-RT RIC)
  1. best approach is to create a JIRA item and attach document to it
  2. link to JIRA item
  3. Another issue was related to SCTP in E2. Prashant will write an e-mail on the topic (incl Alexandre )
2. Naman/subhash commented that e-mail is maybe good enough.
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.
Sunil updates?
1. 2023-03-14, 2023-03-28, 2023-04-11: no news
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)
        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.
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.
Cap Gemini updates?
1. 2023-03-14
  1. RIC-851 done
  2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
2. 2023-03-28, 2023-04-11: no news.
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
GRPC vs RMR
1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11: no update
RICAPP agenda: RICAPP Meetings.

2023-03-28 (Tuesday)

Recording: link to zoom recording

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

2023-03-14 (Tuesday)

Recording: link to zoom recording

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

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. Last checked on 2023-02-28
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10405 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
    1. 2023-02-28: Abhijit worked with Matt and Sridhar from LF on this. Jobs are now running, but they fail. There's a credential issue. Abhijit to remind Sridhar. Once this is fixed, we can change Dockerfile to install prerequisites.
  2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/10287 → waiting for test cases, Gunja know and will update test case.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. new bug report RIC-962
2. RIC-961 (fixed already)
3. RIC-964 (fixed already)
4. RIC_966 (fixed already)
5. RIC-968 (fixed already)
6. RIC-940 sdlpy missing whitespace → Timo
7. RIC-939 race conditions in RMR → Abdulwahid
8. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
9. RIC-915 dms_cli for installing xapp not working (raised by James)
10. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
11. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
12. RIC-897 SCTP connection fails with Viavi // update with workaround
13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
14. RIC-894 long idle period (days) causes RMR connection breaks
15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
17. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
18. RIC-837 RMR is not forwarding messages from E2T to E2M
19. RIC-835 → 2021-12-07 news from Viktor
20. fixed: no new fixes
21. anybody would like to get more familiar with RMR?
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.
James:updates?
1. 2023-01-31:
  1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
  2. Subhash asked for a wiki page documenting this work.
  3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
    1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
    2. Tacker-based deployment needs to be checked.
2. 2023-03-14: no news
Sunil updates?
1. 2023-03-14: no news
Subhash/Naman updates?
1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
  1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
    1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
      1. Thoralf to create JIRA item for this
      2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
      3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
      4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114
2. 2023-03-14:
  1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
  2. A1 mediator nanobot integration still under work.
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.
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.
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
GRPC vs RMR
1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14: no update
Integration with AI/ML project: kserve_adapter
1. data pipeline (Hoejoo's e-mail)
  1. 2023-01-31 not discussed in today's meeting
Gunja and Sachin (CapGemini) presented changes that were done for RIC subscription delete required as per RIC-851. Thoralf to start a mail thread with Nitin, Subhash, Gunja, Sachin on how xapps can be notified of subscription changes. link to the presentation 2023-03-14: Discussion done and resulted in RIC-967.
RICAPP agenda: RICAPP Meetings.

2023-02-28 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. Last checked on 2023-02-28
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10405 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
    1. 2023-02-28: Abhijit worked with Matt and Sridhar from LF on this. Jobs are now running, but they fail. There's a credential issue. Abhijit to remind Sridhar. Once this is fixed, we can change Dockerfile to install prerequisites.
  2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/10287 → waiting for test cases, Gunja know and will update test case.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. RIC-940 sdlpy missing whitespace → Timo
2. RIC-939 race conditions in RMR → Abdulwahid
3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
4. RIC-915 dms_cli for installing xapp not working (raised by James)
5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
7. RIC-897 SCTP connection fails with Viavi // update with workaround
8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
9. RIC-894 long idle period (days) causes RMR connection breaks
10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. RIC-837 RMR is not forwarding messages from E2T to E2M
14. RIC-835 → 2021-12-07 news from Viktor
15. fixed: no new fixes
16. anybody would like to get more familiar with RMR?
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.
James:updates?
1. 2023-01-31:
  1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
  2. Subhash asked for a wiki page documenting this work.
  3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
    1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
    2. Tacker-based deployment needs to be checked.
2. 2023-02-14: no updates
3. 2023-02-28: no updates (James did not participate).
Sunil updates?
1. 2023-02-28: no updates
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
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.
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
GRPC vs RMR
1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
2. 2023-01-31, 2023-02-14, 2023-02-28: no update
Integration with AI/ML project: kserve_adapter
1. data pipeline (Hoejoo's e-mail)
  1. 2023-01-31 not discussed in today's meeting
Gunja and Sachin CapGemini) presented changes that were done for RIC subscription delete required as per RIC-851. Thoralf to start a mail thread with Nitin, Subhash, Gunja, Sachin on how xapps can be notified of subscription changes. link to the presentation
RICAPP agenda: RICAPP Meetings.

2023-02-14 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. Last checked on Dec-15
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. RIC-940 sdlpy missing whitespace → Timo
2. RIC-939 race conditions in RMR → Abdulwahid
3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
4. RIC-915 dms_cli for installing xapp not working (raised by James)
5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
7. RIC-897 SCTP connection fails with Viavi // update with workaround
8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
9. RIC-894 long idle period (days) causes RMR connection breaks
10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. RIC-837 RMR is not forwarding messages from E2T to E2M
14. RIC-835 → 2021-12-07 news from Viktor
15. fixed: no new fixes
16. anybody would like to get more familiar with RMR?
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.
Sunil still to discuss with other team members for other items from subteam-h
1. 2023-02-14: Sunil provided list with four items.
James:updates?
1. 2023-01-31:
  1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
  2. Subhash asked for a wiki page documenting this work.
  3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
    1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
    2. Tacker-based deployment needs to be checked.
2. 2023-02-14: not updates
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
GRPC vs RMR
1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
2. 2023-01-31: no update
3. 2023-02-14: no update
Johannes/Bryan: RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2023-01-31: Abhijit wanted to merge something. pls. contact Thoralf.
  1. no news from Johannes/Bryan
2. 2023-02-14:
  1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
  2. Thoralf to raise support request to LF
Integration with AI/ML project: kserve_adapter
1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
  1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
    1. Thoralf to create JIRA item for this
    2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
    3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
2. data pipeline (Hoejoo's e-mail)
  1. 2023-01-31 not discussed in today's meeting
CapGemini to present to project meeting changes that were done for RIC subscription delete required
RICAPP agenda: RICAPP Meetings.

2023-01-31 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. Last checked on Dec-15
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. RIC-940 sdlpy missing whitespace → Timo
2. RIC-939 race conditions in RMR → Abdulwahid
3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
4. RIC-915 dms_cli for installing xapp not working (raised by James)
5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
7. RIC-897 SCTP connection fails with Viavi // update with workaround
8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
9. RIC-894 long idle period (days) causes RMR connection breaks
10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. RIC-837 RMR is not forwarding messages from E2T to E2M
14. RIC-835 → 2021-12-07 news from Viktor
15. fixed: no new fixes
16. anybody would like to get more familiar with RMR?
Mark your affiliation in https://openprofile.dev so that statistics are correctly generated.
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
Sunil still to discuss with other team members for other items from subteam-h
1. 2023-01-31: no news yet. HCL still in internal discussion on what open-src items to work on in 1H2023
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.
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
GRPC vs RMR
1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
2. 2023-01-31: no update
Johannes/Bryan: RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2023-01-31: Abhijit wanted to merge something. pls. contact Thoralf.
  1. no news from Johannes/Bryan
Integration with AI/ML project: kserve_adapter
1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
  1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
    1. Thoralf to create JIRA item for this
    2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. BUt also ok if only in one.
2. data pipeline (Hoejoo's e-mail)
  1. 2023-01-31 not discussed in today's meeting
RICAPP agenda: RICAPP Meetings.

2023-01-17 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. Last checked on Dec-15
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. RIC-940 sdlpy missing whitespace → Timo
2. RIC-939 race conditions in RMR → Abdulwahid
3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
4. RIC-915 dms_cli for installing xapp not working (raised by James)
5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
7. RIC-897 SCTP connection fails with Viavi // update with workaround
8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
9. RIC-894 long idle period (days) causes RMR connection breaks
10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. RIC-837 RMR is not forwarding messages from E2T to E2M
14. RIC-835 → 2021-12-07 news from Viktor
15. fixed: no new fixes
16. anybody would like to get more familiar with RMR?
2022-12-13, 2023-01-17: Bin Yang asked about O2 for RIC platform deployment and xapp deployment. Need to discuss on this topic. O-cloud is deployed in AT&T and Taiwan lab.
1. The current platform deployment scripts might not be in line with O2 envisions
2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
3. O2-D(MS) is relevant to RIC platform.
4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Coudl be implemented as second option for deploying xApps.
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. RIC-860 + RIC-878
    1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
    2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
    3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
    4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
    5. 2022-04-26: still open
    6. 2022-05-11: expecting to finalize by May-27
    7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
    8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
    9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
    10. 2022-08-02: Sunil Singh to check any news on RIC-860 or RIC-878?
    11. 2022-08-16→2022-08-30->2022-09-13→2022-09-27: no update
    12. : some cleanup is needed first.
      1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
      2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
      3. test both if they are actually working
      4. 2022-08-30: team currently busy, but will pick up on this again soon
    13. 2023-01-17: for now remove form agenda and take back if we find someone to work on it.
  2. RIC-641 + RIC-705
    1. RIC-641: done in G
    2. RIC-705: xapp registration still open (for H?) → manage this via H content and don't keep it in the agenda.
contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
1. created on 2022-08-30: Update 2022-09-13 → 2022-09-27: Now hanging with Augu. - waiting for reply
2. 2023-01-17: no news → we drop this item from the agenda
James:
1. 2022-11-08: continues work with keysight (using KPI-mon-go xApp (E2APv1, and older E2SM). hw-go could be used if E2AP2.0 is needed. hw-go does not parse E2SM-parts.
  1. HCL also working on E2APv2.0 xApps.
2. 2023-01-17: work with keysight completed before thanksgiving weekend (excl. xapp; focus on base E2AP cases). No need to keep this in the agenda.
H release content
1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint H release dev sprint 1: Feb-20´to Mar-12
  2. Sprint H release dev sprint 2: Mar-13 to Apr-2
  3. Sprint H release dev sprint 3: Apr-3 to Apr-23
  4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
  5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
3. Please prepare for next meeting a rough view on what you might want to work on. Also as input use delayed items from previous release link
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to schedule a meeting once a proposal is ready.
7. 2022-08-16 →2022-08-30 → 2022-09-27 → 2022-10-11: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
8. 2022-11-08: focus of Nokia proposal will be on scalability (xApps, #E2 connections)
9. 2022-11-22: WG3 spec for RICAPI available in current train. Worth reading. Defines GRPC, but also SCTP+Protobuf interfaces.
10. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2023-01-17: not discussed today.
RICAPP agenda: RICAPP Meetings.
Remember to click on "end meeting for all"

2023-01-03 (Tuesday)

Recording: Link to zoom recording

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

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

2022-12-06 (Tuesday)

Recording: Link to zoom recording

The meeting was hosted by Sunil.

Updates on RICP.

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

2022-11-22 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. 2022-10-11+2022-11-08+2022-11-22
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. RIC-940 sdlpy missing whitespace → Timo
2. RIC-939 race conditions in RMR → Abdulwahid
3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
4. RIC-915 dms_cli for installing xapp not working (raised by James)
5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
7. RIC-897 SCTP connection fails with Viavi // update with workaround
8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
9. RIC-894 long idle period (days) causes RMR connection breaks
10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. RIC-837 RMR is not forwarding messages from E2T to E2M
14. RIC-835 → 2021-12-07 news from Viktor
15. fixed: no new fixes
16. anybody would like to get more familiar with RMR?
demo day? Suggestion: Dec-20. Add demo topic here: 2022-12-20 Release G
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. RIC-860 + RIC-878
    1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
    2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
    3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
    4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
    5. 2022-04-26: still open
    6. 2022-05-11: expecting to finalize by May-27
    7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
    8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
    9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
    10. 2022-08-02: Sunil Singh to check any news on RIC-860 or RIC-878?
    11. 2022-08-16→2022-08-30->2022-09-13→2022-09-27: no update
    12. : some cleanup is needed first.
      1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
      2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
      3. test both if they are actually working
      4. 2022-08-30: team currently busy, but will pick up on this again soon
  2. contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
    1. created on 2022-08-30: Update 2022-09-13 → 2022-09-27: Now hanging with Augu. - waiting for reply
  3. RIC-641 Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
    1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
    2. 2022-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: Sunil Singh check status with Anh Nguyen
    6. 2022-08-16: any news?
      1. one optinion is to cleanup CI first with the approach in RIC-912
      2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
    7. 2022-08-30 Waiting for Anh Nguyen to come fully back to work.
    8. 2022-09-13→ 2022-09-27: no update, but Anh Nguyen is now back and in discussion with Anssi
    9. 2022-10-11: Anh Nguyen to pick up again. Thoralf fixed CI issues via sandbox, minor change in CI job definition and it commit.
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
5. 2022-07-19: James is working on it with LF
6. 2022-08-02: any updates?
  1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
  2. James working Sridhar on xTesting.
7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
9. 2022-09-13: kubectl version used in testing doesn't match expectations. Work in progress
10. 2022-09-27: Demo is in the RSAC meeting from last week. Instructions are here: Automated Testing via XTesting And also watch the RSAC video recording from last week: link (fast forward to minute 9:00).
  1. next step: promote this to all OSC subprojects via TOC.
  2. James trying to run robot test cases in it/test.
11. 2022-10-11: still work in progress. Second demonstration with updated scripts: https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/12518526/XTesting-demo.mp4?api=v2
12. 2022-11-08: continues work with keysight (using KPI-mon-go xApp (E2APv1, and older E2SM). hw-go could be used if E2AP2.0 is needed. hw-go does not parse E2SM-parts.
  1. HCL also working on E2APv2.0 xApps.
G release content wrap up
1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint G release dev sprint 1: Aug-22 to Sep-11
  2. Sprint G release dev sprint 2: Sep-12 to Oct-2
  3. Sprint G release dev sprint 3: Oct-3 to Oct-23
  4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
  5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
3. link to G Release summary. Try to finalize all work by Dec-6 so we can generate the release images in the week of Dec-6
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to schedule a meeting once a proposal is ready.
7. 2022-08-16 →2022-08-30 → 2022-09-27 → 2022-10-11: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
8. 2022-11-08: focus of Nokia proposal will be on scalability (xApps, #E2 connections)
9. 2022-11-22: WG3 spec for RICAPI available in current train. Worth reading. Defines GRPC, but also SCTP+Protobuf interfaces.
In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
1. ~~2022-09-13: likely the way we go forward - Subhash and Thoralf will handle~~
  1. ~~2022-09-27: Thoralf to create presentation material and send to subhash~~
  2. ~~2022-10-11: Material shared and sent to RSAC~~
  3. ~~2022-11-08: DONE~~
2. ~~FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place) - Thoralf will present on the O-RAN day~~
  1. ~~2022-11-08: DONE~~
  2. Thoralf talked about the RIC in the presentation "Panel 3 - The RIC: How to over-deliver on the promise". The panel 3 recording starts at 1:46:00 into the youtube video: https://youtu.be/W1i6EPQ1wzo?t=6370 Thoralf also talked in the breakout panel discussion "Unpacking the intelligence of RIC: optimization and automation of complexity" (no video)
  3. ~~James organized a video loop for the OSC video recordings and James (CMCC) and and Ramesh (HCL) talked in the breakout panel discussion "Accelerating O-RAN adoption through open source"~~
  4. ~~OAI planning to support E2SM-KPM/E2SM-RC in CU/DU/gNB~~
  5. ~~ns-3 E2 adapter (GPL) is now published in OSC.~~
Update from Samsung side
1. news discussed in G release content section
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-08-02
  1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
  2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
2. 2022-09-13: working is progressing. end of September first commits should come.
3. 2022-09-27: first commit likely coming this week. Johannes could demo in two weeks from now.
4. 2022-10-11: first commit under review.
  1. 2022-10-11 Johannes to look into CI (and module tests) for Rust
    1. status: basic framework ready (ping-pong dmeo works between two xapps). next step SDL.
  2. 2022-11-08 demo (5-10min)
5. 2022-11-22. Thoralf to ask for status
RICAPP agenda: RICAPP Meetings.

2022-11-08 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. 2022-10-11+2022-11-08
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automatec CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-11-08: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. RIC-940 sdlpy missing whitespace → Timo
2. RIC-939 race conditions in RMR → Abdulwahid
3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
4. RIC-915 dms_cli for installing xapp not working (raised by James)
5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
7. RIC-897 SCTP connection fails with Viavi // update with workaround
8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
9. RIC-894 long idle period (days) causes RMR connection breaks
10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. RIC-837 RMR is not forwarding messages from E2T to E2M
14. RIC-835 → 2021-12-07 news from Viktor
15. fixed: RIC-943 (alarm-go), RIC-944 + RIC-945 (E2term)
16. anybody would like to get more familiar with RMR?
Suggestion: for the next meeting, as over the last two years, let's stick to the EET 4pm time slot even as the US and most parts of Europe change back from DST.
demo day? Suggestion: Dec-20
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. RIC-860 + RIC-878
    1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
    2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
    3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
    4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
    5. 2022-04-26: still open
    6. 2022-05-11: expecting to finalize by May-27
    7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
    8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
    9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
    10. 2022-08-02: Sunil Singh to check any news on RIC-860 or RIC-878?
    11. 2022-08-16→2022-08-30->2022-09-13→2022-09-27: no update
    12. : some cleanup is needed first.
      1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
      2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
      3. test both if they are actually working
      4. 2022-08-30: team currently busy, but will pick up on this again soon
  2. contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
    1. created on 2022-08-30: Update 2022-09-13 → 2022-09-27: Now hanging with Augu. - waiting for reply
  3. RIC-641 Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
    1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
    2. 2022-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: Sunil Singh check status with Anh Nguyen
    6. 2022-08-16: any news?
      1. one optinion is to cleanup CI first with the approach in RIC-912
      2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
    7. 2022-08-30 Waiting for Anh Nguyen to come fully back to work.
    8. 2022-09-13→ 2022-09-27: no update, but Anh Nguyen is now back and in discussion with Anssi
    9. 2022-10-11: Anh Nguyen to pick up again. Thoralf fixed CI issues via sandbox, minor change in CI job definition and it commit.
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
5. 2022-07-19: James is working on it with LF
6. 2022-08-02: any updates?
  1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
  2. James working Sridhar on xTesting.
7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
9. 2022-09-13: kubectl version used in testing doesn't match expectations. Work in progress
10. 2022-09-27: Demo is in the RSAC meeting from last week. Instructions are here: Automated Testing via XTesting And also watch the RSAC video recording from last week: link (fast forward to minute 9:00).
  1. next step: promote this to all OSC subprojects via TOC.
  2. James trying to run robot test cases in it/test.
11. 2022-10-11: still work in progress. Second demonstration with updated scripts: https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/12518526/XTesting-demo.mp4?api=v2
12. 2022-11-08: continues work with keysight (using KPI-mon-go xApp (E2APv1, and older E2SM). hw-go could be used if E2AP2.0 is needed. hw-go does not parse E2SM-parts.
  1. HCL also working on E2APv2.0 xApps.
G release content planning
1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint G release dev sprint 1: Aug-22 to Sep-11
  2. Sprint G release dev sprint 2: Sep-12 to Oct-2
  3. Sprint G release dev sprint 3: Oct-3 to Oct-23
  4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
  5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to schedule a meeting once a proposal is ready.
7. 2022-08-16 →2022-08-30 → 2022-09-27 → 2022-10-11: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
8. 2022-11-08: focus of Nokia proposal will be on scalability (xApps, #E2 connections)
In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
1. 2022-09-13: likely the way we go forward - Subhash and Thoralf will handle
  1. 2022-09-27: Thoralf to create presentation material and send to subhash
  2. 2022-10-11: Material shared and sent to RSAC
  3. 2022-11-08: DONE
2. FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place) - Thoralf will present on the O-RAN day
  1. 2022-11-08: DONE
  2. Thoralf talked about the RIC in the presentation "Panel 3 - The RIC: How to over-deliver on the promise". The panel 3 recording starts at 1:46:00 into the youtube video: https://youtu.be/W1i6EPQ1wzo?t=6370 Thoralf also talked in the breakout panel discussion "Unpacking the intelligence of RIC: optimization and automation of complexity" (no video)
  3. James organized a video loop for the OSC video recordings and James (CMCC) and and Ramesh (HCL) talked in the breakout panel discussion "Accelerating O-RAN adoption through open source"
  4. OAI planning to support E2SM-KPM/E2SM-RC in CU/DU/gNB
  5. ns-3 E2 adapter (GPL) is now published in OSC.
Update from Samsung side
1. A1 - golang - Naman used RMR from E2 manager (not from xapp-framework).
2. DMS REST server - Remote-API-equivalent to dmscli.
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-08-02
  1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
  2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
2. 2022-09-13: working is progressing. end of September first commits should come.
3. 2022-09-27: first commit likely coming this week. Johannes could demo in two weeks from now.
4. 2022-10-11: first commit under review.
  1. 2022-10-11 Johannes to look into CI (and module tests) for Rust
    1. status: basic framework ready (ping-pong dmeo works between two xapps). next step SDL.
  2. 2022-11-08 demo (5-10min)
RICAPP agenda: RICAPP Meetings.

2022-10-25 (Tuesday)

CANCELLED due to conference participation and sick leave.

2022-10-11 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. 2022-10-11
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how module testing can be done is to be discussed // also need to discuss CI
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-10-11: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. RIC-940 sdlpy missing whitespace → Timo
2. RIC-939 race conditions in RMR → Abdulwahid
3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
4. RIC-915 dms_cli for installing xapp not working (raised by James)
5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
7. RIC-897 SCTP connection fails with Viavi // update with workaround
8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
9. RIC-894 long idle period (days) causes RMR connection breaks
10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. RIC-837 RMR is not forwarding messages from E2T to E2M
14. RIC-835 → 2021-12-07 news from Viktor
15. fixed: no new fixes.
16. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. RIC-860 + RIC-878
    1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
    2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
    3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
    4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
    5. 2022-04-26: still open
    6. 2022-05-11: expecting to finalize by May-27
    7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
    8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
    9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
    10. 2022-08-02: Sunil Singh to check any news on RIC-860 or RIC-878?
    11. 2022-08-16→2022-08-30->2022-09-13→2022-09-27: no update
    12. : some cleanup is needed first.
      1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
      2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
      3. test both if they are actually working
      4. 2022-08-30: team currently busy, but will pick up on this again soon
  2. contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
    1. created on 2022-08-30: Update 2022-09-13 → 2022-09-27: Now hanging with Augu. - waiting for reply
  3. RIC-641 Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
    1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
    2. 2022-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: Sunil Singh check status with Anh Nguyen
    6. 2022-08-16: any news?
      1. one optinion is to cleanup CI first with the approach in RIC-912
      2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
    7. 2022-08-30 Waiting for Anh Nguyen to come fully back to work.
    8. 2022-09-13→ 2022-09-27: no update, but Anh Nguyen is now back and in discussion with Anssi
    9. 2022-10-11: Anh Nguyen to pick up again. Thoralf fixed CI issues via sandbox, minor change in CI job definition and it commit.
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
5. 2022-07-19: James is working on it with LF
6. 2022-08-02: any updates?
  1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
  2. James working Sridhar on xTesting.
7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
9. 2022-09-13: kubectl version used in testing doesn't match expectations. Work in progress
10. 2022-09-27: Demo is in the RSAC meeting from last week. Instructions are here: Automated Testing via XTesting And also watch the RSAC video recording from last week: link (fast forward to minute 9:00).
  1. next step: promote this to all OSC subprojects via TOC.
  2. James trying to run robot test cases in it/test.
11. 2022-10-11: still work in progress. Second demonstration with updated scripts: https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/12518526/XTesting-demo.mp4?api=v2
2022-10-11: last remaining demo from F-release
1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → middle of Sept → (updated 2022-09-27): now scheduled for 2022-10-11 (Erkki)
G release content planning
1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint G release dev sprint 1: Aug-22 to Sep-11
  2. Sprint G release dev sprint 2: Sep-12 to Oct-2
  3. Sprint G release dev sprint 3: Oct-3 to Oct-23
  4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
  5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to schedule a meeting once a proposal is ready.
7. 2022-08-16 →2022-08-30 → 2022-09-27 → 2022-10-11: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
1. 2022-09-13: likely the way we go forward - Subhash and Thoralf will handle
  1. 2022-09-27: Thoralf to create presentation material and send to subhash
  2. 2022-10-11: Material shared and sent to RSAC
2. FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place) - Thoralf will present on the O-RAN day
Update from Samsung side
1. A1 - golang - Naman used RMR from E2 manager (not from xapp-framework). Need module label - Thoralf to check. Add Alexandre to mail chain.
2. DMS REST server - Remote-API-equivalent to dmscli. Abukar + Abdulwahid-team and Samsung team on reviewing DMS server implementation. TODO-Thoralf
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-08-02
  1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
  2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
2. 2022-09-13: working is progressing. end of September first commits should come.
3. 2022-09-27: first commit likely coming this week. Johannes could demo in two weeks from now.
4. 2022-10-11: first commit under review.
  1. 2022-10-11 Johannes to look into CI (and module tests) for Rust
    1. status: basic framework ready (ping-pong dmeo works between two xapps). next step SDL.
  2. 2022-10-25 demo
host for 2022-10-25? - Sunil
RICAPP agenda: RICAPP Meetings.

2022-09-27 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. 2022-09-27
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/9006 → https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/9020 OK, (influx update) only deployment changes. So ok with test case.
  2. https://gerrit.o-ran-sc.org/r/c/ric-plt/stslgo/+/9010 → https://gerrit.o-ran-sc.org/r/c/ric-plt/stslgo/+/9047 OK, (influx update) test cases included.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-08-30, 2022-09-13, 2022-09-27: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. 2022-09-27: one new bug: RIC-940 → Timo
2. RIC-940 sdlpy missing whitespace → Timo
3. RIC-939 race conditions in RMR → Abdulwahid
4. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
5. RIC-915 dms_cli for installing xapp not working (raised by James)
6. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
7. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
8. RIC-897 SCTP connection fails with Viavi // update with workaround
9. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
10. RIC-894 long idle period (days) causes RMR connection breaks
11. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
12. RIC-857 sporadically RMR takes multiple minutes before being "ready"
13. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
14. RIC-837 RMR is not forwarding messages from E2T to E2M
15. RIC-835 → 2021-12-07 news from Viktor
16. fixed: no new fixes.
17. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. RIC-860 + RIC-878
    1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
    2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
    3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
    4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
    5. 2022-04-26: still open
    6. 2022-05-11: expecting to finalize by May-27
    7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
    8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
    9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
    10. 2022-08-02: Sunil Singh to check any news on RIC-860 or RIC-878?
    11. 2022-08-16→2022-08-30->2022-09-13→2022-09-27: no update
    12. : some cleanup is needed first.
      1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
      2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
      3. test both if they are actually working
      4. 2022-08-30: team currently busy, but will pick up on this again soon
  2. contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
    1. created on 2022-08-30: Update 2022-09-13 → 2022-09-27: Now hanging with Augu. - waiting for reply
  3. RIC-641 Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
    1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
    2. 2022-06-21
      1. RIC-642 (python) done
      2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: Sunil Singh check status with Anh Nguyen
    6. 2022-08-16: any news?
      1. one optinion is to cleanup CI first with the approach in RIC-912
      2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
    7. 2022-08-30 Waiting for Anh Nguyen to come fully back to work.
    8. 2022-09-13→ 2022-09-27: no update, but Anh Nguyen is now back and in discussion with Anssi
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
5. 2022-07-19: James is working on it with LF
6. 2022-08-02: any updates?
  1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
  2. James working Sridhar on xTesting.
7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
9. 2022-09-13: kubectl version used in testing doesn't match expectations. Work in progress
10. 2022-09-27: Demo is in the RSAC meeting from last week. Instructions are here: Automated Testing via XTesting And also watch the RSAC video recording from last week. TODO
  1. next step: promote this to all OSC subprojects via TOC.
  2. James trying to run robot test cases in it/test.
2022-07-05: still one remaining demos.
1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → middle of Sept → (updated 2022-09-27): now scheduled for 2022-10-11 (Erkki)
G release content planning
1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint G release dev sprint 1: Aug-22 to Sep-11
  2. Sprint G release dev sprint 2: Sep-12 to Oct-2
  3. Sprint G release dev sprint 3: Oct-3 to Oct-23
  4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
  5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to schedule a meeting once a proposal is ready.
7. 2022-08-16 →2022-08-30 → 2022-09-27: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
1. 2022-09-13: likely the way we go forward - Subhash and Thoralf will handle
2. FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place)
3. 2022-09-27: Thoralf to create presentation material and send to subhash
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-08-02
  1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
  2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
2. 2022-09-13: working is progressing. end of September first commits should come.
3. 2022-09-27: first commit likely coming this week. Johannes could demo in two weeks from now.
RICAPP agenda: RICAPP Meetings.

2022-09-13 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. 2022-09-13
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/9006 OK, (influx update) only deployment changes. So ok with test case.
  2. https://gerrit.o-ran-sc.org/r/c/ric-plt/stslgo/+/9010 OK, (influx update) test cases included.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on 2022-05-27. 2022-08-30, 2022-09-13: we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. 2022-09-13: one new bug: RIC-939
2. RIC-939 race conditions in RMR → Abdulwahid
3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
4. RIC-915 dms_cli for installing xapp not working (raised by James)
5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
7. RIC-897 SCTP connection fails with Viavi // update with workaround
8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
9. RIC-894 long idle period (days) causes RMR connection breaks
10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. RIC-837 RMR is not forwarding messages from E2T to E2M
14. RIC-835 → 2021-12-07 news from Viktor
15. fixed: no new fixes.
16. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
  5. 2022-04-26: still open
  6. 2022-05-11: expecting to finalize by May-27
  7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
  8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
  9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
  10. 2022-08-02: Sunil Singh to check any news on RIC-860 or RIC-878?
  11. 2022-08-16→2022-08-30->2022-09-13: no update
  12. : some cleanup is needed first.
    1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
    2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
    3. test both if they are actually working
    4. 2022-08-30: team currently busy, but will pick up on this again soon
  13. 2022-08-30: contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
    1. 2022-09-13: Now hanging with Augu. - waiting for reply
Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-06-21
  1. RIC-642 (python) done
  2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
5. 2022-08-02: Sunil Singh check status with Anh Nguyen
6. 2022-08-16: any news?
  1. one optinion is to cleanup CI first with the approach in RIC-912
  2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
7. 2022-08-30 Waiting for Anh Nguyen to come fully back to work.
8. 2022-09-13: now update, but Anh Nguyen is now back and in discussion with Anssi
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
5. 2022-07-19: James is working on it with LF
6. 2022-08-02: any updates?
  1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
  2. James working Sridhar on xTesting.
7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
9. 2022-09-13: kubectl version used in testing doesn't mahc expectations. Work in progress
2022-07-05: still one remaining demos.
1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → (update 2022-08-16) middle of Sept (Erkki)
G release content planning
1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint G release dev sprint 1: Aug-22 to Sep-11
  2. Sprint G release dev sprint 2: Sep-12 to Oct-2
  3. Sprint G release dev sprint 3: Oct-3 to Oct-23
  4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
  5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to schedule a meeting once a proposal is ready.
7. 2022-08-16 →2022-08-30 → 2022-09-13: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
1. 2022-08-30: Subhash presented the results of the discussion - material is here https://lf-o-ran-sc.atlassian.net/wiki/display/RICP/E2AP+2.0+Design
In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
1. 2022-09-13: likely the way we go forward - Subhash and Thoralf will handle
2. FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place)
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-08-02
  1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
  2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
2. 2022-09-13: working is progressing. end of September first commits should come.
2022-09-13: Joseph Thaliath & Sandeep J to present plans of OSC AI/ML subproject
1. slideset: https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/13697098/AIMLFW-KickOffMeeting.pdf?api=v2
RICAPP agenda: RICAPP Meetings.

2022-08-30 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. 2022-08-30 We did not check this this time.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on May-27-2022. 2022-08-30 we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. 2022-08-30: TODO
2. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
3. RIC-915 dms_cli for installing xapp not working (raised by James)
4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
6. RIC-897 SCTP connection fails with Viavi // update with workaround
7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
8. RIC-894 long idle period (days) causes RMR connection breaks
9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
12. RIC-837 RMR is not forwarding messages from E2T to E2M
13. RIC-835 → 2021-12-07 news from Viktor
14. fixed: no new fixes.
15. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
  5. 2022-04-26: still open
  6. 2022-05-11: expecting to finalize by May-27
  7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
  8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
  9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
  10. 2022-08-02: Sunil Singh to check any news on RIC-860 or RIC-878?
  11. 2022-08-16→2022-08-30: some cleanup is needed first.
    1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
    2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
    3. test both if they are actually working
    4. 2022-08-30: team currently busy, but will pick up on this again soon
  12. 2022-08-30: contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
5. 2022-07-19: James is working on it with LF
6. 2022-08-02: any updates?
  1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
  2. James working Sridhar on xTesting.
7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-06-21
  1. RIC-642 (python) done
  2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
5. 2022-08-02: Sunil Singh check status with Anh Nguyen
6. 2022-08-16: any news?
  1. one optinion is to cleanup CI first with the approach in RIC-912
  2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
7. 2022-08-30 Waiting for Any Nguyen to come fully back to work.
2022-07-05: still one remaining demos.
1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → (update 2022-08-16) middle of Sept (Erkki)
G release content planning
1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint G release dev sprint 1: Aug-22 to Sep-11
  2. Sprint G release dev sprint 2: Sep-12 to Oct-2
  3. Sprint G release dev sprint 3: Oct-3 to Oct-23
  4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
  5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to schedule a meeting once a proposal is ready.
7. 2022-08-16 →2022-08-30 no news yet
Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
1. 2022-04-26: in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
3. Thoralf to schedule another meeting end of May (after F).
4. 2022-06-07: Thoralf will schedule a meeting for week after next week
5. 2022-06-21→2022-07-05: This has to wait for end of July
6. 2022-08-02: meeting scheduled for 2022-08-04
7. 2022-08-30: Subhash presented the results of the discussion - material is here https://lf-o-ran-sc.atlassian.net/wiki/display/RICP/E2AP+2.0+Design
In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-08-02
  1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
  2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
RICAPP agenda: RICAPP Meetings.

2022-08-16 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/8824 → OK, as only new swagger yaml file for which nothing is implemented yet.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on May-27-2022. 2022-08-16 we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. 2022-08-16: TODO
2. RIC-936 change from gcr.io → ghcr.io in master and f-release DONE
3. RIC-935 flannel namespace change. fixed in master and f-release DONE
4. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
5. RIC-915 dms_cli for installing xapp not working (raised by James)
6. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
7. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
8. RIC-897 SCTP connection fails with Viavi // update with workaround
9. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
10. RIC-894 long idle period (days) causes RMR connection breaks
11. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
12. RIC-857 sporadically RMR takes multiple minutes before being "ready"
13. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
14. RIC-837 RMR is not forwarding messages from E2T to E2M
15. RIC-835 → 2021-12-07 news from Viktor
16. fixed: RIC-935, RIC-936
17. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
  5. 2022-04-26: still open
  6. 2022-05-11: expecting to finalize by May-27
  7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
  8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
  9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
  10. 2022-08-02: Sunil Singh to check any news on RIC-860 or RIC-878?
  11. 2022-08-16: some cleanup is needed first.
    1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
    2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
    3. test both if they are actually working
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
5. 2022-07-19: James is working on it with LF
6. 2022-08-02: any updates?
  1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
  2. James working Sridhar on xTesting.
7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-06-21
  1. RIC-642 (python) done
  2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
5. 2022-08-02: Sunil Singh check status with Anh Nguyen
6. 2022-08-16: any news?
  1. one optinion is to cleanup CI first with the approach in RIC-912
  2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
2022-07-05: still one remaining demos.
1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → (update 2022-08-16) middle of Sept (Erkki)
G release content planning
1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint G release dev sprint 1: Aug-22 to Sep-11
  2. Sprint G release dev sprint 2: Sep-12 to Oct-2
  3. Sprint G release dev sprint 3: Oct-3 to Oct-23
  4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
  5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to schedule a meeting once a proposal is ready.
7. 2022-08-16 no news yet
Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
1. 2022-04-26: in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
3. Thoralf to schedule another meeting end of May (after F).
4. 2022-06-07: Thoralf will schedule a meeting for week after next week
5. 2022-06-21→2022-07-05: This has to wait for end of July
6. 2022-08-02: meeting scheduled for 2022-08-04
7. 2022-08-16: Subhash to present results of discussion in next meeting on 2022-08-30
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-08-02
  1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
  2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
2. 2022-08-16: repo is now created ->Closed
RICAPP agenda: RICAPP Meetings.

2022-08-02 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. 2022-08-02: no large commits
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on May-27-2022. 2022-08-02 we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. 2022-08-02: no new bugs, no new fixes
2. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
3. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
6. RIC-897 SCTP connection fails with Viavi // update with workaround
7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
8. RIC-894 long idle period (days) causes RMR connection breaks
9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
12. RIC-837 RMR is not forwarding messages from E2T to E2M
13. RIC-835 → 2021-12-07 news from Viktor
14. fixed:no new fixes
15. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
  5. 2022-04-26: still open
  6. 2022-05-11: expecting to finalize by May-27
  7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
  8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
  9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
  10. 2022-08-02: Sunil Singh to check any news on RIC-860 or RIC-878?
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
5. 2022-07-19: James is working on it with LF
6. 2022-08-02: any updates?
  1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
  2. James working Sridhar on xTesting.
Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-06-21
  1. RIC-642 (python) done
  2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
5. 2022-08-02: Sunil Singh check status with Anh Nguyen
2022-07-05: still one remaining demos.
1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
G release content planning
1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint G release dev sprint 1: Aug-22 to Sep-11
  2. Sprint G release dev sprint 2: Sep-12 to Oct-2
  3. Sprint G release dev sprint 3: Oct-3 to Oct-23
  4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
  5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to scheduke a meeting once a proposal is ready.
Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
1. 2022-04-26: in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
3. Thoralf to schedule another meeting end of May (after F).
4. 2022-06-07: Thoralf will schedule a meeting for week after next week
5. 2022-06-21→2022-07-05: This has to wait for end of July
6. 2022-08-02: meeting scheduled for 2022-08-04
Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
1. 2022-07-19 no news
2. 2022-08-02 → move to bug sections (Thoralf added this as comment to RIC-894)
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-08-02
  1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
  2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
RICAPP agenda: RICAPP Meetings.

2022-07-19 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).2022-07-19:
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on May-27-2022. 2022-07-19 we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. 2022-07-19: we did not check this this time.
2. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
3. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
6. RIC-897 SCTP connection fails with Viavi // update with workaround
7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
8. RIC-894 long idle period (days) causes RMR connection breaks
9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
12. RIC-837 RMR is not forwarding messages from E2T to E2M
13. RIC-835 → 2021-12-07 news from Viktor
14. fixed:no new fixes
15. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
  5. 2022-04-26: still open
  6. 2022-05-11: expecting to finalize by May-27
  7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
  8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
  9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: XTesting proposed as alternative to OTF
5. 2022-07-19: James is workin on it with LF
Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-06-21
  1. RIC-642 (python) done
  2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
2022-07-05: still two remaining demos.
1. 2022-07-19: RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Shobha)
  1. new function in https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/nodeb-rnib.git;a=blob;f=reader/rNibReader.go -> GetRanFunctionDefinition()
  2. C version via creader (see https://packagecloud.io/o-ran-sc/release/packages/debian/stretch/rnib_1.2.5_all.deb)
  3. play video "RIC_888.mp4" from tmp folder (remember ... → "share sound")
2. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
3. 2022-07-19: Thoralf uploaded demo on deploying RIC, connecting the simulator project's E2 (node) simulator, Nokia simulator and deploy the hw-go xapp as well: 2022-05-24 Release F
F release wrap up
1. 2022-07-05 & 2022-07-19: F release. See demo page: Release criteria checklist - Release F, Near-RT RIC (F release) = image list, F Release = summary, 2022-05-24 Release F = demos.
G release content planning
1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
  1. Sprint G release dev sprint 1: Aug-22 to Sep-11
  2. Sprint G release dev sprint 2: Sep-12 to Oct-2
  3. Sprint G release dev sprint 3: Oct-3 to Oct-23
  4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
  5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
GRPC vs RMR
1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
1. 2022-04-26: in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
3. Thoralf to schedule another meeting end of May (after F).
4. 2022-06-07: Thoralf will schedule a meeting for week after next week
5. 2022-06-21→2022-07-05: This has to wait for end of July
Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
1. 2022-07-19 no news
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-07-19 TOC approved ric-plt/xapp-frame-rust is ready for content. ric-app/hw-rust still to be created
2. 2022-07-19 go through commit steps
RICAPP agenda: RICAPP Meetings.

2022-07-05 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).2022-07-05:
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on May-27-2022. 2022-07-05 we did not do this this time
Every time: Check if there are new bug reports in JIRA: link
1. 2022-07-05: we did not check this this time.
2. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
3. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
6. RIC-897 SCTP connection fails with Viavi // update with workaround
7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
8. RIC-894 long idle period (days) causes RMR connection breaks
9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
12. RIC-837 RMR is not forwarding messages from E2T to E2M
13. RIC-835 → 2021-12-07 news from Viktor
14. fixed:no new fixes
15. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update: - Code checked-in
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
  5. 2022-04-26: still open
  6. 2022-05-11: expecting to finalize by May-27
  7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
  8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: Xtesting proposed as alternative to OTF
5. 2022-07-05: Any news from James?
Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-06-21
  1. RIC-642 (python) done
  2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-py) out of the F release. Which means they are likely early G release features.
2022-07-05: still two remaining demos.
1. No demo today (plan for 2022-07-19) 5 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Manoj)
2. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
3. 2022-07-05: Thoralf uploaded demo on deploying RIC, connecting the simulator project's E2 (node) simulator, Nokia simulator and deploy the hw-go xapp as well: 2022-05-24 Release F
F release wrap up
1. 2022-07-05 & 2022-07-19: F release. See demo page: Release criteria checklist - Release F, Near-RT RIC (F release) = image list, F Release = summary, 2022-05-24 Release F = demos.
Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
1. 2022-04-26:
  1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
  2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
  3. Thoralf to schedule another meeting end of May (after F).
  4. 2022-06-07: Thoralf will schedule a meeting for week after next week
2. 2022-06-21→2022-07-05: This has to wait for end of July
Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
1. 2022-07-05 no news
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-06-21: We had a meeting on this last week and proposal for TOC is in the making. Two new components: ric-plt/xapp-frame-rust and ric-app/hw-rust)
2. 2022-07-05:
  1. addition of ric-plt/xapp-frame-rust and ric-app/hw-rust was approved by TOC on Jun-23-2022.
  2. Thoralf to create the repos once back from holiday (mid July)
RICAPP agenda: RICAPP Meetings.

2022-06-21 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/8368 OK cleanup of ric-dep and it-dep (only copied code)
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493 OK
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/8569 OK
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on May-27-2022. Not done this time
Every time: Check if there are new bug reports in JIRA: link
1. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
2. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
3. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
4. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
5. RIC-897 SCTP connection fails with Viavi // update with workaround
6. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
7. RIC-894 long idle period (days) causes RMR connection breaks
8. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
9. RIC-857 sporadically RMR takes multiple minutes before being "ready"
10. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
11. RIC-837 RMR is not forwarding messages from E2T to E2M
12. RIC-835 → 2021-12-07 news from Viktor
13. fixed: RIC-920 (gNB ID fix)
14. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in.
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
  5. 2022-04-26: still open
  6. 2022-05-11: expecting to finalize by May-27
  7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
4. 2022-06-21: Xtesting proposed as alternative to OTF
Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-06-21
  1. RIC-642 (python) done
  2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
2022-06-21: demo held on 2022-07-06. Remaining demos planned for 2022-06-21
1. No demo today (plan for 2022-07-19) 5 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Manoj)
2. 10min RIC-916 new reconnect timer in E2 to reject new connect for x seconds (dhiraj)
3. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
F release wrap up
1. see §6 in Jira usage conventions
2. Thoralf to go through JIRA and check status of items. Thoralf might send e-mails to get current status.
3. Thoralf to organize sprint demos for May-24, at 9am ET in an extended timeslot of the project meeting.
  1. See demo page: 2022-05-24 Release F
New contribution proposals: Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
1. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
  1. 2022-04-26:
    1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
    2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
    3. Thoralf to schedule another meeting end of May (after F).
    4. 2022-06-07: Thoralf will schedule a meeting for week after next week
    5. 2022-06-21: This has to wait for end of July
Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
RUST as a language for xApps and framework. Will take this in the details in next meeting.
1. 2022-06-21: We had a meeting on this last week and proposal for TOC is in the making. Two new components: ric-plt/xapp-frame-rust and ric-app/hw-rust)
2. Approved by the TOC.
RICAPP agenda: RICAPP Meetings.

2022-06-07 (Tuesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/8324 OK (commit of previously reviewed files in e2ap branch)
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8303 OK (commit of previously reviewed files in e2ap branch)
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/8323 OK (commit of previously reviewed files in e2ap branch)
4. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/8332 OK (change in proto file that caused changes in generated files)
5. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/8368 OK (lots of code moved from it/dep repo)
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this on May-27-2022 - no surprises
4. ric-plt/alarm-go 0,0 // no bugs (2021-11-22 → 2022-02-13 → 2022-05-26)
5. ric-plt/appmgr 19,3 // 1 major bug (2022-01-30 → 2022-02-13 → 2022-05-26)
6. ric-plt/e2mgr 88,6 → 87,7 // no bugs (2021-11-18 → 2022-02-14 → 2022-05-27)
7. ric-plt/lib/rmr 86,1 // no bugs (2021-11-23 → 2022-02-08 → 2022-05-24)
8. ric-plt/sdlgo 90,2 → 90,5 // no bugs (2022-01-31 → 2022-02-14 → 2022-05-27)
9. ric-plt/submgr 51,4 // no bugs (2022-01-30 → 2022-02-13 → 2022-05-27)
10. ric-plt/tracelibcpp 0,0 // 1 major bug (2022-01-25 → 2022-02-08 → 2022-05-24)
11. ric-plt/tracelibgo 96,2 //0 bugs (2022-01-30 → 2022-02-13 → 2022-05-27)
12. ric-plt/xapp-frame 0,0 // no bugs (2021-11-22 → 2022-02-13 → 2022-05-26)
13. ric-plt/xapp-frame-cpp 95,6 → 96,3 // no blocker bugs (2022-01-26 → 2022-02-00 → 2022-05-25)
Every time: Check if there are new bug reports in JIRA: link
1. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
2. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
3. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
4. RIC-897 SCTP connection fails with Viavi // update with workaround
5. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
6. RIC-894 long idle period (days) causes RMR connection breaks
7. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
8. RIC-857 sporadically RMR takes multiple minutes before being "ready"
9. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
10. RIC-837 RMR is not forwarding messages from E2T to E2M
11. RIC-835 → 2021-12-07 news from Viktor
12. fixed: no new fixes
13. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in.
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
  5. 2022-04-26: still open
  6. 2022-05-11: expecting to finalize by May-27
  7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    1. 2022-05-30: Thoralf comment in RIC-915
Progress on E2APv2.0?
1. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
    1. hw-go issue with old xapp frame lib used. - needs to be updated.
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
    1. done, but not yet open for review.
    2. 2022-05-30: Simulator worked fine, but thoralf raised SIM-99 for supporting source-address binding in the simulator
  5. 2022-05-31: as we're not ready with RIC-641 (cpp) and RIC-642 (python) we decided to still keep RMR enabled as interface provided by the subscription manager. RIC-642 is almost ready, and I understand RIC-641 is also being worked on. 07-06-2022 - RIC-641 HCL team is working on this.
  6. 07-06-2022: E2APv2.0 - Code merged
2. in DU
  1. 2022-02-23 Former user (Deleted) reported in TOC that this work is done.
RIC-641 Sandeep (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-04-26: working on it
3. 2022-05-11: news? Could be handled as exception to be worked on during May-15 to Jun-5 so we can still include this into F.
4. 2022-06-07: Any news?
F release wrap up
1. see §6 in Jira usage conventions
2. Thoralf to go through JIRA and check status of items. Thoralf might send e-mails to get current status.
3. Thoralf to organize sprint demos for May-24, at 9am ET in an extended timeslot of the project meeting.
  1. See demo page: 2022-05-24 Release F
  2. 2022-07-06 demo held. Remaining demos planned for 2022-06-21
    1. 5 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Manoj)
    2. 10min RIC-916 new reconnect timer in E2 to reject new connect for x seconds
New contribution proposals: Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
1. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
  1. 2022-04-26:
    1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
    2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
    3. Thoralf to schedule another meeting end of May (after F).
    4. 2022-06-07: Thoralf will schedule a meeting for week after next week
Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
Note - 6-7-2022 : Matti send a mail on this. RUST as a language for xApps and framework. Will take this in the details in next meeting.
RICAPP agenda: RICAPP Meetings.

2022-05-24

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

2022-05-11 (exceptionally Wednesday)

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/8127 ok
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/stslgo/+/8112 ok
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8136 ok
4. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/8147 ok - as only files only moved from other repo
5. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8196 ok
6. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8215 ok
7. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8218 ok
8. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7592 ok
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. We did not do this today.
Every time: Check if there are new bug reports in JIRA: link
1. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
2. RIC-903 new (from PW) DefaultUser setup fails when authentication is enabled for InfluxDB. 2022-05-11: fixed
3. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
4. RIC-897 SCTP connection fails with Viavi // update with workaround
5. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
6. RIC-894 long idle period (days) causes RMR connection breaks
7. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail. 2022-05-11: fixed
  1. could be staging repo related (10004) vs release repo (10002) for the base image
8. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
9. RIC-857 sporadically RMR takes multiple minutes before being "ready"
10. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
11. RIC-837 RMR is not forwarding messages from E2T to E2M
12. RIC-835 → 2021-12-07 news from Viktor
13. fixed: RIC-903, RIC-890, RIC-891, RIC-892
14. anybody would like to get more familiar with RMR?
2022-06-07: We plan to release in June. Thoralf will coordinate creation of container images by e-mail.
1. F release tasks for releasing the container images: Near-RT RIC (F release)
2. F release status: F Release
3. F release criteria checklist (filled in by Thoralf): Release criteria checklist - Release F
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in.
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
  5. 2022-04-26: still open
  6. 2022-05-11: expecting to finalize by May-27
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
  1. Currently in the hands of OTF team (Alex)
  2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
Progress on E2APv2.0?
1. in ric platform and simulators?
  1. 2022-04-26
    1. subscription manager change for E2APv2.0 is now in E2APv2.0 branch
    2. config update message support coming this week.
    3. after this cleanup of small things here and there that are still needed.
  2. 2022-05-10
    1. thoralf suggests May-13 as day for moving E2AP branch to master
      1. Subhash agrees. So let's aim for that.
      2. Subhash to list which Config transfer failure cases move into next release (just left-over create JIRA item)
    2. Nokia has already tested some E2APv2.0 procedures with Nokia simulator (like E2 setup, subscription success case)
    3. Subhash still working on simulator in sim project
2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
    1. hw-go issue with old xapp frame lib used. - needs to be updated.
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
    1. done, but not yet open for review.
3. in DU
  1. 2022-02-23 Former user (Deleted) reported in TOC that this work is done.
RIC-641 Sandeep (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-04-26: working on it
3. 2022-05-11: news? Could be handled as exception to be worked on during May-15 to Jun-5 so we can still include this into F.
F release wrap up
1. see §6 in Jira usage conventions
2. Thoralf to go through JIRA and check status of items. Thoralf might send e-mails to get current status.
3. Thoralf to organize sprint demos for May-24, at 9am ET in an extended timeslot of the project meeting.
  1. See demo page: 2022-05-24 Release F
New contribution proposals: Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
1. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
  1. 2022-04-26:
    1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
    2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
    3. Thoralf to schedule another meeting end of May (after F).
Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
RICAPP agenda: RICAPP Meetings.

2022-04-26

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/8095 ok
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8069 ok
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. We did not do this today.
Every time: Check if there are new bug reports in JIRA: link
1. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
2. RIC-903 new (from PW) DefaultUser setup fails when authentication is enabled for InfluxDB
3. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
4. RIC-897 SCTP connection fails with Viavi // update with workaround
5. RIC-894 long idle period (days) causes RMR connection breaks // update with more information
6. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
7. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail.
  1. could be staging repo related (10004) vs release repo (10002) for the base image
8. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
9. RIC-857 sporadically RMR takes multiple minutes before being "ready"
10. RIC-835 → 2021-12-07 news from Viktor
11. RIC-837 RMR is not forwarding messages from E2T to E2M
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. fixed: no new fixes
14. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in.
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-04-12: Still open
  5. 2022-04-26: still open
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
  1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
  2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
Progress on E2APv2.0?
1. in ric platform and simulators?
  1. 2022-03-29
    1. AP: Subhash to present he E2AP2.0 slides (15min) from here: E2AP 2.0 Design
    2. Simulator code updated to E2APv2.0: https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/7971 (incl. asn1c generated files) config transfer message coming soon
    3. protobuf definitions for configuration components under re-work
    4. E2APv2-0 branches? nodeb-rnib already branched.
  2. 2022-04-12
    1. E2M patch for E2 Setup as per new version (Dhiraj/Arun to review). Octet sequence for config request/repsonse within E2 setup not yet correctly handled
    2. next step is config update message (1-2 weeks)
    3. transaction id handling should be in same patch as well.
  3. 2022-04-26
    1. subscription manager change for E2APv2.0 is now in E2APv2.0 branch
    2. config update message support coming this week.
    3. after this cleanup of small things here and there that are still needed.
2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
    1. hw-go issue with old xapp frame lib used. - needs to be updated.
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
    1. done, but not yet open for review.
3. in DU
  1. 2022-02-23 Former user (Deleted) reported in TOC that this work is done.
RIC-641 Sandeep (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-04-26:working on it
2022-04-26: NU (Northeastern University) proposed as new repo in the simulator project for their contribution of an E2 adapter that adapts E2 to the ns-3 (RAN) simulator. A presentation is planned for the TOC call on Apr-27.
F release wrap up
1. see §6 in Jira usage conventions
2. Thoralf to go through JIRA and check status of items. Thoralf might send e-mails to get current status.
3. Thoralf to organize sprint demos for May-24, at 9am ET in an extended timeslot of the project meeting.
New contribution proposals: Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
1. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
  1. 2022-04-26:
    1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
    2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
    3. Thoralf to schedule another meeting end of May (after F).
2. Thoralf (near-RT RIC) proposed a new repo ric-plt/stslgo . Details: https://lists.o-ran-sc.org/g/toc/message/674
  1. 2022-04-26: repo is now available
Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
RICAPP agenda: RICAPP Meetings.

2022-04-12

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/7974 ok, protobuf definitions only
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/8037 ok, generated asn.1 encoder/decoder files.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. We did not do this today.
Every time: Check if there are new bug reports in JIRA: link
1. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
2. RIC-903 new (from PW) DefaultUser setup fails when authentication is enabled for InfluxDB
3. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
4. RIC-897 SCTP connection fails with Viavi // update with workaround
5. RIC-894 long idle period (days) causes RMR connection breaks // update with more information
6. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
7. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail.
  1. could be staging repo related (10004) vs release repo (10002) for the base image
8. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
9. RIC-857 sporadically RMR takes multiple minutes before being "ready"
10. RIC-835 → 2021-12-07 news from Viktor
11. RIC-837 RMR is not forwarding messages from E2T to E2M
12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
13. fixed:
14. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
  1. Sangeetha working on RIC-860, done, but code still to be checked in.
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-04-12: Still open
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-01-27 (Mail sent)
2. 2022-02-15: resending with the right David
3. 2022-03-01:
  1. workshop to be planned (James in discussion with David)
  2. in last weeks SMO+RSAC meeting this was discussed as well. It would be good to have a test case that just verifies successful deployment of the RIC platform, workshop still to be scheduled.
  3. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
  4. 2022-03-15: James creating a E release profile for powder
4. 2022-03-15: workshop still to be held (was moved by two weeks (Mar-24))
5. 2022-03-29: OTF workshop planned for April-7 9am EDT https://lists.o-ran-sc.org/g/discuss/message/487
6. 2022-04-12
  1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
  2. actual workshop planned for RSAC on Apr-21 9am EDT.
  3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
Progress on E2APv2.0?
1. in ric platform and simulators?
  1. 2022-03-29
    1. AP: Subhash to present he E2AP2.0 slides (15min) from here: E2AP 2.0 Design
    2. Simulator code updated to E2APv2.0: https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/7971 (incl. asn1c generated files) config transfer message coming soon
    3. protobuf definitions for configuration components under re-work
    4. E2APv2-0 branches? nodeb-rnib already branched.
  2. 2022-04-12
    1. E2M patch for E2 Setup as per new version (Dhiraj/Arun to review). Octet sequence for config request/repsonse within E2 setup not yet correctly handled
    2. next step is config update message (1-2 weeks)
    3. transaction id handling should be in same patch as well.
2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
    1. hw-go issue with old xapp frame lib used. - needs to be updated.
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
    1. done, but not yet open for review.
3. in DU
  1. 2022-02-23 Former user (Deleted) reported in TOC that this work is done.
RIC-641 Sandeep (HCL) is working on this. Work is progressing.
1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
New contribution proposals: Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
1. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
2. Thoralf (near-RT RIC) proposed a new repo ric-plt/stslgo . Details: https://lists.o-ran-sc.org/g/toc/message/674
RICAPP agenda: RICAPP Meetings.

2022-03-29

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/7955 ok, removal of deprecated code
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. We did not do this today.
Every time: Check if there are new bug reports in JIRA: link
1. RIC-897 SCTP connection fails with Viavi
2. RIC-894 long idle period (days) causes RMR connection breaks
3. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
4. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail.
  1. could be staging repo related (10004) vs release repo (10002) for the base image
5. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
6. RIC-857 sporadically RMR takes multiple minutes before being "ready"
7. RIC-835 → 2021-12-07 news from Viktor
8. RIC-837 RMR is not forwarding messages from E2T to E2M
9. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
10. fixed: RIC-895 (routes in routing mgr for service update messages)
11. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
2. 2022-03-01_
  1. Sangeetha working on RIC-860, done, but code still to be checked in.
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
  3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
  4. Subhash asked for documentation of nanobot from Sunil. almost done.
3. 2022-03-15: status Sangeetha?
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-01-27 (Mail sent)
2. 2022-02-15: resending with the right David
3. 2022-03-01:
  1. workshop to be planned (James in discussion with David)
  2. in last weeks SMO+RSAC meeting this was discussed as well. It would be good to have a test case that just verifies successful deployment of the RIC platform, workshop still to be scheduled.
  3. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
  4. 2022-03-15: James creating a E release profile for powder
4. 2022-03-15: workshop still to be held (was moved by two weeks (Mar-24))
5. 2022-03-29: workshop planned for April-7 9am EDT https://lists.o-ran-sc.org/g/discuss/message/487
Progress on E2APv2.0?
1. in ric platform and simulators?
  1. Any first code/design review request that Arun and Dhiraj should review?
  2. progress, subhash: simulator adapted. E2T changes internally ready.
  3. Subhash&co did not plan to do any testing on xApp side.
  4. thoralf to sent invitation to Subhash &co for Friday → DONE
    1. agreed on configuration transfer to be handled similar to function definitions as E2APv2.0 now defines configuration updates as replacing instead of updating existing component configuration entries.
    2. E2 reset to be handled as new state that xApps see: "connected---transition1-->connected-but-under-reset---transition2-->connected". We use a timer, instead of strict xapp and submgr confirmation that all has been cleaned up. xApps shall resubscribe only after transition2. xapps can assume that submgr has removed all subscriptions (in its view of the world) and that the E2 node has removed them (in its view of the world)
    3. Subhash will send slideset for this during this week
    4. E2 implementation status and reviews coming?
  5. 2022-03-15 any news?
    1. do we need an E2APv2.0 branch (submgr used/uses e2ap-v02.00)
      1. if we create a E2 branch now we can do the review in that branch. E2T, E2M, and RNIB. submgr already has branch.
      2. Subhash to ask from Alex Stancu for branch in E2 sim
    2. Already initial versions of the work? Dhiraj and Arun are available for reviewing.
    3. updated design: E2AP 2.0 Design
    4. Could provide initial version in which config handling (IE in E2 Setup) is just ignored.
    5. AP: Subhash to present he E2AP2.0 slides (15min)
    6. A1 mediator work proceeding (two more APIs)
  6. 2022-03-29
    1. AP: Subhash to present he E2AP2.0 slides (15min) from here: E2AP 2.0 Design
    2. Simulator code updated to E2APv2.0: https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/7971 (incl. asn1c generated files) config transfer message coming soon
    3. protobuf definitions for configuration components under re-work
    4. E2APv2-0 branches? nodeb-rnib already branched.
2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
    1. hw-go issue with old xapp frame lib used. - needs to be updated.
    2. in same mail thread there's another issue - to be discussed over mail.
    3. 2022-03-15: Still open corner case where registration is not done yet, but sub requests are already sent. Thoralf to ask from Nune.
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
    1. done, but not yet open for review.
3. in DU
  1. 2022-02-23 Former user (Deleted) reported in TOC that this work is done.
RIC-641 Sandeep (HCL) is working on this. Work is progressing
New contribution proposals
1. E2 RESET handling
  1. when meeting?
  2. Thoralf to send meeting invitation for this or next week (timezone india+europe)
2. Influx-DB Wrapper
  1. new repo=stslgo (shared time series layer)
  2. involve Sunil (HCL) and Dhiraj and Subhash & co for proposal
3. O1-NetConf Enhancements
  1. Nune said "ok"
4. Stability Issues
  1. Nune said "ok"
5. Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
RICAPP agenda: RICAPP Meetings.

2022-03-15

Recording: link to zoom recording

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).
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. 2022-03-15: Thoralf went through the list → no updates.
Every time: Check if there are new bug reports in JIRA: link
1. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail.
2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
3. RIC-857 sporadically RMR takes multiple minutes before being "ready"
4. RIC-835 → 2021-12-07 news from Viktor
5. RIC-837 RMR is not forwarding messages from E2T to E2M
6. RIC-840 Unable to deploy E2Term on Dawn release
7. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
8. fixed: no new fixes since last meeting. We marked RIC-840 as done because in E it seems to work.
9. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
2. 2022-03-01_
  1. Sangeetha working on RIC-860, done, but code still to be checked in.
  2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
  3. O1 testing is also being worked on.
  4. Subhash asked for documentation of nanobot from Sunil. almost done.
3. 2022-03-15: status Sangeetha?
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-01-27 (Mail sent)
2. 2022-02-15: resending with the right David
3. 2022-03-01:
  1. workshop to be planned (James in discussion with David)
  2. in last weeks SMO+RSAC meeting this was discussed as well. It would be good to have a test case that just verifies successful deployment of the RIC platform, workshop still to be scheduled.
  3. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
  4. 2022-03-15: James creating a E release profile for powder
4. 2022-03-15: workshop still to be held (was moved by two weeks (Mar-24))
Progress on E2APv2.0?
1. in ric platform and simulators?
  1. Any first code/design review request that Arun and Dhiraj should review?
  2. progress, subhash: simulator adapted. E2T changes internally ready.
  3. Subhash&co did not plan to do any testing on xApp side.
  4. thoralf to sent invitation to Subhash &co for Friday → DONE
    1. agreed on configuration transfer to be handled similar to function definitions as E2APv2.0 now defines configuration updates as replacing instead of updating existing component configuration entries.
    2. E2 reset to be handled as new state that xApps see: "connected---transition1-->connected-but-under-reset---transition2-->connected". We use a timer, instead of strict xapp and submgr confirmation that all has been cleaned up. xApps shall resubscribe only after transition2. xapps can assume that submgr has removed all subscriptions (in its view of the world) and that the E2 node has removed them (in its view of the world)
    3. Subhash will send slideset for this during this week
    4. E2 implementation status and reviews coming?
  5. 2022-03-15 any news?
    1. do we need an E2APv2.0 branch (submgr used/uses e2ap-v02.00)
      1. if we create a E2 branch now we can do the review in that branch. E2T, E2M, and RNIB. submgr already has branch.
      2. Subhash to ask from Alex Stancu for branch in E2 sim
    2. Already initial versions of the work? Dhiraj and Arun are available for reviewing.
    3. updated design: E2AP 2.0 Design
    4. Could provide initial version in which config handling (IE in E2 Setup) is just ignored.
    5. AP: Subhash to present he E2AP2.0 slides (15min)
    6. A1 mediator work proceeding (two more APIs)
2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
    1. hw-go issue with old xapp frame lib used. - needs to be updated.
    2. in same mail thread there's another issue - to be discussed over mail.
    3. 2022-03-15: Still open corner case where registration is not done yet, but sub requests are already sent. Thoralf to ask from Nune.
    4. 2022-03-29: xapp wasn't registered (as visible in output of curl commane below. instructions how to register are in user_guide_v2
      1. $ curl -i -X GET http://10.244.0.138:8080/ric/v1/xapps //IP = appmgr IP
      2. []
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
    1. done, but not yet open for review.
3. in DU
  1. 2022-02-23 Former user (Deleted) reported in TOC that this work is done.
Alexandre started work on RIC-705
RIC-641 Sandeep (HCL) is working on this.
RICAPP agenda: RICAPP Meetings.

2022-03-01

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7610 OK
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7587 OK redis client from v7 to v8 and adapting to changes in interface.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. not done this time.
Every time: Check if there are new bug reports in JIRA: link
1. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
2. RIC-857 sporadically RMR takes multiple minutes before being "ready"
3. RIC-835 → 2021-12-07 news from Viktor
4. RIC-837 RMR is not forwarding messages from E2T to E2M
5. RIC-840 Unable to deploy E2Term on Dawn release
6. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
7. fixed: no new fixes since last meeting.
8. anybody would like to get more familiar with RMR?
Cross-check with A. if he has updated the instructions to point to helm3.
1. A. can look on this on Jan-31 and update here: new section here - https://docs.o-ran-sc.org/projects/o-ran-sc-it-dep/en/latest/installation-guides.html
2. 2022-02-14: there's a review for this documentation change (change 7638). The review fails in LF CI/Jenkins in SMO/non-rt RIC related parts. Asked help from James by e-mail. James raised a request to LF: IT-23628
3. 2022-02-16: merged and DONE.
Sunil still to discuss with other team members for other items from subteam-h
1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
2. Sangeetha working on RIC-860, done, but code still to be checked in.
3. Sangeetha working on RIC-878, status see Jira item
4. Subhash asked for documentation of nanobot from Sunil.
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-01-27 (Mail sent)
2. 2022-02-15: resending with the right David
3. 2022-03-01: workshop to be planned (James in discussion with David)
4. in last weeks SMO+RSAC meeting this was discussed as well. It would be good to have a test case that just verifies successful deployment of teh RIC platform, workshop still to be scheduled.
5. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
Progress on E2APv2.0?
1. in ric platform and simulators?
  1. Any first code/design review request that Arun and Dhiraj should review?
  2. progress, subhash: simulator adapted. E2T changes internally ready.
  3. Subhash&co did not plan to do any testing on xApp side.
  4. thoralf to sent invitation to Subhash &co for Friday → DONE
    1. agreed on configuration transfer to be handled similar to function definitions as E2APv2.0 now defines configuration updates as replacing instead of updating existing component configuration entries.
    2. E2 reset to be handled as new state that xApps see: "connected---transition1-->connected-but-under-reset---transition2-->connected". We use a timer, instead of strict xapp and submgr confirmation that all has been cleaned up. xApps shall resubscribe only after transition2. xapps can assume that submgr has removed all subscriptions (in its view of the world) and that the E2 node has removed them (in its view of the world)
    3. Subhash will send slideset for this during this week
2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
    1. hw-go issue with old xapp frame lib used. - needs to be updated.
    2. in same mail thread there's another issue - to be discussed over mail.
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
3. in DU
  1. 2022-02-23 Former user (Deleted) reported in TOC that this work is done.
anybody working on this RIC-705 Alexandre wants to know.
1. 2022-02-15: Thoralf sent mail to E & A.
2. 2022-02-21: Alexandre agree to work on RIC-705. Might also later work on RIC-641. To keep track of things, I (Thoralf) took the liberty to give Alexandre a separate subteam tag in Jira: “subteam-utfpr” and marked RIC-705 as per the convention. I updated the links in §7.2 accordingly in Jira usage conventions.
RICAPP agenda: RICAPP Meetings.

2022-02-15

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. not done this time.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. ric-plt/alarm-go 0,0 // no bugs (2021-11-22 → 2022-02-13 )
4. ric-plt/appmgr 19,3 // 1 major bug (2022-01-30 → 2022-02-13)
5. ric-plt/e2mgr 88,6 // no bugs (2021-11-18 → 2022-02-14)
6. ric-plt/lib/rmr 86,2 // no bugs (2021-11-23 → 2022-02-08)
7. ric-plt/sdlgo 25,2 → 90,2// no bugs (2022-01-31 → 2022-02-14) → RIC-887 fixed reporting job issue
8. ric-plt/submgr 51,2 // no bugs (2022-01-30 → 2022-02-13)
9. ric-plt/tracelibcpp 0,0 // 1 major bug (2022-01-25 → 2022-02-08)
10. ric-plt/tracelibgo 96,2 //0 bugs (2022-01-30 → 2022-02-13)
11. ric-plt/xapp-frame 0,0 // no bugs (2021-11-22 → 2022-02-13)
12. ric-plt/xapp-frame-cpp 95,6 // no blocker bugs (2022-01-26 → 2022-02-09)
Every time: Check if there are new bug reports in JIRA: link
1. new RIC-885, RIC-887 (sdlgo) → fixed
2. new RIC-883 xappframe-cpp → Alexandre fixed this
3. RIC-872 → Alexandre fixed this
4. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
5. RIC-857 sporadically RMR takes multiple minutes before being "ready"
6. RIC-835 → 2021-12-07 news from Viktor
7. RIC-837 RMR is not forwarding messages from E2T to E2M
8. RIC-840 Unable to deploy E2Term on Dawn release
9. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
10. fixed: RIC-872, RIC-883, RIC-885, RIC-887
11. anybody would like to get more familiar with RMR?
Cross-check with A. if he has updated the instructions to point to helm3.
1. A. can look on this on Jan-31 and update here: new section here - https://docs.o-ran-sc.org/projects/o-ran-sc-it-dep/en/latest/installation-guides.html
2. 2022-02-14: there's a review for this documentation change (change 7638). The review fails in LF CI/Jenkins in SMO/non-rt RIC related parts. Asked help from James by e-mail. James raised a request to LF: IT-23628
Sunil still to discuss with other team members for other items from subteam-h
1. 2022-02-15 done and clarified
  1. RIC-878 - A1 mediator testing in nanobot
  2. RIC-860 xapp testing nanobot enhancements: wider coverage of functionality, e.g., Subscription deletion
  3. RICAPP-176 adapting bouncer xapp to REST subscription interface.
  4. Other tickets CI/CD and Code coverage tickets, I am still looking for the resources to work on that.
James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
1. 2022-01-27 (Mail sent)
2. 2022-02-15: resending with the right David
Progress on E2APv2.0?
1. in ric platform and simulators?
  1. any questions/comments on Arun's slideset in RIC-722 ?
  2. Any first code/design review request that Arun and Dhiraj should review?
  3. progress, subhash: simulator adapted. E2T changes internally ready.
  4. config xapp and E2 manager interface.
  5. discuss E2 reset
  6. thoralf to sent invitation to Subhash &co for Friday
  7. Subhash&co did not plan to do any testing on xApp side.
2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
3. in DU?
anybody working on this RIC-705 Alexandre wants to know.
1. 2022-02-15: Thoralf sent mail to E & A.
RICAPP agenda: RICAPP Meetings.

2022-02-01

Recording: link to zoom recording

Thoralf-TODO-cross-check with A. if he has updated the instructions to point to helm3.
1. A. can look on this on Jan-31 and update here: new section here - https://docs.o-ran-sc.org/projects/o-ran-sc-it-dep/en/latest/installation-guides.html
Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7450 ok
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/7465 ok
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7481 ok
4. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/7515 ok
5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7592 ok (note this is the E2APv2.0 support in submgr in subbranch "e2ap-02.00" - only to be merged with other E2APv2.0 changes)
6. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7587 ok
7. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7610 ok
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. ric-plt/alarm-go 0,0 // no bugs (2021-11-22 → 2022-01-30 )
4. ric-plt/appmgr 17,5 → 19,3 // 1 major bug (2021-11-22 → 2022-01-30)
5. ric-plt/e2mgr 88,6 // no bugs (2021-11-18 → 2022-01-30)
6. ric-plt/lib/rmr 70,4 → 86,2 // no bugs (2021-11-23 → 2022-01-25)
7. ric-plt/sdlgo 47,4 → 32.4 → 25,2 // no bugs (2021-11-23 → 2022-01-31) → raise bug
8. ric-plt/submgr 44,8 → 47,4 → 51,2 // no bugs (2021-11-22 → 2022-01-30)
9. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-11-16 → 2022-01-25)
10. ric-plt/tracelibgo 94,7 → 96,2 //0 bugs (2021-11-22 → 2022-01-30)
11. ric-plt/xapp-frame 0,0 // no bugs (2021-09-30 → 2021-11-22) - same as before.
12. ric-plt/xapp-frame-cpp 96,3 → 95,6 // still 2 blocker bugs → 0 blocker bugs (fix) (2021-11-17 → 2022-01-26)
Every time: Check if there are new bug reports in JIRA: link
1. new: RIC-872 needs someone to fix. → Alexandre working it. Discussion in revies
2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
3. RIC-857 sporadically RMR takes multiple minutes before being "ready"
4. RIC-835 → 2021-12-07 news from Viktor
5. RIC-837 RMR is not forwarding messages from E2T to E2M
6. RIC-840 Unable to deploy E2Term on Dawn release
7. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
8. fixed: RIC-880, RIC-875, RIC-873, RIC-869, RIC-862
9. anybody would like to get more familiar with RMR?
F release
1. schedule
  1. Sprint F release dev sprint 1: Feb-21 to Mar-13 (as per Releases)
  2. Sprint F release dev sprint 2: Mar-14 to Apr-3
  3. Sprint F release dev sprint 3: Apr-4 to Apr-24
  4. Sprint F release dev sprint 4: Apr-25 to May-15 (last planned development sprint)
  5. Sprint F release dev sprint5: May-16 to Jun-5 (only for unplanned last-minute development items)
2. Filter All RICP items: F release only (links copied from Jira usage conventions)
  1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-s and all teams.
  2. committed items only: all teams (committed)
  3. items that are known to require work, but are currently not in F release: link
3. update xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
4. Sunil still to discuss with other team members for other items from subteam-h
5. James: RSAC recommended incorporating OTF in testing (David K. can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James. 2022-01-27 (Mail sent)
James had a meeting with Powderlab in UofU on using their lab setup for testing. They have earlier tested OSC D release (and others). James is thinking about using this. Low hanging fruit would be to see if we can run our end-2-end robot test cases in this lab.
1. POWDER testbed ORAN demo submission at MWC 2022: https://oranalliance.atlassian.net/wiki/spaces/OAH/pages/2330100360/PROCESSING+MWC-B-22-14+University+of+Utah
Needed: overview of what is in golang and what in python and what in c++ and what is missing →
1. Added this as RIC-882 (F release)
RICAPP agenda: RICAPP Meetings.

2022-01-18

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

Thoralf-TODO-cross-check with Abdulwahid if he has updated the instructions to point to helm3.
Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. we did not do this this time.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. We did not do this this time
Anybody willing to work on them?
Every time: Check if there are new bug reports in JIRA: link
1. new: RIC-872 needs someone to fix. → Alexandre fixed this.
2. RIC-875 thoralf to gheck with timo if fixed already.
3. All others thoralf still to gpo thporugh if any news on them.
4. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
5. ~~RIC-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak) → Alexandre~~ → DONE
6. RIC-861 re-enable RMR libary's module tests
7. RIC-857 sporadically RMR takes multiple minutes before being "ready"
8. RIC-835 → 2021-12-07 news from Viktor
9. RIC-837 RMR is not forwarding messages from E2T to E2M
10. RIC-840 Unable to deploy E2Term on Dawn release
11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
12. fixed: RIC-862, RIC-828, RIC-836, RIC-858, RIC-859, RIC-863, RIC-865
13. anybody would like to get more familiar with RMR?
F release
1. schedule
  1. Sprint F release dev sprint 1: Feb-21 to Mar-13 (as per Releases)
  2. Sprint F release dev sprint 2: Mar-14 to Apr-3
  3. Sprint F release dev sprint 3: Apr-4 to Apr-24
  4. Sprint F release dev sprint 4: Apr-25 to May-15 (last planned development sprint)
  5. Sprint F release dev sprint5: May-16 to Jun-5 (only for unplanned last-minute development items)
2. Filter All RICP items: F release only (links copied from Jira usage conventions)
  1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-s and all teams.
  2. committed items only: all teams (committed)
  3. items that are known to require work, but are currently not in F release: link
3. update xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
  1. kpimon
  2. bouncer
  3. all hello-world xapps (hw-go already uses submgr REST ifc)
  4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
4. Sunil still to discuss with other team members for other items from subteam-h
5. James: RSAC recommended incorporating OTF in testing (David K. can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
Needed: overview of what is in golang and what in python and what in c++ and what is missing
E-release Demo for E2APv1.1 and support for OID in function definitions (Naman)
RICAPP agenda: RICAPP Meetings.

2022-01-04

Recording: link to zoom recording

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

2021-12-21

Recording: link to zoom recording

We will have the E-release demo in one hour from now: 2021-12-21 Release E
next meeting: Jan-4-2022 focus will be the ric xapp project. After this the next one is on Jan-18 which will again handle xapp and ric platform combined.
1. Any input for F release, pls. send to Thoralf (back in office on Jan-10)
Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/6964 ok, not relevant as only API definition
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7151 ok
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7152 ok
4. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6712 ok, as a test tool.
5. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7398 ok
6. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7428 ok
7. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7290 ok
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. We did not do this this time
Anybody willing to work on them?
Every time: Check if there are new bug reports in JIRA: link
1. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
2. RIC-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak) → Alexandre
3. RIC-861 re-enable RMR libary's module tests
4. RIC-857 sporadically RMR takes multiple minutes before being "ready"
5. RIC-835 → 2021-12-07 news from Viktor
6. RIC-837 RMR is not forwarding messages from E2T to E2M
7. RIC-840 Unable to deploy E2Term on Dawn release
8. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
  1. 2021-12-21: Trying to get bandwidth for this during F release.
9. fixed: RIC-828, RIC-836, RIC-858, RIC-859, RIC-863, RIC-865
10. anybody would like to get more familiar with RMR?
Action items
1. SCCL update - Matti will check with Tracy
  1. still discussion within O-RAN-SC still ongoing
  2. publication of O-RAN specs of July train should happen any time now.
  3. O-RAN specs of July train have been released. Need to check if any parts have been put under SCCL
2. E2 simulator seeing E2 setups not passing through: Wiki page updated but no word from Nokia - trying 100 subscriptions - testing still in progress, will check with Amit if bug has been filed (nokia waiting for test case being run in newer cloud environment). Amit raised RIC-852 for this.
  1. 2021-12-21 no news from Nokia side. → see RIC-852 above
E release
1. E release images test-deployed. E2 Setup works, xApp deployment. All manual checks.
2. TOC approved E release on Dec-15. Release images are here: Near-RT RIC (E release)
3. 2021-12-21 Thoralf double-checked that branch "e-release" has been created in all components and also updated release checklist (all OK now): Release criteria checklist - Release E. All criteria "ok"
Preliminary planning for the F release
1. Not completed in E release (spill over into F): RIC-849, and all from this list.
2. Candidate list for F release (priority column as per Thoralf's best understanding) https://jira.o-ran-sc.org/issues/?jql=(fixVersion%20in%20(ZZZ_future)%20or%20fixVersion%20in%20(F)%20)AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20%20ORDER%20BY%20component%20ASC
3. we will discuss this again in the next meeting.
4. Thoralf to send a reminder.
Nitin: submgr subscription REST interface: https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/xapp-frame.git;a=tree;f=api
RICAPP agenda: RICAPP Meetings.

2021-12-07

Recording: link to zoom recording

Anybody new who wants to introduce him/herself?
Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. we did not do this this time.
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. We did not do this this time
Anybody willing to work on them?
Every time: Check if there are new bug reports in JIRA: link
1. RIC-865 → Done fix unit tests in xapp-frame-py
2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
3. RIC-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak)
4. RIC-861 re-enable RMR libary's module tests
5. RIC-858 → Done
6. RIC-857 sporadically RMR takes multiple minutes before being "ready"
7. RIC-835 → 2021-12-07 news from Viktor
8. RIC-836 → Done
9. RIC-837
10. RIC-840
11. RIC-852
12. anybody would like to get more familiar with RMR?
13. Can Alexandre help with the RMR bug RIC-858?
Action items
1. SCCL update - Matti will check with Tracy
  1. still discussion within O-RAN-SC still ongoing
  2. publication of O-RAN specs of July train should happen any time now.
  3. O-RAN specs of July train have been released. Need to check if any parts have been put under SCCL
2. E2 simulator seeing E2 setups not passing through: Wiki page updated but no word from Nokia - trying 100 subscriptions - testing still in progress, will check with Amit if bug has been filed (nokia waiting for test case being run in newer cloud environment). Amit raised RIC-852 for this.
  1. 2021-12-07 no news from Nokia side.
Expected that we stop development end of November. In Dec-7 meeting we will do status check and after this only exceptional (specially managed) commits to near-RT RIC for the rest of December.
1. reverting a commit related to simulator in https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/7253
2. E release images test-deployed. E2 Setup works, xApp deployment. All manual checks.
Preliminary planning for the F release
1. likely not completed in E release (spill over into F): RIC-647, and all from this list.
2. Candidate list for F release (priority column as per Thoralf's best understanding) https://jira.o-ran-sc.org/issues/?jql=(fixVersion%20in%20(ZZZ_future)%20or%20fixVersion%20in%20(F)%20)AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20%20ORDER%20BY%20component%20ASC
3. we will discuss this again in two weeks from now.
4. Thoralf to send a reminder.
Thoralf to arrange release demo for Dec-21: Release Demo with e.g. OID, submgr changes and E release example deployment
RICAPP agenda: RICAPP Meetings.

2021-11-23

Recording: link to zoom recording

Anybody new who wants to introduce him/herself?
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).
every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. ric-plt/alarm-go 0,0 // no bugs (2021-09-30 → 2021-11-22)
4. ric-plt/appmgr 0,0 → 17,5 // 1 major bug ( 2021-09-30 → 2021-11-22)
5. ric-plt/e2mgr 88,0 // no bugs (2021-09-28 → 2021-11-18)
6. ric-plt/lib/rmr 86,1->70,4 // no bugs (2021-09-07 → 2021-11-23) → raise bug
7. ric-plt/sdlgo 47,4 → 32.4// no bugs (2021-09-28 → 2021-11-23) → raise bug
8. ric-plt/submgr 44,8 → 47,4// no bugs (2021-09-30 → 2021-11-22)
9. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-08-10 → 2021-11-16)
10. ric-plt/tracelibgo 94,7//0 bugs (2021-09-30 → 2021-11-22)
11. ric-plt/xapp-frame 0,0 // no bugs (2021-09-30 → 2021-11-22) - same as before.
12. ric-plt/xapp-frame-cpp 96,3 // still 2 blocker bugs (2021-09-22->2021-11-17)
Anybody willing to work on them?
Every time: Check if there are new bug reports in JIRA: link
1. RIC-858 → new
2. RIC-835
3. RIC-836 → Done
4. RIC-837
5. RIC-840
6. RIC-852
7. RIC-857
8. anybody would like to get more familiar with RMR?
9. Can Alexandre help with the RMR bug RIC-858?
Action items
1. SCCL update - Matti will check with Tracy
  1. still discussion within O-RAN-SC still ongoing
  2. publication of O-RAN specs of July train should happen any time now.
2. E2 simulator seeing E2 setups not passing through: Wiki page updated but no word from Nokia - trying 100 subscriptions - testing still in progress, will check with Amit if bug has been filed (nokia waiting for test case being run in newer cloud environment). Amit raised RIC-852 for this.
3. DONE-2021-11-23 James (INT PTL): Sent email to PTLs on what is needed. Need automation of testing for all projects.
  1. Any comments?
  2. VES alarm events, for example (James)
  3. James: non-rt RIC - near-RT RIC integration A1. Discuss With Sunil/Matti/James, e.g. TS xApps has disabled code for this.
  4. A1-EI could also be integrated (Subhash raised this)
  5. Ramesh - resue E2 simulator
  6. DONE-2021-11-23: thoralf to start mail thread on this.
Expected that we stop development end of November. In Dec-7 meeting we will do status check and after this only exceptional (specially managed) commits to near-RT RIC for the rest of December.
Subhash (sent this before the meeting)
1. E2AP v1.1 support [RIC-640 and RIC-638] : We are working on implementation of RIC-640 and RIC-638. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/6931 https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/7041 https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/7050
2. A1 mediator (Could be moved to F release) (RIC-647): partial implementation is done to support A1-P API which is not enabled yet.
3. RICDMS (Could be moved to F release) [RIC-714] : Implementation is not yet started only we have finalized the API.
4. RICCTL (Could be moved to F release) [RIC-445] : Pushed some sample commands for A1-P related operations. We are discussing with our internal team to use code from ONAP community which is taking little time.
Preliminary planning for the F release
1. likely not completed in E release (spill over into F): RIC-647, and all from this list.
2. Candidate list for F release (priority column as per Thoralf's best understanding) https://jira.o-ran-sc.org/issues/?jql=(fixVersion%20in%20(ZZZ_future)%20or%20fixVersion%20in%20(F)%20)AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20%20ORDER%20BY%20component%20ASC
3. we will discuss this again in two weeks from now.
Do we update to golang 1.16 (in go.mod) in all repos? Juha now updated golang version in Ubuntu base image along with Ubuntu image update to 20.04.
1. A1-Med is using 1.16; others need to be checked
2. I understand that we updated this together with the Ubuntu 20.04 update during the last two weeks.
Nitin: installation using helm3.
1. Sangeetha: this should be possible since Cherry. Helm charts are the same.
Calico should also work.
Sangeetha asked for bug reports if any help is needed. Thoralf commented that before starting to work check with Thoralf if already someone working on the item.
RICAPP agenda: RICAPP Meetings.

2021-11-09

Recording: link to zoom recording

Anybody new who wants to introduce him/herself?
1. GG (Parallel Wireless): wants to participate and possible contribute
2. Viktor (contractor for globallogic/ARM) working on the ARM64 port
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).
every second time: Review code coverage stats and blocker code smells
...
1. Anybody willing to work on them?
Every time: Check if there are new bug reports in JIRA: link
1. RIC-835
2. RIC-836 → Done
3. RIC-837
4. RIC-840
5. RIC-852
6. RIC-857
7. anybody would like to get more familiar with RMR?
  1. Alexandre offered to help a bit and would like to get familiar with RMR.
Action items
1. SCCL update - Matti will check with Tracy
  1. still discussion within O-RAN-SC still ongoing
  2. publication of O-RAN specs of July train should happen any time now.
  3. no news (2021-11-23)
2. E2 simulator seeing E2 setups not passing through: Wiki page updated but no word from Nokia - trying 100 subscriptions - testing still in progress, will check with Amit if bug has been filed (nokia waiting for test case being run in newer cloud environment). Amit raised RIC-852 for this.
  1. 2021-11-23: still open as we focus on RMR - E2T case
3. James (INT PTL): Sent email to PTLs on what is needed. Need automation of testing for all projects.
  1. Any comments?
  2. VES alarm events, for example (James)
  3. James: non-rt RIC - near-RT RIC integration A1. Discuss With Sunil/Matti/James, e.g. TS xApps has disabled code for this.
  4. A1-EI could also be integrated (Subhash raised this)
  5. Ramesh - resue E2 simulator
  6. TODO thoralf to start mail thread on this.
  7. 2021-11-23: Thoralf to send
Thoralf recorded a 24min step-by-step video on how to deploy the Dawn release: 2021-11-05 Demo video release Dawn
1. anybody has time to do part of the demo with public E2 simulator?
Expected that we stop development end of November. In Dec-7 meeting we will do status check and after this only exceptional (specially managed) commits to near-RT RIC for the rest of December.
Arm port (do we need Jenkins CI jobs?)
1. new merge requests
2. RIC-835 - Viktor offered possibility of access to ARM hardware if needed (Subhash said restarting the componet helps)
Preliminary planning for the F release
1. likely not completed in E release (spill over into F): RIC-647, and all from this list.
2. Candidate list for F release (priority column as per Thoralf's best understanding) https://jira.o-ran-sc.org/issues/?jql=(fixVersion%20in%20(ZZZ_future)%20or%20fixVersion%20in%20(F)%20)AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20%20ORDER%20BY%20component%20ASC
We did not discuss this today: Do we update to golang 1.16 (in go.mod) in all repos? Juha now updated golang version in Ubuntu base image along with Ubuntu image update to 20.04.
1. A1-Med is using 1.16; others need to be checked
RICAPP agenda: RICAPP Meetings.

2021-10-26

Recording: link to zoom recording

Note that originally we wanted to do some preliminary planning for the F release, but I did not have time to prepare for this, So we can handle this only on Nov-9
Anybody new who wants to introduce him/herself?
1. LoreLei - PlugFests, RIC in PowderLab, proof of concept - AT&T
2. Yasmin, Joyce, Mirette - Dell
3. Wasi, Nitin, Praneeth - Mavenir
4. David Allabaugh - Fujitsu - WG-10 - info modelling
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. ...
every second time: Review code coverage stats and blocker code smells
...
1. Anybody willing to work on them?
Every time: Check if there are new bug reports in JIRA: link
1. no new items
Do we update to golang 1.16 (in go.mod) in all repos? Juha now updated golang version in Ubuntu base image along with Ubuntu image update to 20.04.
1. A1-Med is using 1.16; others need to be checked
Subhash:
1. RIC-CTL repo created, RIC-DMS repo created for O2 related interfaces; no blockers
2. SCCL update - Matti will check with Tracy
RIC tester: Wiki page updated but no word from Nokia - trying 100 subscriptions - testing still in progress, will check with Amit if bug has been filed.
Nitin: Can RIC be installed on anything but Ubuntu? See ric-dep folder.
James (INT PTL): Sent email to PTLs on what is needed. Need automation of testing for all projects.
RICAPP agenda: RICAPP Meetings.

2021-10-12

Recording: link to zoom recording

Anybody new who wants to introduce him/herself (michel p (from NU working with Mavenir))
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).
Every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. ric-plt/alarm-go 0,0 // no bugs (2021-01-31 → 2021-09-30)
4. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31 → 2021-09-30)
5. ric-plt/e2mgr 88,0 // no bugs (2021-01-30 → 2021-09-28)
6. ric-plt/sdlgo 47,4 // no bugs (2021-09-28 → 2021-09-30)
7. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31 → 2021-09-30)
8. ric-plt/submgr 33,4 → 44,8 // no bugs (2021-01-31 → 2021-09-30 (fail) )
9. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31 → 2021-09-30)
10. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31 → 2021-09-30 (fail)) - same as before.
11. Anybody willing to work on them?
Every time: Check if there are new bug reports in JIRA: link
1. no new items
A reminder related to the visibility of LF IT support requests: "If you raise issues to LF support that are sensible to make visible to others, pls. first raise a ticket to join "ORAN" organization in the support tool: "When these organizations (ORAN) were created in the beginning, we added by default all members from the committer groups into the organization. If at that time a particular user was not part of any group or just joined the community, then they will not be automatically added into the oran organization. Going forward, the new user will need to create a support ticket to be added to the organization."
https://gerrit.o-ran-sc.org/r/admin/repos/ric-plt/ricctl now exists. Also added in Scope of the near-RT RIC platform and its components (summary)
F release is coming. Need to start some planning on F release. Anything you would like to work on? Anything we should be working on. Let's do a bit of planning in the meeting two weeks from now.
Subhash: shared updates from Samsung
1. E2APv1.1 using simulator from sim/... This project also requires some cleanup. Ron Shacham
  1. there are more changes coming in this simulator area (not further elaborated here)
  2. let's come back to this in F release planning
2. A1 reimplementation. A1-P one read-like ifc now ported. Rest of work still remaining.
3. O2 (dmscli). Thoralf to schedule meeting for Thursday.
4. ricctl repo exists. work can start.
Alexandre raised RIC-826
1. thoralf to double-check ric-dep using helm3.
2. original bug in RIC-826 was acatully fixed and conifirmed by Alexandre. Thoralf to clsoe.
3. Alexandre to write e-mail to Thoralf about the local image problem.
SCCL: https://www.o-ran.org/sccl
Post-meeting there was a discussion on a new xApp with Mavenir and various others: link
RICAPP agenda: RICAPP Meetings.

2021-09-28

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/vespamgr/+/6638 ok, only counter definitions.
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6704 ok
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6712 ok, Thoralf asked authors for more info. Feedback: The change is done for sdltool that is used for testing (robot testing etc.). We do not have any unit tests for this test tool in "src/cli/*"
4. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/6705 ok
5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6766 ok
Skipped today: every second time: Review code coverage stats and blocker code smells
1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Only a few components where code coverage reports work:
4. ric-plt/e2mgr 88,4 → 88,0 // no bugs (2021-01-30 → 2021-09-28) there was a minor code addition
5. ric-plt/lib/rmr 86,1 // no bugs (2021-08-17 → 2021-09-07)
6. ric-plt/sdlgo 45,5 → 47,4 // no bugs (2021-02-01 → 2021-09-28)
7. ric-plt/xapp-frame-cpp 95,6 // still 2 blocker bugs (2021-08-04 → 2021-09-22) - same as before. Anybody willing to work on them?
Every time: Check if there are new bug reports in JIRA: link
1. RIC-828 (some security issue in DBAAS container) → already fixed.
2. RIC-830 (raised by Subhash after discussion): unless someone has an idea how to do auto-tagging for go modules that are in the same repo, Thoralf suggests to close this as "not fixed" and we continue with manual labelling of each module.
discuss RIC-184 and why we still have helm2 as in RIC-826. To me it seems RIC should be deployed using helm3, but Nune, for example says still, "You should use helm3 only for xApp deployment. For the deployment of platform components, you still need to use helm2".
1. old report (checked already two weeks ago): RIC-826 discusses issue around helm3 usage in app manager. Anybody volunteering (HCL?) to check if we still have helm2 instructed somewhere in it/dep or ric-plt/ric-dep?
2. Sunil & Sangeetha to check if we still have any helm2 references in code or in wiki pages for Dawn.
3. Onboarding (provided by xApp manager) is already using helm3, but the helm2 question is about deploying the base RIC platform.
E2 simulator? Which we is still maintained:
1. https://gerrit.o-ran-sc.org/r/gitweb?p=sim%2Fe2-interface.git;a=summary
  1. originally developed by AT&T and managed by Alex. Not sure if V... is still maintaining.
2. https://gerrit.o-ran-sc.org/r/gitweb?p=it/test.git;a=blob;f=ric_benchmarking/e2-interface/e2sim/src/ASN1c/E2AP-PDU.h
  1. used by HCL for e2sim deployment and bouncer xapp communication. Here the version which we are using in E2AP-PDU.h is E2APv1.01 (ok to use).
3. https://gerrit.o-ran-sc.org/r/gitweb?p=it/test.git;a=blob;f=simulators/e2sim/ASN1c/E2AP-PDU.h
4. Summary Ask Alex to continue supporting/working in sim repo's e2 simulator. The other one that should be continued is it/test's ric_benchmarking (as it works wityh bouncer xApp). (b) was taken from (a) and further enhanced.
5. Summary Delete the simulator in it/test's simulators/e2sim subdirectory. Thoralf to file a JIRA case for this towards the infra project. Thoralf filed: INT-144
HCL needs access to it/test (still open, Sunil to check)
Samsung items
1. RIC-653 A1 image in deplooyment is now updated.
2. RIC-812 thoralf to mark thjis item as dropped from E release
3. RIC-647 needs to have UTR from the beginning
4. RIC-445 new repo is requested from TOC: "ricctl"
5. RIC-714 Subhash to schedule meeting with Nune (=Abukar) and Thoralf
SDRAN (ONF) implementation now is open-sourcing the 1.1 version. If there's re-use potential (e.g. in simulator), let's do that.
RICAPP agenda: RICAPP Meetings.

2021-09-14

Recording: link to zoom recording

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. (Thoralf checked on 2021-09-10 no large commits)
Skipped today: 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. Not done this time // anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
Every time: Check if there are new bug reports in JIRA: link
1. old report RIC-826 discusses issue around helm3 usage in app manager. Anybody volunteering (HCL?) to check if we still have helm2 instructed somewhere in it/dep or ric-plt/ric-dep?
2. (Thoralf checked on 2021-09-10 no new items)
Nokia had to move O1-related JIRA items to post-E release: RIC-655, RIC-656, RIC-497 and RIC-798. Also there are still legal issues around the copyright of definitions from 3GPP specs that are needed when implementing O1.
Subhash:
1. RIC-653: A1 Mediator image old - has been corrected. Another issue with helm - has also been resolved. Needs to be reviewed. Somebody from Nokia need to update RIC deployment.
2. New repo requested for RIC CLI - still pending Thoralf. A1 Mediator go version will use the existing repo (replacing python version)
3. Naman pushed an update to python xapp framework - under review.
HCL:
1. Continue on RIC benchmarking.
Can we share ONeS slides to Subhash now?
RICAPP agenda: RICAPP Meetings.

2021-08-31

Exceptionally, we did not have a meeting today.

2021-08-17

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6584 OK
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/6551 OK (move of implementation from one repo to another)
Skipped today: 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
  1. ric-plt/a1 85,3 // no bugs (2021-01-26)
  1. ric-plt/alarm-go 0,0 // no bugs (2021-01-31)
  2. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31)
  3. ric-plt/asn1-documents not applicable
  4. ric-plt/dbaas 0,0 // 2 blocker bugs in UT code (2021-01-27) - seems not to be anymore in latest version of source code.
  5. ric-plt/e2 0,0 // 2 blocker bugs (2021-06-18) - Thoralf raised RIC-802 and send e-mail to Dhiraj, Subhash and Naman. 2021-08-17: RIC-802 is for subteam-n in E. No other news
  6. ric-plt/e2mgr 88,4 // no bugs (2021-01-30)
  7. ric-plt/lib/rmr 86,1 // no bugs (2021-08-17)
  8. ric-plt/rtmgr 77,8 // no bugs (2021-01-31)
  9. ric-plt/sdl 66,6 // 1 minor vulnerability bug (2021-01-29)
  10. ric-plt/sdlgo 45,5 // no bugs (2021-02-01)
  11. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31)
  12. ric-plt/submgr 33,4 // no bugs (2021-01-31)
  13. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-08-10)
  14. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31)
  15. ric-plt/vespamgr 79,0 // no bugs (2020-12-07)
  16. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31)
  17. ric-plt/xapp-frame-cpp 95,6 // still 2 blocker bugs (2021-08-04) - same as before. Anybody willing to work on them?
  18. ric-plt/xapp-frame-py 96,3 // 0 blocker bugs (2021-01-26)
  19. com/golog 80,7 // no bugs (2021-01-31)
  20. com/log 73,5 // 1 blocker bug and 8 minor ones (2021-01-27) - same as before. Need to fix Sonarcube issues (with Java version) first.
  21. com/pylog 33,7 // 11 major and minor bugs (2021-01-26)
Every time: Check if there are new bug reports in JIRA: link
1. new: RIC-826 (discussion ongoing)
Note the presentation slides and video from "Open Source Conference 2021 (5G, IoT and Edge Computing) (organized by the IEEE ComSoc Bangalore chapter and Samsung SOSCON" is now available here: Overall architecture (not component-specific)
E2-related specs are now in IPR approval phase on O-RAN alliance side (O-RAN alliance member only access):
1. O-RAN.WG3.UCR-v01.00: https://oranalliance.atlassian.net/wiki/download/attachments/2068513840/O-RAN.WG3.UCR-v01.00.docx?api=v2
2. O-RAN.WG3.E2GAP-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/213254315/O-RAN.WG3.E2GAP-v02.00.docx?api=v2
3. O-RAN.WG3.E2AP-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/226295809/O-RAN.WG3.E2AP-v02.00.docx?api=v2
4. O-RAN.WG3.E2SM-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/244318246/O-RAN.WG3.E2SM-v02.00.docx?api=v2
5. O-RAN.WG3.E2SM-KPM-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/244318246/O-RAN.WG3.E2SM-KPM-v02.00.docx?api=v2
6. O-RAN.WG3.E2SM-RC-v01.00 https://oranalliance.atlassian.net/wiki/download/attachments/244318246/O-RAN.WG3.E2SM-RC-v01.00.docx?api=v2
E release "committed" content: link
Design or coordination aspects of some items of the E release
1. RIC-638 config transfer E2APv1.1 (Subhash)
2. RIC-445 CLI (demo from subhash as well)
3. NOT today: RIC-80 and RIC-796 (REST interface for subscriptions only) (Possibly Anssi)
4. RIC-809 subscription interface (Supreeth)
5. RIC-805 We are likely moving the "remove old API part" only in the next release, i.e., maintain old and new in parallel for one release. Team needs some more discussion before something can be presented. Namespace in new implementation is given as part of each get/set method. Previously the namespace was given during SDK initialization. During E release we will only deprecate the old interface, but keep it. Only in F release we will remove.
6. Mavenir thinking about gRPC as communication mechanism (Matti to send e-mail address to Thoralf).
  1. probably for next meeting due to holiday
7. Discuss disaggregated VES agent use case and impact on RIC. Thoralf
  1. This is O-RAN O1 release 6 work (July-Dec 2021). Thoralf understands it introduces a "VES proxy agent" into the Edge CloudInfra that on the left gets VES events from CNFs (e.g., via REST events, or (the new thing) a CloudInfra Kafka instance) and on the right side forwards these to the SMO (e.g., directly into Kafka). Not sure if left-side injection can also be done via O1 websocket performance data streaming.
  2. There might be some issues around data schema alignment that need to be addressed
  3. Anyway, from CNF point of view seems to be one more way of sending statistics/metrics out towards the SMO. For now let's focus on existing O1 (files or websocket streaming) means. Also note that statistics are currently collected via Prometheus. I.e., if, we'd be talking about a new or update mediator component that takes the data from Prometheus and sends it to that new "VES proxy agent".
  4. Note that performance related there are also activities under the Prometheus umbrella that might be relevant, e.g., https://openmetrics.io/
  5. So this seems not to be relevant for the E release of near-RT RIC.
...
RICAPP agenda: RICAPP Meetings.

2021-08-03

Recording: link to zoom recording

Skipped today: 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).
Skipped today: 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
Every time: Check if there are new bug reports in JIRA: link
E release timeline: Releases and see §6 in Jira usage conventions
1. Sprint E release dev sprint 1: Aug-23 to Sep-12
2. Sprint E release dev sprint 2: Sep-13 to Oct-3
3. Sprint E release dev sprint 3: Oct-4 to Oct-24
4. Sprint E release dev sprint 3: Oct-25 to Nov-14 (last planned development sprint)
5. Sprint E release dev sprint 5: Nov-15 to Dec-3 (only for unplanned last-minute development items)
E release planning
...
RICAPP agenda: RICAPP Meetings.

2021-07-20 no meeting

2021-07-06

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/4880 OK
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/6395 OK
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/6301 OK as helm chart adaptations that just did some same renaming in many files.
4. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/6447 OK
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
New item for every meeting: check if there are new bug reports in JIRA: link
Dawn release criteria checklist filled in: Release criteria checklist - Release D
Sonarcube jobs are failing because of the same issue it seems (grep for ERROR): https://jenkins.o-ran-sc.org/view/com-log/job/com-log-autotools-sonarqube/55/ and https://jenkins.o-ran-sc.org/view/ric-plt-e2mgr/job/ric-plt-e2mgr-sonar-prescan-script/ and many more. Chaitanya raised https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22326 for this. It's related to opensdk. No fix yet available, but ideas what to do.
1. Sunil will check with Chaitanya and Alok
thoralf on holiday, matti as well. No meeting in two weeks from now. And next meeting first week of August: On Aug-3.
Release E planning. Thoralf to send e-mail as kick-off.
RICAPP agenda: RICAPP Meetings.

2021-06-22

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/com/asn1c/+/6266 OK
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6132 OK
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6134 OK
4. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6128 OK
5. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6014 OK
6. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6157 OK (existing test case was updated with new attributes)
7. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlpy/+/6060 OK
8. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6167 OK
9. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/6183 OK
10. https://gerrit.o-ran-sc.org/r/c/ric-plt/libe2ap/+/6131 OK (as per meeting minutes from 2021-05-25)
11. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/6199 OK (all code copied from other place into 3rdparty subdir)
12. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/6237 OK (removal)
13. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6241 OK (test case was adapted to change in data type)
14. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6242 OK (only documentation)
15. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlpy/+/6261 OK
16. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6211 OK
17. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6265 OK
18. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/6301 OK as Influx helm chart changes.
19. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/6309 OK
20. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6313 OK
21. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6322 OK
22. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6081 OK
23. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/6345 OK
24. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/4880 OK (not yet merged)
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
  1. ric-plt/a1 85,3 // no bugs (2021-01-26)
1. 1. ric-plt/alarm-go 0,0 // no bugs (2021-01-31)
  2. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31)
  3. ric-plt/asn1-documents not applicable
  4. ric-plt/dbaas 0,0 // 2 blocker bugs in UT code (2021-01-27) - seems not to be anymore in latest version of source code.
  5. ric-plt/e2 0,0 // 2 blocker bugs (2021-06-18) - Thoralf raised RIC-802 and send e-mail to Dhiraj, Subhash and Naman.
  6. ric-plt/e2mgr 88,4 // no bugs (2021-01-30)
  7. ric-plt/lib/rmr 86,1 // no bugs (2021-06-22)
  8. ric-plt/rtmgr 77,8 // no bugs (2021-01-31)
  9. ric-plt/sdl 66,6 // 1 minor vulnerability bug (2021-01-29)
  10. ric-plt/sdlgo 45,5 // no bugs (2021-02-01)
  11. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31)
  12. ric-plt/submgr 33,4 // no bugs (2021-01-31)
  13. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-06-22)
  14. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31)
  15. ric-plt/vespamgr 79,0 // no bugs (2020-12-07)
  16. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31)
  17. ric-plt/xapp-frame-cpp 95,6 // 2 blocker bugs (2021-06-23) - Thoralf sent e-mail reminder to Anssi, Ron, Matti.
  18. ric-plt/xapp-frame-py 96,3 // 0 blocker bugs (2021-01-26)
  19. com/golog 80,7 // no bugs (2021-01-31)
  20. com/log 73,5 // 1 blocker bug and 8 minor ones (2021-01-27) - Thoralf sent e-mail to Abdulwahid
  21. com/pylog 33,7 // 11 major and minor bugs (2021-01-26)
Subhash: pls. merge: https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/6365 and re-release
check D-release status: Release criteria checklist template, including e-mail reminder. All components to be handled by Nokia, except A1 → Subhash and RMR → Scott
Subhash shared the information about this public anybody-can-attend conference. It also includes a session about O-RAN SC (Subhash and Thoralf speaking): https://opensource.samsung.com/community/blogList
RICAPP agenda: RICAPP Meetings.

2021-06-08

We used the timeslot for demos: link

2021-05-25

Recording: link to zoom recording

Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/rtmgr/+/5990 ok (Abdulwahid checked this. It's only M size as the commit incorrectly replace many lines with spaces to tabs. Also review 6105 actually fixes some test cases in this area: This should be sufficient as the underlying functionality wasn't changed)
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6132 ok
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/vespamgr/+/5987 ok
4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6014 ok
5. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/5826 (ok, even if no test cases as this is yaml files (Helm chart) repackaged.)
6. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlpy/+/6060 ok
7. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/6061 ok
8. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/6062 ok
9. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6082 ok
10. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6109 ok
11. https://gerrit.o-ran-sc.org/r/c/ric-plt/rtmgr/+/6112 ok
12. https://gerrit.o-ran-sc.org/r/c/ric-plt/libe2ap/+/6131 (still in review, Thoralf commented that unit test cases to be added // we can compromise and extract this into separate item for E)
13. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6081ok (replaced by other review, anyway contains test cases, but will likely be abandoned anyway)
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
  1. ric-plt/a1 85,3 // no bugs (2021-01-26)
  2. ric-plt/alarm-go 0,0 // no bugs (2021-01-31)
  3. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31)
  4. ric-plt/asn1-documents not applicable
  5. ric-plt/dbaas 0,0 // 2 blocker bugs in UT code (2021-01-27) - seems not to be anymore in latest version of source code.
  6. ric-plt/e2 0,0 // 2 blocker bugs (2021-06-18)
  7. ric-plt/e2mgr 88,4 // no bugs (2021-01-30)
  8. ric-plt/lib/rmr 86,1 // no bugs (2021-06-22)
  9. ric-plt/rtmgr 77,8 // no bugs (2021-01-31)
  10. ric-plt/sdl 66,6 // 1 minor vulnerability bug (2021-01-29)
  11. ric-plt/sdlgo 45,5 // no bugs (2021-02-01)
  12. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31)
  13. ric-plt/submgr 33,4 // no bugs (2021-01-31)
  14. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-06-22)
  15. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31)
  16. ric-plt/vespamgr 79,0 // no bugs (2020-12-07)
  17. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31)
  18. ric-plt/xapp-frame-cpp 95,6 // 2 blocker bugs (2021-06-23) - Thoralf sent e-mail to Anssi, Ron, Matti.
  19. ric-plt/xapp-frame-py 96,3 // 0 blocker bugs (2021-01-26)
2. As of 2021-05-25 the following components are missing in the report: ric-plt/alarm-cpp, ric-plt/libe2ap, ric-plt/nodeb-rnib, ric-plt/o1, ric-plt/ric-dep, ric-plt/ric-test, ric-plt/sdlpy, ric-plt/utils. Also ric-plt/jaegeradapter is missing, but we probably abandon that component. So no need to spend time on it.
  1. AP-Sunil: check this with HCL team
3. How to get reports more frequently and up to date?
  1. AP-Sunil: check this with HCL team
4. check why some have zero code coverage
  1. AP-Sunil: check this with HCL team
5. ric-plt/e2 is already being handled via RIC-731 (expected to complete in Dawn)
Thoralf updated the CII evaluation criteria. We are now marked as "passed": Core Infrastructure Initiative (CII) Badging and https://bestpractices.coreinfrastructure.org/en/projects/4605
1. Note I added RC-5 in Release criteria checklist template "RC-5: Check that "blocker" code smells in Sonartype have been addressed"
Status check of D release items.
Subhash's mail - we went through the D release status of various items Samsung was planning to work on.
Sunil. RIC-723 further input needed from Thoralf
1. Chaitanya (taking over from Alok): discuss in Wednesday's call.
Sunil:
1. RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - completed // Subtask RIC-746 (Testing nanobot on top of helm 3 and k8s v1.18 version): Closed // Subtask RIC-747( Study how nanobot tests can be extended to Xapp) - Closed // Subtask RIC-748(Study OTF & Xtesting as a prospective test framework candidate to draw from for ORAN Near RT RIC) : Attached the ppt to the ticket. Given presentation to Thoralf and Matti. As suggested we need some hands-on experience with OTF to confirm on this. OTF installation on local setup - Moved to Next release. // Subtask RIC-779(Xapp Testing Enhancement like Subscription deletion need to be handled using nanobot): Newly created ticket for handling subscription deletion using nanobot automation. Next Release. // Subtask RIC-775(Run nanobot based test automation from - it/test repository on RIC with k8 1.18/helm3 in OSC lab) Working on the vpn client connectivity (Softether). - In-progress // Ticket RIC-791:
  Raised for updating the container tag and pushing in to staging nexus repo.
2. RIC-723 - [Study performance overhead of latest opentracing solutions] - InProgress Able to generate sampling data after getting some help from Thoralf. Continue to work with other scenarios to compare with previous results.
3. RIC-731- [Static code and test coverage for E2] - 90% Completed. // Blocked on RIC-760 for test coverage.HCL working actively on RIC-731
4. RIC-743 Create multiple e2sim for RIC benchmarking // Thoralf created RIC-790 and moved the two remaining subtasks from RIC-150 to it. I closed RIC-150 as DONE
demos again? Yes. On Jun-8 same time slot as this meeting, but 2 hours. Organizational issues after the demo.
1. From last meeting:
  1. Thoralf to discuss demos for Nokia features, e.g. REST subscriptions, O2 CLI (DMS CLI - Subhash wished for this as REST API is the next step)
  2. Possible influxDB demo to show how to use from xApps
  3. Possible demos in devops areas (e.g. RIC-754)
  4. RIC-129 as slideset demo as real data cannot be used in public demo
  5. RIC-773 if ready by demo
  6. demo for RIC-747/RIC-748 slidesets
Remove Scott as committer - AP Thoralf to start mail thread
Replace Rahul with Naman - AP Thoralf to start approval mail on this.
RICAPP agenda: RICAPP Meetings.

2021-05-11

Recording: link to zoom recording

Every time: Check 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. TODO-check in next meeting only
2. not yet merged: https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/5933 - abandoned
3. not yet merged: https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/5826 (conclusion: no unit testing equivalent for YAML files in helm charts). - need to coordinate with Felix - decide to get rid of the 3rdpart directory because files will be slightly modified to refer to common template.
every second time: Review code coverage stats. (Sunil checks if this next step (overview page) is on HCL or on Thoralf's side as next action) - will discuss with Thoralf next time or by email.
1. https://sonarcloud.io/organizations/o-ran-sc/projects?search=ric&sort=coverage
2. NExt Sstep: Thoralf to create some way to maintain history data
When does Dawn end? As per release calendar, normally May-14. However I think we will start late with integrating everything together. So the 3-week sprint that is normally reserved for integration (May-17 – Jun-4) is likely still ok for additions. Based on this I would set a deadline for last commits to Jun-4.
Thoralf still to update or CII evaluation
1. I added RC-5
Heewon's xApp python framework issue related to RIC-773 - some issues still
Update on A1-EI interface implementation.- Able to query A1-EI types from non RT RIC- Issue is clarified from nonRT RIC team to create EI-JOB
No progress done on E2APv1.1 support as Naman cannot work on it yet.
HCL updates;
1. RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - completed
  1. Subtask RIC-747( Study how nanobot tests can be extended to Xapp) - Had discussion with Thoralf and prioritize the testing scenarios for the next release. – Closed this ticket,
  2. Subtask RIC-748(Study OTF & Xtesting as a prospective test framework candidate to draw from for ORAN Near RT RIC) : Attached the ppt to the ticket. Given presentation to Thoralf and Matti.
    As suggested we need some hands-on experience with OTF to confirm on this. OTF installation on local setup - Ongoing.
  3. Subtask RIC-779(Xapp Testing Enhancement like Subscription deletion need to be handled using nanobot): Newly created ticket for handling subscription deletion using nanobot automation.
2. RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress
  1. Able to generate sampling data after getting some help from Thoralf. Continue to work with other scenarios to compare with previous results. Same status as in last meeting. work on it this week.
3. RIC-731- [Static code and test coverage for E2] - 90% Completed.
  1. Blocked on RIC-760 for test coverage.
  2. Same status as in last meeting
4. RIC-671 [Achieve level "passing" in CII]
  1. Requested Thoralf for submitting application for ORAN project onboarding on LFN security.
  2. Same status as in last meeting
5. RIC-150 - Perform e2e RIC benchmarking

Subtask RIC-741(Verify Subcription flow using nanobot): Closed. Code merged

Subtask RIC-742(Verify Indication flow using nanobot): Closed. Code merged

Subtask RIC-750: (Bouncer to E2sim E2E Testing using nanobot) : Closed. Code merged

Subtask RIC-754: (Kpimon to E2sim E2E testing using nanobot) : Closed. Code merged

.RIC-743 Create multiple e2sim for RIC benchmarking

Same status as in last meeting - some indications are still dropping

RIC-744 Verify the E2E communication for multiple e2sim

Had debug session with Nokia team on E2term pod restart issue. Working further on this.

demos again?
1. From last meeting:
  1. Thoralf to discuss demos for Nokia features.
  2. Possible influxDB demo to show how to use from xApps
  3. Possible demos in devops areas (e.g. RIC-754)
  4. demo for RIC-747/RIC-748 slidesets
RICAPP agenda: RICAPP Meetings.

2021-04-27

Recording: link to zoom recording

Every time: Check that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/5848 (ok, exceptional) "Add ability to save route table updates to disk". Actual code lines changed is "only" 96 in an area that supports debugging. Wrote a note to Scott, but no expectation to add test cases.
2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/5856 (ok, includes unit test)
3. https://gerrit.o-ran-sc.org/r/c/ric-plt/vespamgr/+/5864 (ok, actually only test cases for coverage improvements)
4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/5865 (ok, adds HTTP port in subscription, test case was adapted)
5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/5897 (ok, unit testing coverage improvements)
6. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/5909 (ok,. test case was added)
7. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/5925 (ok, new test cases)
8. not yet merged: https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/5933
9. not yet merged: https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/5826 (conclusion: no unit testing equivalent for YAML files in helm charts).
every second time: Review code coverage stats. (Sunil checks if this next step (overview page) is on HCL or on Thoralf's side as next action) - will discuss with Thoralf next time or by email.
1. no news yet.
Thoralf still to update or CII evaluation
Heewon's xApp python framework issue related to RIC-773 - check agian two weeks from now.
RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - completed
1. Subtask RIC-747( Study how nanobot tests can be extended to Xapp) - Prepared a study PPT and will discuss in next call with Matti and Thoralf.
2. Subtask RIC-748(Study OTF & Xtesting as a prospective test framework candidate to draw from for ORAN Near RT RIC) : Prepared a PPT and will discuss in next call with Matti and Thoralf
RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress // Able to generate sampling data after getting some help from Thoralf. Continue to work with other scenarios to compare with previous results. Same status as in last meeting
RIC-731- [Static code and test coverage for E2] - 90% Completed. Blocked on RIC-760 for test coverage. Same status as in last meeting
RIC-671 [Achieve level "passing" in CII] Requested Thoralf for submitting application for ORAN project onboarding on LFN security. Same status as in last meeting
RIC-150 - Perform e2e RIC benchmarking
1. Subtask: RIC-740, RIC-741 & RIC-742 Addressed the review comments provided by Dave. Jenkin job is also successful. Waiting for Bharath to review the tickets. So that tickets can be closed.
2. Subtask: RIC-754 KPIMON xapp validation using nanobot with SDL Committed the code in gerrit. Review and Job is successful. Will merge the code.
.RIC-743 Create multiple e2sim for RIC benchmarking Same status as in last meeting
RIC-744 Verify the E2E communication for multiple e2sim Same status as in last meeting
A1-EI Subhash is now working on this. E2 work. Subhash to send e-mail to Thoralf with details on change in committers, incl. LF ID of Naman.
demos again?
1. Thoralf to discuss demos for Nokia features.
2. Possible influxDB demo to show how to use from xApps
3. Possible demos in devops areas (e.g. RIC-754)
4. demo for RIC-747/RIC-748 slidesets
RICAPP agenda: RICAPP Meetings.
RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - completed
1. Subtask RIC-747( Study how nanobot tests can be extended to Xapp) : Discussed with Thoralf and based on priority we listed out the scenarios for xapp testing using nanobot.
  First Priority:
  - Xapp Testing Enhancement like Subscription deletion need to be addup.
  - The control interface nanobot could even steer different scenarios, e.g., related to timing. E.g., send a subscription delete for a originally-failed or non-existent subscription; or send duplicate subscriptions, … I.e., testing for correct behavior in failure/timeout scenarios.
  Second Priority:
  - Xapp need to handle E2 Control which already has a scenario (see spec) in which the E2 node sends back a RIC CONTROL ACK. That could be tested as well.
  - Additionally we could have test cases for A1 policy handling (and possibly A1-EI handling if we get +https://jira.o-ran-sc.org/browse/RIC-129+ implemented within Dawn)
  Third Priority:
  - O1 proxying, i.e., the CM flow to xApps and FM/PM flow from xApps would be more test cases.
  - Change in the xApp test implementation in which we do not rely on logs but nanobot communicates with the test xApp via some control interface to check Whether a test has been successful or not.
2. Subtask RIC-748(Study OTF & Xtesting as a prospective test framework candidate to draw from for ORAN Near RT RIC) : Given demo to Thoralf and Matti about this OTF and xtesting comparison.
  As discussed with Thoralf he asked which one we can go with either xtesting or OTF.
  I preferred OTF test framework need to explore more on hands-on experience with OTF and VTH integration.
  Working in progress on deploying OTF in to our environment and also looking for OSC lab access to understand.

2021-04-13

Recording: link to zoom recording

Every time: Check that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. not done this time, but will do next meeting.
every second time: Review code coverage stats. (Sunil checks if this next step (overview page) is on HCL or on Thoralf's side as next action) - will discuss with Thoralf next time or by email.
Samsung: Naman replacement for Rahul - will focus on E2AP 1.1 in E2 Manager
1. A1-EI: Building infrastructure and dev setup - initial implementation this month.
2. py xapp framework (Heewon Park - reported one issue on missing API in E2AP library) - RIC-773 - Matti will followup.
RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - completed
RIC-762- Code is merged by Felix. - Closed
1. Subtask: RIC-746 Run nanobot based test automation from - it/test repository on RIC with k8 1.18/helm3 in OSC Lab Nanobot testing completed on top of helm 3 and k8s v1.18 version. Closed this subtask. Created a new subtask RIC-755, to do nanobot testing in OSC lab with steps provided. As suggested by Thoralf.
RIC-723 - [Study performance overhead of latest open-tracing solutions] – InProgress
1. Able to generate sampling data after getting some help from Thoralf. Continue to work with other scenarios to compare with previous results.Work in progress
RIC-731- [Static code and test coverage for E2T] - 90% Completed. // Blocked on RIC-760 for test coverage.
RIC-671 [Achieve level "passing" in CII] Requested Thoralf for submitting application for ORAN project onboarding on LFN security. Work in progress
RIC-150 - Perform e2e RIC benchmarking
1. Subtask: RIC-740, 741 & 742Code committed. Addressed the review comments provided by Dave. Job build failed issue resolved. The tickets can now be closed
2. Subtask: RIC-754 KPIMON xapp validation using nanobot with SDL // SDL database query validation using robot and Testing part done. Updated the steps in readme file. // Code commit – InProgress.
RIC-743 Create multiple e2sim for RIC benchmarking // E2term pod restart issue – Work in progress - waiting for meeting with Nokia.
RIC-744 Verify the E2E communication for multiple e2sim // Multiple RIC indication messages is working fine with the connected E2 Nodes. Tested with 100+ E2 nodes.
HCL account request still in progress - both account and VM is missing - Matti will keep on reminding Felix.
RICAPP agenda: RICAPP Meetings.

2021-03-30

Recording: link to zoom recording with audio transcript

Every time: Check that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
1. https://gerrit.o-ran-sc.org/r/c/ric-plt/appmgr/+/5816 test cases were added separately via: https://gerrit.o-ran-sc.org/r/c/ric-plt/appmgr/+/5820
every second time: Review code coverage stats. (Sunil checks if this next step (overview page) is on HCL or on my side as next action)
Thoralf on holiday: Apr-02 to Apr-13. Matti to host the next meeting
Time changed to 1pm UTC. I.e., locations without daylight savings time the meeting starts now one hour earlier
CII badging: https://bestpractices.coreinfrastructure.org/en/projects?q=oranand not yet public: https://security.lfx.linuxfoundation.org/#/my-projects (near-RT RIC)
RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - InProgress // VPN access enabled waiting for Felix to create VM in T-lab & share details. – Pending // Subtask: RIC-746 Run nanobot based test automation from - it/test repository on RIC with k8 1.18/helm3 in OSC Lab // Nanobot Testing done on latest helm version and k8s. Found issue in submgr, we got decode failed due to RECIPE.yaml which is not having the latest versions of ricplt components. We internally changed with latest tag of submgr and completed the testing. Once we get the updated RECIPE.yaml we will test this one more time and close the ticket.
RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress // Able to generate sampling data after getting some help from thoralf. Continue to work with other scenarios to compare with previous results. Shared the progress with Thoralf in a dedicated session. Need to study cpp based library of opentracing to modify existing artifacts. Work in progress.
RIC-731- [Static code and test coverage for E2] - 90% Completed. Blocked on RIC-760 for test coverage. Dhiraj waiting for prioritisation of this task by project management. For now this is blocked.
RIC-671 [Achieve level "passing" in CII] // Requested Thoralf for submitting application for ORAN project onboarding on LFN security. Waiting for the reply from LFN to move further. (see item 5 above)
RIC-150 - Perform e2e RIC benchmarking
1. Subtask: RIC-740, 741 & 742 Code committed. Addressed the review comments. Job build failed. working in progress.
2. Subtask: RIC-754 KPIMON xapp validation using nanobot with SDL // Manually checked the database entry from Kpimon and adding up code for checking via SDL. Waiting for the mail response from Matti and Ron on clarifications. The question is related to the simulator. Ron should answer today or tommorrow.
RIC-743 Create multiple e2sim for RIC benchmarking // Mail is send with the detailed information on multi e2sim e2 connection status for Jira ticket. Checked the e2term pod for memory issue at the time of restart. It seems there is no issue in pod memory and CPU configuration. pod restart due to e2term application error only. Currently trying to capture the application log (remember to change config file and restart binary from within the pod) at the time of restart.
RIC-744 Verify the E2E communication for multiple e2sim // Verified the E2E communication with more that 120+ E2 nodes connections with Multiple RIC indication messages. Observed 2-3 RIC subscription delete request everytime. E2Term is randomly restarted. Multiple RIC indication messages is working fine with the connected E2 Nodes. Tested with 100+ E2 nodes.
Influx helm charts - work in progress in ric-dep (no review yet)
update from Samsung
1. design aspects for E2APv1.1 (Rahul to upload) design should be ready.
2. A1 (Subhash to upload)
3. R. to be replaced with someone new.
RICAPP agenda: RICAPP Meetings.

2021-03-16

Recording: link to zoom recording with audio transcript

record-to-cloud. Note we change the recording format and I will post after the meeting in the meeting minutes a publicly available link like this one: link. This allows reading the audio transcript and fast-forward to places in the video that are highly-relevant. The transcript usually take a few hours before available. The video is available immediately.
Regular items:
1. Every time: Check that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/5748 OK
  2. https://gerrit.o-ran-sc.org/r/c/ric-plt/rtmgr/+/5743 OK - Thoralf contacted committers. Bug report RIC-764. The commit included a lot of formatting changes that made it large. Remember to separate such changes from functionality commits.
  3. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/5681 OK
  4. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/5640 OK
  5. https://gerrit.o-ran-sc.org/r/c/ric-plt/libe2ap/+/5617 OK as documentation commit
2. every second time: Review code coverage stats.
Snapshot (2021-03-16) jira_dawn_near_rt_ric.xlsx // Always latest view from JIRA: Content of Dawn: 31 items planned: link and 15 "stretch goals": link
RIC-671 (Alok) Who did originally pointed us to the “LF security” service? Which security issues it actually discovers that we do not already cover with Sonarcube? Does it actually address “container scans” for vulnerabilities? Does it cover scanning for including of vulnerable libraries or modules, like go modules? If we decide to go forward, we need to … (1) decide if we create a “meta project” entry similar to, e.g., CNCF? Like “O-RAN software community (O-RAN SC)” under which we then have separate projects, like, Near-RT RIC, which in turn will include a certain number of repositories?
1. RIC-671 [Achieve level "passing" in CII] Requested Thoralf for submitting application for ORAN project onboarding on LFN security. // Also explored LFN inputs using nexus IQ. The example jobs failed into sandbox. Will continue to work on it.
2. Alok to schedule a meeting on this
Initial discussion on alpine base images. We handle by e-mail. At least QP xApp uses alpine (the same was as A1)
HCL Items:
1. RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - InProgress VPN access enabled waiting for Felix to create VM in T-lab & share details. – Pending In the absence of VM provisioned in Tlab, VM was created in HCL Lab & tested with k1.18 with helm3. The logs were shared with Thoralf & two minor bugs reported ( RIC-761 for dbaas & RIC-762 for helm3). The fix for both bugs have been submitted into Gerrit review by respective owners.
  1. Subtask: RIC-746 Run nanobot based test automation from - it/test repository on RIC with k8 1.18/helm3 in OSC Lab // Nanobot Testing in progress on latest helm version and k8s.
2. RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress // Able to generate sampling data after getting some help from thoralf. Continue to work with other scenarios to compare with previous results.
3. RIC-731- [Static code and test coverage for E2] - 90% Completed. Blocked on RIC-760 for test coverage.
4. RIC-150 - Perform e2e RIC benchmarking
  1. Subtask: RIC-741 Verify Subscription flow using RMR API // Code committed and sent for review
  2. Subtask: RIC-742 Verify Indication flow using RMR API // Code committed and sent for review
  3. Subtask: RIC-754 KPIMON xapp validation using nanobot with SDL // KPIMON deployed and it is running. Validating the packet flow between KPIMON & E2SIM. – InProgress
5. RIC-743 Create multiple e2sim for RIC benchmarking // Able to connect 800 e2sim nodes to the ric platform. Number of connected nodes drops after scaling. Tested with 1500 E2 node iterations. // Collecting the logs and document the observation in a Jira Ticket (still pending)
6. RIC-744 Verify the E2E communication for multiple e2sim // Debugging the issue on subscription response messages with multiple e2simulator – For 10 E2 SIM, RIC subscription Request and response is working fine. // Now scaling it for 800+ RIC Subscription request/response.
  1. Thoralf asked Himesh: Could you provide a description of what you did and what happened in the failure case and where we currently are.
InfluxDB issue (simple single-instance should be enough).
configuration handling in E2AP seems to settle down. Rahul (not in meeting today) will finalize via e-mail.
Subhash (Samsung) asked about t-lab access. About VMs OSC Community Labs Note that HCL is also working on this. Matti looking for someone from ATT to help (Felix busy).
RICAPP agenda: RICAPP Meetings.

2021-03-02

Recording:near_rt_ricplatform_and_ricapp_meeting_2021_03_02.mp4

Thoralf to figure out how to publish zoom recording
for CII compliance improvements we should do this from now on
1. check that all large or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
2. add a regular item in the meeting (once per month) to check code coverage
in context of CII, pls. note this convention in section "security bugs": Tools (mailing list, JIRA, Gerrit)
Release criteria checklist template
If you raise issues to LF support that are sensible to make visible to others, pls. first raise a ticket to join "ORAN" organization in the support tool: "When these organizations (ORAN) were created in the beginning, we added by default all members from the committer groups into the organization. If at that time a particular user was not part of any group or just joined the community, then they will not be automatically added into the oran organization. Going forward, the new user will need to create a support ticket to be added to the organization."
HCL items:
1. RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - InProgress VPN access enabled waiting for Felix to create VM in T-lab & share details. Sent the reminder on Thu (25th Feb). VM in T-lab still needed from Felix.
2. RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress Able to generate sampling data after getting some help from thoralf. Continue to work with other scenarios to compare with previous results. sampling data now available. Numbers seem to be different than from previous PDF. Alok to schedule meeting with Thoralf once enough new information is available.
3. RIC-731- [Static code and test coverage for E2] - 90% Completed. Had a debug session with E2 dev team today (2nd March) & we were able to get the blocker issue resolved. Looking forward to close the issue by this week & ready for submitting Gerrit changes to ci-management repo.
4. RIC-671 [Achieve level "passing" in CII] Received information from LFN on queries on dynamic code analysis & CLM. Going through it.
5. RIC-150 - Perform e2e RIC benchmarking
  1. Subtask: RIC-741 Verify Subscription flow using RMR API Done – Still need to commit the code
  2. Subtask: RIC-742 Verify Indication flow using RMR API Done – Still need to commit the code
  3. Subtask: RIC-754 KPIMON xapp validation using nanobot with SDL : KPIMON Xapp deployment got crashloopbackoff state. Sent mail to the committer (Jinwei.fan@samsung.com) to confirm on this.
6. RIC-743 Create multiple e2sim for RIC benchmarking Able to connect 800 e2sim nodes to the ric platform. Number of connected nodes drops after trying to scale >800 (Tests fail with 1500 E2 node iterations).
7. RIC-744 Verify the E2E communication for multiple e2sim Transaction ID issue has been resolved. Now debugging the issue on subscription response messages with multiple e2simulator.
1.5 slides from Rahul (if no time, by e-mail). Rahul to send mail. include Matti, Thoralf, Abukar, Alok. Ramesh, Sunil (if you don't have the address, I can add them to the mail later) → Slide E2APDesign 2.0.pptx
RICAPP agenda: RICAPP Meetings.

2021-02-16

Recording: near_rt_ricplatform_and_ricapp_meeting_2021_02_16.mp4

discuss how to proceed with RIC-184. OTF,. robot. Maybe schedule another meeting during this week,

update from HCL: User stories created under RIC-184 (InProgress)
1. - Got credentials for OSC lab created for Alok facilitated by Felix.
  - Requested Felix, for rest of the credentials for HCL team members
  - Working with HCL local IT team for VPN client whitelisting

1. RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress
  - We be going through the content shared by Thoralf from previous effort of opentracing based work
  RIC-731- [Static code and test coverage for E2] - 90% Completed.
  - Blocked for Developer’s response.
  RIC-671 [Achieve level "passing" in CII]
  - Internally discussed the requirements for Epic.
  - Need a setup call with Thoralf this week for clarifying & grooming the stories. Alok created a gap analysis. Alok to call for a meeting.
  RIC-150 - Perform e2e RIC benchmarking
                  Subtask: RIC-741   Verify Subscription flow using RMR API Subscription Request and response verification done using kubectl api and calculated latency on RoundTripTime of subscription flow in nanobot automation
                  Subtask: RIC-742 Verify Indication flow using RMR API Currently working on latest code of bouncer xapp and e2sim to validate the indication message flow locally using nanobot. Working on CDF (distribution function) plotting to represent latency vs throughput on the message flow.
  RIC-743 Create multiple e2sim for RIC benchmarking
                  Benchmarking the code with 1500+ E2SIM, But the result is not stable (only 50 or 700 E2 nodes are connected). "moving up from 50 is not yet stable". Currently checking on this.
  1. Try to make this reproducible. Maybe someone from E2T/E2M can take a look at it,
2. RIC-744 Verify the E2E communication for multiple e2sim // adding the sleep timer after every GNB sub request that has reduced the number of message rejection on subMgr side. It like the 1 is rejected out of 5 messages. // Debugging the issue // continue by e-mail with committers.
3. Dhjiraj to talk to Sangeetha on the automation side.
E2AP config transfer (Rahul)
1. Rahul to send a mail on the type of octet strings we might have.
A1-EI design updated: A1-EI_v2.pptx
RICAPP agenda: RICAPP Meetings.

2021-02-02

Recording: near_rt_ricplatform_and_ricapp_meeting_2021_02_02.part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2021_02_02.part2.mp4

We would like to introduce a minor branch from Cherry in which we combine Cherry with the xApp onboarding feature. This way we have a stable branch (as compared to master) against which xApps can be developed that require this change.
1. fixes done to cherry we will also do to "cherry-plus-onboarding" (exact branch date to be checked with Felix, but it should be soon (this or next week)).
2. only branch is in components that actually have a change.
3. all Dawn features continue on master (no similar approach for such features)
Moved the following items from subteam-n back to subteam-n-proposal
1. RIC-71 Subscription manager: Better debugging capabilities
2. RIC-226 fix for SDL (C++) silent hang
3. RIC-330 Merge individual library repos (lib) python into framework repo. Also for C++ and for Golang
4. RIC-366 A1 API as higher abstraction level in xapp framework SDK (golang)higher abstraction level in xapp framework SDK (golang)
5. RIC-373 O1 mediator to check health of all platform components and expose this via O1
6. RIC-421 O1 mediator to handle restart gracefully
please check your contribution plan and mark things as "soft commitment" like subteam-X. and things that you don't commit to as "subteam-X-proposal". Once done, send me a e-mail with that fact. Deadline: Feb-9-2021
1. links under §7.5 in Jira usage conventions
A1-EI
1. only minor update to slideset and that serves as design proposal according to which implementation is done. A1-EI_v2.pptx
configuration update concept.
1. further discussion by mail.
A1 mediator and RMR lib update?
1. updating A1 mediator with latest RMR image. Matti to add thoralf in mail thread on this
RICAPP agenda: RICAPP Meetings.

2021-01-21 4th meeting on Dawn planning

Recording: RIC_and_RICAPP_dawn_planning_2021_01_21.part1.mp4 and RIC_and_RICAPP_dawn_planning_2021_01_21.part2.mp4

discuss CII badging page: CII status: near-RT RIC
1. HCL wanted to some work related to CII: (1) code scanning for vulnerabilities (owasp tool and more tools) (2) continuation of static code analysis (E2T)
  1. contact on LF side is: trishan de lanerolle (tdelanerolle@linuxfou....org)
2. HCL Sangeetha take a look if we can do dsomething for CII "The project MUST have evidence that the test_policy for adding tests has been adhered to in the most recent major changes to the software produced by the project."
RIC-671 mark to E and Dawn
RIC-636 and RIC-635 Ramesh is checking
RIC–114: Thoralf to remove from HCL and create new item for INflux-based time series support. Thoralf created RIC-734 after the mneeting and removed RIC.-114 from HCL and dawn
RIC-682 (Samsung) - look if the only remaining item in it (RIC-382) make sense and if you want to work on this.

2021-01-19

Recording: near_rt_ricplatform_and_ricapp_meeting_2021_01_19.mp4

Implementation of RIC-114 (redis time series plugin) - Ramesh
1. move out from Dawn: RIC-114
2. create new item for InfluxDB Relay integration and unless we see issues we include it always into Near-RT platform, but only for xApp usage. No need to have an abstract SDL interface that hides the actual underlying Time-series DB. Still to be discussed: Only put this in xApp framework if we can fully hide the fact that it is InfluxDB or put dependency on InfluxDB into xapp framework. Pending Also WG3 work.
E2APv1.1 vs E2APv2.0 and do we upgrade to E2APv1.1. Do we define configuration transfer and OID in E2 Setup as mandatory (as in E2APv2.0) even if in E2APv1.1 they are optional?
1. E2SIM work also needed. Need to bring this up in TOC as it might affect other E2 nodes implementations on DU/CU.
2. thoralf to schedule a meeting on this with Rahul/Subhash/Rittwik for next week Wednesday/Thursday
FYI: Dhiraj (committer in E2T) would like to have discussion with Alok on RIC-731. He (Dhiraj) will call a meeting, To get some understanding of how this was done for other repos and what Alok is planing.
Subhash wants to discuss A1-EI. We agreed to
1. A1 mediator should provide the mechanism to receive EIJobResult and further send it to xApp over RMR.
2. xApp should use preconfigured EITypeID to create EIJob.
going through current list of Dawn items and checking commitments - meeting on Thursday, 8am, ET.
RICAPP agenda: RICAPP Meetings.

2021-01-05

Recording: near_rt_ricplatform_and_ricapp_meeting_2021_01_05.mp4

discuss RIC-708 on whether AT&T or Samsung can work on the python and c++ subitem for the xapp framework (mentioned in description of RIC-708). Matti said the python part AT&T could work on. To be checked by Matti.
E2AP 1.1 spec high level discussion (raised by Rahul) - slideset presented, next step is to continue by e-mail disucssion (Matti, Thoralf, E2M/E2T committers, )
A1-EI discussion. Subhash waiting for comments from Matti. Also there was some discussion on the "EI result object" (received by xApp/near-RT RIC). EI result object expected top be provided by EI data producer, while job is managed by non-rt RIC. I.e., there's an interface between non-RT RIC and EI data producer on informing about jobs (and URL targets for the EI result objects).
HCL (Alok) to report on quick analysis on "more advanced" LF CI/CD pipeline that we might want to use in context of OTF (integration track).
1. uses gitlab-based CI. for continuing testing LF uses XTESTING
2. Alok shared the link from opnfv: http://testresults.opnfv.org/functest/xtesting/
3. Alok still discuss with nanobot folks and Felix how current verification is done. (infrastructure testing?)
4. Subhash asked about existing robot test cases and how they would be integrated.
5. Ramesh commented that ONAP is more aligned with LFN and that's one of the reasons we are looking into this.
RICAPP agenda: RICAPP Meetings.

2020-12-22

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_12_22.mp4

we started 15 minutes late
next meeting Jan-5-2021
For 2021: HCL (Alok) to report on quick analysis on "more advanced" LF CI/CD pipeline that we might want to use in context of OTF (integration track).
A1/EI implementation plan A1-EI-HLD.pptx
RICAPP agenda: RICAPP Meetings.

2020-12-08 dawn planning

Recording: RIC_and_RICAPP_dawn_planning_2020_12_08_part1.mp4 , RIC_and_RICAPP_dawn_planning_2020_12_08_part2.mp4 and RIC_and_RICAPP_dawn_planning_2020_12_08_part3.mp4

2020-12-08 main project meeting

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_12_08_part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2020_12_08_part2.mp4

CII badging status (end of Cherry) needs to be filled in: CII status: near-RT RIC
1. nobody volunteered. Thoralf to do this.
committers changed for E2T and E2Mgr. For A1, for ric-dep
Dawn planning: See §7.5 for filters for Dawn planning. We use labels:
1. preliminarily committed: subteam-n, subteam-h / h1, subteam-s / s1 / s2, subteam-a
2. proposal to other team: subteam-n-proposal, subteam-s-proposal, subteam-h-proposal, subteam-a-proposal
demos in December for Dec-17? let me know if there's something to demo.
1. HCL proposed demo of benchmarking
meeting on Dec-22? We will keep the meeting. What about Jan-5? Also ok.
HCL status
1. - HCL: RIC-149: Review comments completed. Merged. DONE
  - HCL: RIC-150: Code committed and Merged. completed part in Cherry (log-base checking), but more work in Dawn (API based checking)
  - HCL: RIC-109: Merged. marked as DONE
  - HCL: RIC-360: Code submitted & Merged CLOSE once gerrit review in RIUC-678 is done (see open review https://gerrit.o-ran-sc.org/r/c/it/dep/+/5237)
  - HCL: RIC-509: Merged. CLOSE in JIRA DONE
  In Progress:
  - Enhancing E2E packet flow between xapp and e2sim by adding APIs to capture and parse the packets
  - RIC indication message decoded in bouncer xapp. Multi E2 connection setup in progress.
Samsung: no updates related to Cherry.
RICAPP agenda: RICAPP Meetings.

For Dawn planning meeting:

Dawn-R7 starts this week and is up to about Mar-5, Dawn-R8 starts Mar-6 and ends ~Apr-26
RIC-705/RIC-706 subteam-s or subteam-a?

2020-11-24

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_11_24_part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2020_11_24_part2.mp4

Cherry status. See Cherry Release (Dec 2020) - 12 items status unclear, 18 items done, some amount of items moved out from Cherry TODO-link
Dawn filter: link
Dawn - another planing meeting next week or two weeks from now? One meeting two weeks from now. Thoralf to schedule.
Samsung status
1. A1-EI could be a work for Dawn. Thoralf-to-map-to S1
2. E2AP work proceeds
3. LCM - Thoralf to schedule a meeting with Nune and Samsung
4. Security: Samsung could work on (1) Document known vulnerability in release notes. (2) (low-prio) Dynamic code analysis. Note that HCL is also looking at vulnerability scanning. From WG there was no work (yet).
HCL
1. HCL: RIC-149: Review comments completed. Merge is pending.
2. HCL: RIC-150: Code committed into "it/test", but not yet merged.
3. HCL: RIC-109: Merged, i.e. DONE.
4. HCL: RIC-360: Code submitted & Merged. One change still not yet merged.
5. HCL: RIC-509: Merged, Go through subitem in JIRA and check if still sensible. If not, let me know if I shoudl delete, or transfer into a new Dawn Epic
CLI footprint
1. no data yet.
RICAPP agenda: RICAPP Meetings.

2020-11-10

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_11_10.mp4

After this meeting we had Dawn planning meeting. Updated slideset (v6 - same link as before): https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/14123013/cherry_and_dawn_near_rt_ric.pptx?api=v2
1. recording of the meeting: RIC_and_RICAPP_dawn_planning_2020_11_10_part1.mp4 and RIC_and_RICAPP_dawn_planning_2020_11_10_part2.mp4
We plan to introduce a more O2-like xApp deployment interfaces. This introduces incompatibility for xApps. xApps will pass their descriptor information when registering with the app manager.
1. check O-RAN WG on current shared view.
2. registration could be hidden in xApp framework
3. RSAC LCM also has something about this.
Status updates
1. HCL
  1. - HCL: RIC-149: Commit done. Working on Review comments.
    - HCL: RIC-150: Targeting to submit for gerrit review by wed.
    - HCL: RIC-109: In Review → reminder sent
    - HCL: RIC-360: Targeting to submit for gerrit review by wed. pls. send e-mail to Felix and committers of ric-dep.
    - HCL: RIC-509: 3 Jobs remaining (Out of 18).
2. Samsung
  1. RIC-95 merge still pending. Subhash sent a reminder. Thoralf tested RIC-95 with three E2 nodes.
5min Subhash (Samsung) to present CLI plan. More discussion needed. check progress in two weeks from now.
RICAPP agenda: RICAPP Meetings.

2020-10-27

Recording: RIC_and_RICAPP_dawn_planning_2020_10_27_part2.mp4

project status updates
1. known issues with Alpine base image. Scott and Timo are resolving.
2. including ASN.1 to be included in python or C++ repo. Various options, but let's wait for TOC's legal aspects.
3. formally this week should be code freeze for Cherry. Let me know if we need to manage any exceptions.
4. HCL: RIC-109 commit coming, review ongoing
5. HCL: RIC-509 commit coming, review ongoing
6. HCL: RIC-149 commit coming, review ongoing
7. HCL: RIC-360, RIC-150 likely to be finnished over the next few weeks
Samsung
1. Subhash working on RIC-95 and all items done. Concluded now after last reviews.
2. RIC-203 subteam-s1 not planning to work on it. Moving it out from Cherry.
Dawn planning slide: https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/14123013/cherry_and_dawn_near_rt_ric.pptx?api=v2 updated in 1h planning meeting we had before this meeting. Recording: RIC_and_RICAPP_dawn_planning_2020_10_27_part1.mp4 and RIC_and_RICAPP_dawn_planning_2020_10_27_part2.mp4. Next planning meeting in two weeks from now. Initial interests on who would like to work on what should come by then.
RICAPP agenda: RICAPP Meetings.

2020-10-13

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_10_13.mp4

note the presentations on RIC and xApps from ONeS (link) and in O-RAN.
demo on Thursday Sprint demos → 2020-10-15 Cherry R6.2 (please add agenda items)
asn1-py as separate repo or as part of xapp-frame-py? Discussion to be continued over e-mail.
status update (HCL).
1. Thoralf to organize a meeting with Abdulwahid, Anssi, Adi, Felix. Ask Abdulwahid to have some working setup ready for comparison. HCL (Neeraj) to setup the environment (whcih is not working)
  1. meeting recording: RIC_troubleshooting_part1.mp4 RIC_troubleshooting_part2.mp4 RIC_troubleshooting_part3.mp4 RIC_troubleshooting_part4.mp4
2. Subhash raised the issue of where the test cases are stored) e2's folder "automation". To be discussed in Bharath's meeting. Also Thoralf would like it to be clear if platform test cases go into ric-plt/ric-test or into it/test.
3. RIC-109 DB: study: SDL scaling with Redis cluster (instead of sentinel) "Ready to submit gerrit review request with helm chart & docs for redis-cluster. "
4. RIC-360 Plan and prototype helm (and k8s) upgrade with xApp manager, REC, RIC infrastructure "Work in progress. Changing appmgr/xapp-onboarder
5. RIC-509 Components supporting continuous integration infrastructure, e.g., static code analysis "Gerrit Changes for below JIRA tickets (Under RIC-509 Epic) have been merged: RIC-648, RIC-649, RIC-650 (Verified & Reviewed but not merged yet)
6. RIC-150 Perform e2e RIC benchmarking "Working on end to end E2SM message exchange among HW xAPP, SubMgr, RTMgr, E2Term & E2SIM. Facing issues w.r.t message exchange with SubMgr, RTMgr. Debugging is in progress. Shared the logs to community and getting support from these components experts to resolve the issue."
7. RIC-149 Define and implement automated test cases for flows to be defined early in Bronze-R4 1) Ricdeployment : Done. Need repo(it/test) access to commit our changes for review. 2) HealthCheck Testsuite : i)dbaas: Kubectl ping pong done and coding completed. ii) dbaas: As confirmed, using SDL is the best approach to check for dbaas healthcheck and manual testing completed. Integrating with robot framework is in progress. iii)Submgr healthcheck - As confirmed Anssi we tried adding liveness/readiness probe to submgr and check for http requests. Its in progress. 3) ETE Testssuite: i)Robotxapp deployment checked manually and its working fine. But rmr code which i used for robotxapp deployment is the older one with NNG package. Hence want to check with Bharath and Dave. ii) Automation : out of 11 testcases , 8 testcases passed for this xappdeployments and 3 testcases failed using post request for RAN via E2mgr X2 interface and seems the commands are deprecated. Alternate commands to check for and try proceeding. URL: https://lf-o-ran-sc.atlassian.net/wiki/display/RICP/E2+Manager+R4+Interface+Design#E2ManagerR4InterfaceDesign-X2SetupRequest(Deprecated)
RIC-95 updates (Subhash). RIC-260, RIC-643. Rahul commented that RIC-95 is basically done. Two merges still pending, but code review already done. Thoralf is still to do testing.
How do we plan work for Dawn. Thoralf proposes 1h planning meeting where we collect input from all possible contributors.
1. We also look at the current draft/wish list cherry_and_dawn_near_rt_ric.pptx
2. Thoralf to organize a separate meeting next week on this
RICAPP agenda: RICAPP Meetings.

2020-09-29

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_09_29_part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2020_09_29_part2.mp4

reminder on next demo: 2020-10-15 Cherry R6.2 . Pls. add anything you want to demo there.
RIC-360 any progress. Discussion with Nune and Nithin kept?
1. deployment script changes (Abdulwahid) related to helm3. Discussed with Felix (onboarder (felix) changes still needed).
2. appmgr changes no discussion → Nune
3. Thoralf to invite meeting with Alok + Sri + ramesh (still this weeks)
4. Status: working on go code changes in appmgr
RIC-509
1. subitems being worked on by LF next.
2. Status: Created Jira tickets for each component under the EPIC: (e.g. RIC-648, RIC-649, RIC-650) & submitted Gerrit change requests to these three tickets.
RIC-109: since Jussi on holiday pls. involve Timo T (another committer for dbaas). Status:Converted the k8 manifest files into helm chart. Creating documentation other artifacts as discussed on the call with ORAN SPOCs.
RIC-249 (of RIC-95) currently blocked by XML-to-PER conversion of RIC_SERVICE_UPDATE_ACK.
1. Thoralf still to test the 1-week old code that Rahul wrote (RIC-248)
2. This now hangs with Adi.
3. Also another issue is how an empty RIC Service Query/update would look like. ASN.1 is also a bit unclear.
RIC-203 is still in team S1 or currently nobody planning to work on this?
1. Rahul might be able to work on this, but earliest decision on this in next meeting.
RIC-150 (RIC benchmark) Status: Able to exchange RIC Subscription Request & Response between HW xAPP and E2 Simulator (Action type - Report). Now working on handling RIC Indication message exchnage between HW xAPP & E2 Simulator
RIC-149 (more tests) Status: 1) RIC deployment Testsuite: RIC deployment testing is done. Need to send the code for review. 2) Healthcheck Testsuite: O1mediator issue is fixed. Created interface.robot and verified the log for this component. dbaas - ping pong test is in progress. submgr - Unable to proceed due to ClusterIP issue. We sent query to Dave on this. 3) ETE Testsuite : robotxapp deployment is in progress.
some items postponed from Cherry to Dawn: RIC-585 (the alarm for E2 connection loss) , RIC-139 (O1 adapter to summarize platform health state) , RIC-421 (O1 mediator graceful restart)
Subhash xApp demo can be in platform code. Subhash would like to discuss this.
RICAPP agenda: RICAPP Meetings.

2020-09-15

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_09_15.mp4

Schedule for R6 (second half of Cherry: Jira usage conventions → §6).
demos for demo day (next week Thursday = Sep-24 in 2020-09-24 Cherry R6.1 - CANCELLED)
Subhash: move on with exact contribution.
1. [1] Higher abstraction level in xAPP framework SDK (golang) [https://jira.o-ran-sc.org/browse/RIC-366]
  1. We discussed possible abstraction of this on API level. Matti said one person on AT&T side has been working on this before. We need to set up a separate meeting on this: Subhash, Nune, Matti, Neeraj Gupta (HCL), Vaishali (HCL), h_w.park@samsung.com, Akash (bouncer xapp) Identify new capabilities that we can implement on xapp framework side. Focus on things not yet implemented in any xapp frameworks. presentation by h_w.park@samsung.com on what is planned. Aim for 10am EDT (NewYork) on Monday, Sep-21
  2. RIC-80 is already in progress by Antti teams.
  3. general goal xApps should only rely on E2SM, but do not need to touch E2AP messages (using ASN.1). So, a good abstraction would allow xApp implementation without ever touching an ASN.1 compiler if an E2SM would be defined in something else than ASN.1. We can discuss this further in the Monday meeting.
2. [2] Support for E2AP RESET procedure [https://jira.o-ran-sc.org/browse/RIC-383]
3. [3] Developing version of xAPP [https://jira.o-ran-sc.org/browse/RIC-120]
  1. existing "hello world" is C++, but does more than just saying "Hello world", e.g. has own service model. Additional demo xapps in go/python are welcome. For go see in xapp-framework for Go for some skeleton code.
  2. for example, it would be good to have E2SM support for "hello world" E2SM in the simulator.
Alok RIC-509 works better with Ceph (instead of NFS). Meeting to discuss how to integrate this to be called by Alok.
Akash asked about the hello world xApp in terms of a new bouncer xApp (for benchmarking). Pls. contact Matti to get you in contact with hello world expert. Akash to attend also the Monday meeting.
(post-meeting addition): Ron now merged the patch into the E2 simulator: https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/4700 Work on the simulator can now continue.
(post-meeting addition): RIC-360: continued work on appmgr // RIC-509: testing JJB templates in sandbox (sandbox permissions obtained) // RIC-150 Able to send RIC Subsription Request message from Bouncer xAPP to E2 terminator. Working on handling of the RIC Subsription request message at E2 terminator to E2SIM. Debuging is in progress. Able to exchange E2 Setup request and response. RIC-149: Ricdeployment Testsuite - existing issue got fixed except statefulset, working on this. Sent code modification to Dave and Bharath for review. Healthcheck Testsuite - Interface.robot files missing for few components got fixed and added keyword healthcheck for missing components as well. Working on dbaas, submgr related inerface.robot parameters to add and test. E2E Testsuite: Working robotxapp deployment using http post request using both manual and robot automation.
RICAPP agenda: RICAPP Meetings.

2020-09-01

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_09_01.mp4

S1+S2 team any news?
1. Rahul progressing on RIC-95. Thoralf will help with testing as E2 simulator is needed.
2. Subhash interested in picking up items on near-RT RIC platform. Thoralf to send information package.
3. Double-check progress on E2 simulator in simulator project. Action item-Matti: check with Ron. Make sure to to add copyright and license statement.
4. RIC-372 (sdlpy now supports notifications) now done.
H1 team any news?
1. RIC-109 (helm/k8s upgrade) Working on Non NFS based cluster storage on k8s
2. RIC-509: HCL to present output/status of RIC-509.
  1. analysed com-pylog project on sonarcloud using our a/c
  2. Matti noted that xApp's MC xapp has done the same. Always needs to involve LF support case. HCL to include Matti in discussion.
3. RIC-360: Go lang based code changes in progress
4. RIC-150: (e2e benchmarking) Working on the Bouncer xAPP Implementation. "successfully built the e2apv1sim code manually in the LAB and run the e2sim binary. The e2sim sending the E2 setup request message to RIC terminator. The RIC terminator received the E2 setup message and it is not sending the response to e2sim. Because, in decode part of E2 setup request message in RIC, some parameters(RANfunction_Item) are not handled in RIC side and it's giving the decode error."
5. RIC-149 (testing): Started fixing up the health check of ric component testsuites with few missing keywords and missing riccomponent_interface.robot files. As we confirmed with Bharath and Dave we are proceeding to fix the healthcheck and e2e testsuites related issues. Status: In progress Issue: Currently working on this while adding a1mediator interface.robot file " <tpl ($content).AsConfig $>: error calling tpl: Error during tpl function execution for "a1mediator.robot". Due to this some component related files are not mounted to nanobot pod.
alarms implemented in Cherry → check status with owners of sub user stories in RIC-56 - Getting issue details... STATUS (check with owners of 585 203 and 204). Contact Nune
to discuss this reply to Jinri's request: https://lists.o-ran-sc.org/g/main/message/812
1. reply: " from near-RT RIC side we work with: (1) Akraino REC as the Akraino blueprint that we integrate RIC with (2) Nokia investigating if we can provide a wireshark dissector for E2AP (pending discussion with O-RAN alliance) (3) We're using the VESPA (Prometheus to VES adapter) project.
Anything to demo on Thursday? Matti (50/50)?
RICAPP agenda: RICAPP Meetings.

2020-08-18 special meeting on E2 simulator

Recording: 2018_08_18_special_meeting_on_e2_simulator.mp4 (no meeting notes created)

2020-08-18

Recording: 2 parts: near_rt_ricplatform_and_ricapp_meeting_2020_08_18_part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2020_08_18_part2.mp4

Note that previous demo was on Thursday, 2020-08-13 Cherry R5.4. Recording available on the confluence page.
RIC-628 now also fixed. Together with the earlier fix of RIC-444 this should now remove any issues with unintended dependencies on E2SMs. Now the RIC platform should again be independent of E2SMs. Note that the new routing manager implementation >0.6.1 requires an update of the routing manager helm chart as well. These helm charts are in master branch of repo ric-plt/ric-dep.

RIC-509 we are aiming for CII (core infrastructure initiative of the Linux foundation) self-certified badge "basic". Need to check what basic "passing" badge actually implies. Initially this might be a reasonable aim: (1) Weekly static code scans by SonarCloud, (2) Weekly scans by NexusIQ for outdated 3rd-party packages/libraries (3) All critical and major vulnerabilities are remediated, (4) automatic code coverage is 80%-90%. Note that originally we planned for Cherry: "80% for all existing components and 50% code coverage for new ones."

The below projects are onboarded to SonarCloud but not scanned.
ric-plt-e2 ric-plt-sdlgo ric-plt-xapp-frame ric-plt-appmgr ric-plt-dbaas ric-plt-dbaas-hiredis-vip ric-plt- nodeb-rnib ric-plt-submgr ric-plt-utils ric-plt-jaegeradapter ric-plt-tracelibcpp ric-plt-tracelibgo ric-plt- vespamgr ric-plt-asn1-documents ric-plt-streaming-protobufs ric-plt-ric-test ric-plt-ric-dep ric-plt-demo1
not in sonar: com-golog com-pylog com-gs-lite
None of the components except ric-plt-a1 (scanned 3 months ago) is onboarded to NexusIQ.

Project name in SonarCoud	Vulnerabilities	Coverage	Last scan
ric-plt-alarm-go	0	38.8	8/5/2020
ric-plt-lib-rmr	0	73.6	8/3/2020
~~ric-plt-lib-rmr-c (old code, old job not in use anymore)~~	10	42	~~3/29/2020~~
ric-plt-lib-rmr-py	0	0	4/5/2020
ric-plt-rtmgr	0	77.5	8/5/2020
ric-plt-sdl	1 - minor	66.6	7/30/2020
ric-plt-xapp-frame-cpp	0	94.3	3/25/2020
com-log	3	89.9	8/5/2020

Note that Matti and scot are trying to remove the old job info sonarcloud. ~~ric-plt-lib-rmr-c~~

T1 (Antti)
1. RIC-114 scope change
T2 (Abdulwahid)
1. Routing Manager now supports route distribution to multiple RMR control ports.
T4 (Avinoam)
1. E2M - Get node list API changed and now return also the node connection status - completed. Swagger : https://lf-o-ran-sc.atlassian.net/wiki/display/RICP/E2+Manager+REST+API+Swagger
2. Publish SDL event in case Connection Status is changed - Testing is completed - waiting for further testing with some sample xApp from Nokia
3. Publish SDL event in case gNB is added/updated/deleted - in progress
4. E2T Prometheus implementation - completed (including review and testing)
T5 (Matti)
1. O1 APIs (O1-PM/FM/CM) in C++ framework completed - see demo from last week // python framework demo was done earlier in Cherry.
2. E2 Simulator work still ongoing (Ron doing cleanup work). Ron will give presentation about simulator code in meeting with Samsung/HCL/ATT/Nokia after this meeting.
3. RMR-to-VES event adapter for statistics implemented
T6 (Lusheng)
T7 (Bharath)

Subteam-h1 (Alok, Sangeetha)

Ticket Number	Ticket Summary	8/18 Updates
RIC-109	DB: study: SDL scaling with Redis cluster (instead of sentinel)	Found an approach for the ask
		First level of demo scheduled for Fri,21st with ticket SPOCs from ORAN
		Preparing for demo ppt
RIC-360	Plan and prototype helm (and k8s) upgrade with xApp manager, REC, RIC infrastructure	Understood the as-is deployment scripts.
		Explored the Helm2/Helm3 Delta for these deployment scripts
		Changes done in deployment scripts & shared understanding via email to SPOCs/experts (Lusheng)
		Received feedback for additional Code level changes (Go lang based) in few components (in deployment script)

RIC-509	Components supporting continuous integration infrastructure, e.g., static code analysis	Local environment set-up is completed (Thoralf: goal eventually to use LF infra)
		Code-analysis is done on an ORAN project that already supports it and found results to be comparable.
		Working on a candidate ORAN project to run code-analysis.
RIC-150	Perform e2e RIC benchmarking	Understanding flow and scope of this RIC benchmarking across E2 Sim, Bouncer xApp, KPI Mon xApp
		Subtask (RIC-633) E2sim and Xapp created and added to this.
		E2simulator is installed in our lab and checking for RIC Communication.
		Working on KPIMON xApp standup along with its dependencies (E2 Mgr, E2 Subscription Mgr and E2 Term) - waiting for inputs
RIC-149	Define and implement automated test cases for flows to be defined early in Bronze-R4	Understood nanobot flow and deployed the same in our lab for testing health of the RIC Platform. Currently working on E2E tests to check for health of Xapp manager, deployments and E2mgr.

Himesh asked about KPImon (go) related to: View/Reply Online (#828). Matti to discuss with Samsung committers of KPIMON. Contact Ron S.
RICAPP agenda: RICAPP Meetings.

2020-08-04

Recording: video+audio from the first 44 min (near_rt_ricplatform_and_ricapp_meeting_2020_08_05.mp4) and the last 14 minutes only as audio (near_rt_ricplatform_and_ricapp_meeting_2020_08_05.m4a)

Note updates in E2APv01.01 compared to E2APv01.00, e.g., related to config transfer and TNL (failover, scalability).
progress by subteams
1. RIC-95 - currently blocked by IPR checks on Samsung side.
2. Rahul mentioned integration test setup issues. One option is to ask fro help from Tel Aviv. E2 Sim is the other option. Samsung exploring options to make testing easier.
3. Arun (from Samsung) not working for RIC anymore. Subhash replacing him.
4. Simulator key contacts: Bharath, Ron shacham, Thoralf . Thoralf send a e-mail to Subhash as he was interested in this.
5. RIC-109 call with Jussi done. Problem understood and how to do it. Next step how to distribute in K8S for efficient failover.
6. RIC-360 helm and K8S (1.16 → 1.18) upgrade. Issues with one of the docker images for app manager. Trying to update the code for helm3. Alok did install on K8S 1.18. Did not find any issues.
7. Thoralf to schedule a meeting with Ron, Rahul (Samsung), Subhash (Samsung), Ramesh (HSL), Sangeetha (HCL), Alex with Ron introducing his vision on how to implement additional messages in teh E2 simulator. Also Bharath.
Thoralf to think how to report Nokia and AT&T progress
RIC app meeting

2020-07-21

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_07_21.mp4

Matti hosts this meeting as Thoralf is on holiday
Thoralf added subteams S1, S2, H1 to Jira usage conventions. Check also §1e from the same wiki page on how they are used in JIRA.
1. Alok: Helm 2→3, identified key areas, helm commands not supported, validation errors, tiller not supported in Helm 3, Zhe Huang (Felix)
2. Matti will introduce Alok (alok_bh@hcl.com) to Felix
3. Alok: RIC-360 - who can provide detailed user stories - Matti will check with Felix first, then Thoralf when he is back
Next demo will be on Thursday, 2020-07-23 Cherry R5.3. Anything to demo?
RIC app meeting

2020-07-07

Recording: near_rt_ric_platform_project_meeting_2020_07_07.mp4

Recording of Jul-2 demo: TODO (pending Matti)
Thoralf on holiday Jul-21. The Jul-7 meeting we still have normally. Matti (hiltunen@a...) to host the Jul-21 meeting.
After discussion with xApp PTL (Matti), we will use the old existing empty repo "utils" as a general repo for small utility-like code. The first usage will be for RMR-to-VES mediator (event converter) "platform xapp". This work is done under RIC-420.
discuss contributions by HCL .
1. Assign to Alok Bhatt:
  1. ricp-integration RIC-360: plan and prototype helm upgrade with xApp manager, REC, RIC infrastructure
  Which K8S version with Helm 3 support to move to? Is 1.18 confirmed? Yes
  App owners with whom we need to work with for this co-existence of Helm 2 and 3 change and for doing post deployment check / sanity testing? xapp manager, it-dep, ric-dep, Schedule meeting with Lusheng and Felix, Abdulwahid.
  1. ricp-e2e RIC-509: Components supporting continuous integration infrastructure, e.g., static code analysis. Schedule meeting with Lusheng
  Pl share more info on LF CI/CD. Sonarcloud or SonarQube? Jenkins Job Builder / Chained CI?Schedule meeting with Lusheng
  1. DBaaS RIC-109: DB: study: SDL scaling with Redis cluster (instead of sentinel) Schedule meeting with Jussi.
  App owners with whom we need to work with for doing this before and after comparison for this move from Sentinel to Redis Cluster mode? Should be transparent to user
  Output format expected from this study, if any
  Assign to Sangeetha KR:
  1. ricp-e2e RIC-149: Define and implement automated test cases for flows to be defined early in Bronze-R4
  2. ricp-e2e RIC-150: Perform e2e RIC benchmarking
  Pl connect us with Bharath Balasubramanian on these items.
2. Pl enable community lab access for us to work on these. → connect with Lusheng for how to use TLab.
3. We manage this existing team mapping, but the items are assigned to Alok and Sangeetha.
discuss contributions by Samsung
1. For now, we would like to get your opinion regarding adding pub-sub feature to sdlpy/xapp-frame-py. As far as I know, this feature is already exists in sdlgo, but there seems to be no ticket related to this feature.
2. This would be item RIC-372. Note that this is not related to xapp-frame-py, but to sdlpy only. Thoralf to reply to Timothy John Ebido.
3. item in JIRA to be assigned to him. Note that right now we have notifications only in go, but not in python or C++.
ricapp meeting

2020-06-23

Recording: near_rt_ric_platform_project_meeting_2020_06_23.mp4

Demo day is Jul-2, 9am ET: 2020-07-02 Cherry R5.2
Thoralf on holiday Jul-21. The Jul-7 meeting we still have normally.
Bengi asked for RMR performance data comparing old NNG against SI95 implementation. Nothing on wiki page, but we have the PDF in RIC-48 - Getting issue details... STATUS that might help. Matti to ask Scott to eventually post the results also in the wiki page. Also to double-check that SI95 results are not already in wiki page somewhere.
Chokha interested in contributing to near-RT RIC.
Rittwik asked about what we should push to the maintenance release. So far nothing. Matti asked about adding alarm routes to routing manager. We created RIC-525 - Getting issue details... STATUS for this.

2020-06-09

Recording: near_rt_ric_platform_project_meeting_2020_06_09.mp4

new contributors (Rahul) planning to work on RIC-203 implementation with Abdulwahid and on RIC-133 xApp scalability with Matti.
presentation to O-RAN alliance: 2020-06-08: Report to O-RAN alliance on plans for release "Cherry" under Project reports
demo moved by one week. We now demo in the first week of a sprint. For Sprint 1 in near-RT RIC we don't have a demo. First one for sprint 2 will be Jul-2.
committer change: Tommy → Chris L. (in a1, rmr, xapp-frame-py). Remove rajesh from RMR. Katri and Roni to be removed from all repos. Need a replacement.
RICAPP agenda: RICAPP Meetings.

2020-05-26

This event is cancelled due to overlapping workshop. Next meeting will be in two weeks in regular time slot.

2020-05-12

Recording: near_rt_ric_platform_project_meeting_2020_05_12.mp4

Review and agree to minutes of previous meetings
check RIC-95 status. Quite a lot of work. Code review and unit test cases still to be done.We quickly discussed a possibility of doing healthcheck also via a healthcheck E2SM that woudl have to be defined by O-RAN WG3. We discussed this because in the RICAPPSs Hello World xApp an non-standard E2SM does something similar. Current expectation is that WG3 work will not be picking up this E2SM any time soon.
Check for Bronze what we achieved and Cherry-R5 plans: link (check under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12")
Rittwik wants to talk about Cherry release planning.
1. TS use case will probably be expanded on // possibly some ML model management aspects for RIC platform
2. Rittwik mentioned more work in O1/O2, but for Cherry-R5 we might have issues with standardization not ready yet. More likely Cherry-R6 content.
3. For scalability on E2AP no plans in R5 because of standardization being blocked. We do have work for xapp scalabilty study in Cherry-R5 and benchmarking planned for Cherry-R5.
We might or might not have to cancel the next meeting due to overlapping workshop. I will update the groups.io calendar if it's cancelled.
postponed items (out of Bronze): RIC-76 (subscription manager) and many more - see Cherry-R5 plans (same link as in (3) above).

2020-04-28

Recording: near_rt_ric_platform_project_meeting_2020_04_28.mp4

Review and agree to minutes of previous meetings
FYI RICP (combined with RICAPP) demos are every third week: Sprint demos
Status of
1. RIC-95 (design approved by tel aviv teams // implementation should be ready // problem with testing as no access to simulator) Tel Aviv cannot test with proprietary simulator as no time. This might delay RIC-95 further. Harry cannot help as on leave. Ron might get simulator ready within two weeks, but there is some risk that service query is not working yet in simulator. Arunkumar could take a look at the service query support in simulator during next week once RIC-95 is ready. If we make good progress, we could still push this into maintenance release (after TOC approval).
2. RIC-203 no progress. design not clear yet. Drop this from Bronze (not try to push it into maintenance release)
postponed DB items EPICS: (not even started): RIC-123, RIC-107, RIC-118 and RIC-119 as well as user story: RIC-104 to post-Bronze-R4
2020-04-28: epics still open team 1: 17, team 2: 5, team 3: 3, team 4: 8 : team 5: 10, team 6: 2, team 7: 2. sum = 47 still open
FYI: Tommy Carpenter has left the project. Committer upgrade needed. A1, xapp-frame-py → Chris Lott. RMR python version is in xapp-frame-py. RMR also replace tommy with Chris (even if no RMR python work a<nymore), Rpanta also remove from RMR repo. The repo "utils" we should remove. Add Chris now. Remove Tommy after Bronze. Thoralf to initiate this change.

2020-04-14

Recording: near_rt_ric_platform_project_meeting_2020_04_14.mp4

Review and agree to minutes of previous meetings
Between "DBAAS" single-instance and "HA" we switch by using same configmap with different content as in this review: https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/3105 For platform components this is a good solution. The idea is that xApps (if they use SDL) have something similar. We might have to expand how this works for xApps later on, e.g., so that xApps have a way to declare what they need in terms of data storage.
RICAPP agenda: RICAPP Meetings.

2020-03-31

Recording: near_rt_ric_platform_project_meeting_2020_03_31.mp4

Review and agree to minutes of previous meetings
status update in Bronze Release (Jun 2020)
RICAPP agenda: RICAPP Meetings.

2020-03-17

Recording: near_rt_ric_platform_project_meeting_2020_03_17.mp4

Review and agree to minutes of previous meetings
Changing committers: New instructions are here: How to request committer changes.
Matti and I will give a 40 minute talk about RIC at ONeS, North America. However the conference has been postponed from April to Aug/Sep/Oct.
Two requests filed to O-RAN and O-RAN SC for (1) right to publish E2AP ASN.1 in O-RAN-SC's gerrit (ric-plt/asn1-documents) and (2) machine readable version of ASN.1 to be made available for automatic download (e.g. as part of compilation) from O-RAN web page. Matti noted that E2SM have a similar problem on RICAPP side.
RICAPP agenda: RICAPP Meetings.

2020-03-03

Recording: near_rt_ric_platform_project_meeting_2020_03_03.mp4

Review and agree to minutes of previous meetings
new repo request now all new repos created. See last four entries in Scope of the near-RT RIC platform and its components (summary)
Progress report on RIC-203 and RIC-95 (golang) - by Arun
1. first meeting with Abdulwahid related to RIC-203. Dependencies on other capabilities mean work can only start after a couple of weeks
2. meeting with Avinoam's team to be set up by Arun if e-mail discussion does not proceed. T4 has a design proposal. Arun to comment/proceed.
Bengi asked about how we introduce support for WG3 E2AP in E2T and E2M.
1. The code is being adapted to the new E2AP spec from WG3 (with E2 Setup being sent from E2 node to RIC) right now. This is done under https://jira.o-ran-sc.org/browse/RIC-60 . You can even check this in terms of more fine-grained user stories from the scrum board (which the T4 team is using quite well): https://jira.o-ran-sc.org/secure/RapidBoard.jspa?rapidView=19&view=planning.nodetail&epics=visible&issueLimit=100&selectedEpic=RIC-60 The sprints (and mapping to days) used in this board are explained in §6 here: https://lf-o-ran-sc.atlassian.net/wiki/display/RICP/Jira+usage+conventions
RICAPP agenda: RICAPP Meetings.

2020-02-18

Recording: near_rt_ric_platform_project_meeting_2020_02_18.mp4

Review and agree to minutes of previous meetings
new repo requests: ric-plt/xapp-frame-py, ric-plt/xapp-frame-cpp, ric-plt/alarm-go, ric-plt/alarm-cpp. Thoralf to send this for approval to TOC.
Progress on RIC-203 and RIC-95 (golang).
1. Arun quickly introduced himself. For now only person from Samsung who wants to contribute. Working in a team that has already some usage experience with RIC and RIC xAPPs. C++/python experience.
2. Team T4 (Avinoam) work principles: Design review, Unit tests coverage 80%, Automation coverage, Code review, Sonar – zero issues
3. RIC-95 will involve concrete proposal on design - to check with Arunkumar if he can make a design proposal as well.
4. This is a first for existing near-RT RIC project as well. So, we will have to learn form this and adjust our way of working as well.
5. next step: Thoralf to organize a meeting with T4 on Monday/Tuesday and T3 as well. Next steps are planned there.
Schedule alignment between O-RAN and O-RAN-SC (O-RAN member link only: link (or check recording of this meeting))
RICAPP agenda: RICAPP Meetings.

2020-02-04

Recording: near_rt_ric_platform_project_meeting_2020_02_04.mp4

Review and agree to minutes of previous meetings
Discuss some of the Bronze-R4 flows: RICflows-Bronze-R4.pdf
Go through current backlog.
RICAPP agenda: RICAPP Meetings.

2020-01-21

Recording: near_rt_ric_platform_project_meeting_2020_01_21.mp4

Review and agree to minutes of previous meetings
We have this meeting intentionally one week after the previous one. To align on even weeks. We will keep the next meeting (in 2 weeks) even if many participants are in a workshop.
RSAC health check use case discussion: Now the information is in a wiki: https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/
1. health check of E2 via O1
2. status of E2 connections via E2M
3. alarm management
4. platform statistics and a few statistics providers (E2T coudl provide latency measurements of number of E2 packets per connection)
5. A1 health check
6. RMR-based health check for xApps
Go through current backlog.
1. we created RIC-126 as a item that might come post-Bronze.
RICAPP agenda: RICAPP Meetings.

2020-01-14

Recording: near_rt_ric_platform_project_meeting_2020_01_14.mp4

Review and agree to minutes of previous meetings
Propose to have every even week and next meeting would be on 2020-01-21. This is to align with O-RAN alliance meetings. This was ok-ed.
JIRA conventions for release B planning: Jira usage conventions . We take a quick look at the current Epics in JIRA.
RSAC use case on health check seems difficult to digest. Further discussion needed. Direction is to use alarm management, and statistics for alarm monitoring. Actual health checks based test messages also needed, but details still open.
1. John to move the updated health check document into a RSAC wiki page by Thursday. Further updates can be done there.
RICAPP agenda: RICAPP Meetings.

2019-12-17

Recording: near_rt_ric_platform_project_meeting_2019_12_17.mp4

Review and agree to minutes of previous meetings → OK
Next meeting will be in 2020 on January, 14.
tentative: JIRA conventions for release B planning: Jira usage conventions
RSAC use case on health check seems difficult to digest. Further discussion needed.
RICAPP agenda: RICAPP Meetings.

2019-12-03

Recording: near_rt_ric_platform_project_meeting_2019_12_03.mp4 (last 25 minutes lost due to Zoom software not working correctly)

Review and agree to minutes of previous meetings → OK
Amber press release should be out today.
ASN.1 compiler asn1c is now maintained outside of O-RAN SC in https://github.com/nokia/asn1c Related e-mail: link
December, 17 is the last meeting in 2019. Dec-31 we skip due to holiday season. First meeting in 2020 is on January, 14.
Status on this? No progress yet. We're working on good instructions. For now the best is to start reading README.md in the repo "it/dep" (https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree). This is maintained outside of the RIC platform project, though. Eventually, we will have the RIC platform deployment in ric-plt/ric-dep. We are also working on an xApp developer guide for how to develop an xApp in golang. Thoralf to check how we could do this for C++. There is value in the guideline describing a "base". It does not have to describe each and every option. Instructions should work on REC Akraino blueprint and on plain K8S. LE-status-20191204: Waiting for Felix' cleanup work (currently in review). After this 5 working days.
Related to the developer guide: current idea is to talk about (1) Helm Charts, xApp descriptor and schema files, (2) HTTP interface for K8s health probes (aliveness, readiness), (3) RMR interface for communication with other RIC components, (4) Logging, (5) SDL, (6) Config managements (Configmap), (7) metrics creation. If we do not have a E2SM coming soon into WG3, then some simple hello-world E2SM would be good as a base for a demo/sample xApp. We need to consider if we can use the demo1 xApp for the documentation. For C++ let's use a simple E2SM (which has nothing to do with X2). Aim for combined document go and C++. LE-20191204: Thoralf asked from Antti. No reply yet.
SDL Dev guide = 20191213 (LE given on 20191204)
Status of RMR library which will include new MEID handling and update of the documentation related to this.
1. RMR-routing manager and E2T-to-routing-manager interface is now designed. Scott is optimistic that RMR part is ready by end of this week.
2. Matti to at design of MEID routing in RMR under RMR wiki pages as "RMR MEID routing - draft design"
Some question related to SDL library from Bengi (primarily developing C++; possibly python).
1. Q: SDL user guide is needed. Should include some design principles and the big picture. E.g. why there are some constraints on the data types that can be used (e.g. using ordered sets). What is the role of event API and timer API, and when to use own namespace, role of access libraries for read and write APIs (e.g. R-NIB API of E2 manager (go)). Best practices around that also needed. TODO-Thoralf-ask-SDL documentation to go into open-src wiki.
Input from the TS use case for Bronze: "how do we update ML models" is one question we need to address in RICP
Need to plan how we use JIRA in RIC
RICAPP agenda: RICAPP Meetings.

2019-11-19

Recording: near_rt_ric_platform_project_meeting_2019_11_19.mp4

Review and agree to minutes of previous meetings
Release names: Amber, Bronze, Cherry are now decided.
INFO.yaml files should now be ready (exceptions: RSM and rtmgr). Committer management still requires approval by ToC. Plan is to change this approval practices for release Bronze. Once approved, PTL or delegate must update INFO.yaml with new/changed names and reference to approval. We might go for a solution where existing committers must approve and ToC only is notified, but this is not changed yet.
Amber release status by repo: Project Readiness for Amber Release#(NearRealtime)RICPlatform
All license exceptions (code re-used form other sources) are now listed here: https://lf-o-ran-sc.atlassian.net/wiki/display/ORAN/License+Attribution+Records To be approved by TOC on Wednesday, Nov-19.
We're working on good instructions. For now the best is to start reading README.md in the repo "it/dep" (https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree). This is maintained outside of the RIC platform project, though. Eventually, we will have the RIC platform deployment in ric-plt/ric-dep. We are also working on an xApp developer guide for how to develop an xApp in golang. Thoralf to check how we could do this for C++.
RICAPP agenda: RICAPP Meetings.

2019-11-05

Recording: near_rt_ric_platform_project_meeting_2019_11_05.mp4

Review and agree to minutes of previous meetings
Amber release status by repo: Project Readiness for Amber Release#(NearRealtime)RICPlatform
1. as part of this Paul asked, can someone actually deploy the RIC platform? Bengi clearly said that getting other RIC platform components up is difficult. Documentation needed.
Documentation guidelines: https://lf-o-ran-sc.atlassian.net/wiki/display/DOC/#DocumentationHome-RequiredFiles and Configure Repo for Documentation
New component request to be made for Resource Status Processor. Compare to Resource Status Manager (defined here).
Proposal: new component: resource-status-processor
The resource status processor handles incoming E2 resource status report messages and saves the data from these messages into the RNIB. Note that control or management of resource status reporting is not done by this processor, but by the Resource Status Manager. Committers: Shuky Har-Noy, Hila Anina, Yaki Ratz
I will also propose change of committers to TOC:
1. ric-plt/rtmgr: existing committers work on other project. New ones (all Nokia): Nithinsen K and Abdulwahid W
2. ric-plt/submgr: existing committers work on other project. New ones (all Nokia): Anssi Mannila, Juha Hyttinen
We plan to work on O1 implementation using "sysrepo data store plus netopeer 2" over the next few months. We also plan to work on A1 implementation and scalability if E2 termination component. Eventually this work is likely to become b-release content.
There will soon be coming changes in E2 definitions that we are currently using in near-RT RIC. Once WG3 settles on a stable draft specification we can start adapting.
RICAPP agenda: RICAPP Meetings.

2019-10-22

Recording: near_rt_ric_platform_project_meeting_2019_10_22_part1.mp4 and near_rt_ric_platform_project_meeting_2019_10_22_part2.mp4

Review and agree to minutes of previous meetings
Discuss repo changes before sending them as one batch to TOC for approval.
Release B planning: Contributions
O1 in Release B?
RICAPP agenda: RICAPP Meetings

2019-10-08

Recording: near_rt_ric_platform_project_meeting_2019_10_08_part1.mp4 and near_rt_ric_platform_project_meeting_2019_10_08_part2.mp4

Review and agree to minutes of previous meetings
Review and approve Scope of the RIC platform and its components (summary). After approval next step is to inform this to TOC. This was discussed. No further comments. Thoralf to bring this to TOC and to discuss the sentence "This source code is part of the near-RT RIC (Radio Intelligent Controller) platform project (RICP)" in TOC, esp. with Jack
B-release content. O1 southbound - if netconf based - as per Matti mainly related to xApp manager. O1 simulator RU and DU (requires yang as input). Provide yang models for RIC (with managed objects). Ritwick to post b-releas analysis in RSAC wiki page.
FYI. RICP presentation at ONS, Antwerpen, 2019: Overall architecture (not component-specific)
E2AP documentation in gerrit: https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/asn1-documents.git;a=tree
RICAPP agenda: RICAPP Meetings

2019-09-24

Recording:RICmeeting9-24.mp4

Review and agree to minutes of previous meetings
Open action item from last meeting: Thoralf Czichy : status check for each item with owners of JIRA item. 2019-09-24: Still open.
There are no particular issues being discussed in RICP in this session. So this will focus on RICAPP.
RICAPP agenda: RICAPP Meetings

2019-09-10

Recording: near_rt_ric_platform_project_meeting_2019_09_10.mp4

Review and agree to minutes of previous meetings
Discuss draft status report for RICP: Project reports
Who hosts next meeting on 2019-09-24 (Thoralf at ONS (Open Networking Summit) Europe, e.g., presenting RIC link )? → Matti
Open action item Thoralf Czichy : status check for each item with owners of JIRA item.
RICAPP agenda: RICAPP Meetings

2019-08-27

Recording: near_rt_ric_platform_project_meeting_2019_08_27.mp4

Review and agree to minutes of previous meetings
T1 = Antti, T2= Juha, T3 = Abdulwahid (was Viktor), T4 = Itamar, T5 = Rajesh, T6=Lusheng, T7=Bharath. All RIC items marked with suggested primary owner of the item. Thoralf to write e-mail to each suggested owner on status for each item. Initial JIRA filter: link.
1. need feedback by each PO by end of September - to facilitate release B planning.
RICAPP agenda: RICAPP Meetings

2019-08-13

Recording: near_rt_ric_platform_project_meeting_2019_08_13.mp4

Review and agree to minutes of previous meetings
Any objections to this proposal from RICP and RICA PTL: Meeting moved one hour later to 13:00 UTC. We will handle the meeting for the RICP (near-RT RIC platform) and RICA (RIC xApps) projects together. The respective PTL will handle their part. First 30 minutes with focus on RICP and the last 30 minutes focus on RICA. Note that if RICP takes less than 30 minutes, RICA issues might already be handled before 13:30 UTC. The meeting will be held every uneven week.
Release name finalized: "Amber" (former "A" release)
New repos (from the last 2 weeks) - see under "completed" Outstanding Resource Requests for Linux Foundation
NOT: If Thoralf found time to go through them before the meeting: "A" release Epics (focus on Epics that are under development) - assignment via JIRA is still missing.
RICAPP agenda: RICAPP Meetings
Rittwik mentioned an xApp proposed by Samsung which will be discussed in more detail in another O-RAN meeting later today (Rittwik to send details). Rittwik sent the details: RSAC meetings = https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC//calendars In any, case the RSAC meetings discuss release A and B planning items Zoom 1 bridge: https://zoom.us/j/9644759813 (Tue 9-10pm Eastern New York time every other week) and (Thu 9-10am Eastern New York time every other week)

2019-07-30

Recording: near_rt_ric_platform_project_meeting_2019_07_30.mp4

Review and agree to minutes of previous meetings
Notice: non-RT RIC project proposal: https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/15073282/RICnon-RT_OSC_project_proposal.pdf
Notice the links/instructions for o-ran-sc's JIRA, e-mail, Gerrit: Tools (mailing list, JIRA, Gerrit)
1. Former user (Deleted) mentioned that the Thoralf Czichy need to re-check the user stories/Epics in Jira. We need to assign each item to persons (e.g. subproject leads)
Any ideas on Election process for new committers for RIC repos .
1. Thoralf Czichy to make proposal with Former user (Deleted)
2. (Update-Jul-31-2019: Jack Murray needs to write down a manual for this (including some ideas how to make it more efficient), ideally by Aug-7. If not, maybe Lusheng can at least write down how it is currently handled)
Any ideas on Process for new repos (RIC PTL (or person nominated by PTL) suggests to TOC. TOC confirms. Repo can be created)
1. Thoralf Czichy to make proposal with Former user (Deleted)
2. (Update-Jul-31-2019: Jack Murray needs to write down a manual for this (including some ideas how to make it more efficient), ideally by Aug-7. If not, maybe Lusheng can at least write down how it is currently handled)

2019-07-23 (no meeting due to holiday period)

2019-07-09 (no meeting due to holiday period)

2019-06-25

Agenda/Notes

Review and agree to minutes of previous meetings
Code review practice and bootstrapping of committers. https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/Tutorials and https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/Seed+Code+Contribution Contact Lusheng Ji if things are not clear (https://lists.o-ran-sc.org/g/main/message/57).
General available information: The release calendar: https://lf-o-ran-sc.atlassian.net/wiki/display/REL/Releases
1. Q (Pierre-Henri): are all projects following the calendar. Ritwick: Yes, but only pairwise testing between the project components as per testing strategy and acceptance criteria in EPICs.
Release A requirements for RIC, but also incl. eNB and O-DU/OFH: https://lf-o-ran-sc.atlassian.net/wiki/pages/viewpage.action?spaceKey=RSAC&title=Contributions
1. comments expected by end of US business day Wednesday, 26.Jun Comment directly to wiki page.
2. Note that the document suggest the usage of ONAP's https://wiki.onap.org/display/DW/OTF+-+Open+Test+Framework
(Any preferences on rocketchat vs IRC?)

Project meetings (old)

Latest meeting minutes

Broken links to meeting recordings

2023-10-24

2023-10-10

2023-09-26

2023-09-12

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

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

2023-08-01

2023-07-18

2023-07-04

2023-06-20

2023-06-06

2023-05-23

2023-05-09

2023-04-25

2023-04-11

2023-03-28 (Tuesday)

2023-03-14 (Tuesday)

2023-02-28 (Tuesday)

2023-02-14 (Tuesday)

2023-01-31 (Tuesday)

2023-01-17 (Tuesday)

2023-01-03 (Tuesday)

2022-12-06 (Tuesday)

2022-11-22 (Tuesday)

2022-11-08 (Tuesday)

2022-10-25 (Tuesday)

2022-10-11 (Tuesday)

2022-09-27 (Tuesday)

2022-09-13 (Tuesday)

2022-08-30 (Tuesday)

2022-08-16 (Tuesday)

2022-08-02 (Tuesday)

2022-07-19 (Tuesday)

2022-07-05 (Tuesday)

2022-06-21 (Tuesday)

2022-06-07 (Tuesday)

2022-05-24

2022-05-11 (exceptionally Wednesday)

2022-04-26

2022-04-12

2022-03-29

2022-03-15

2022-03-01

2022-02-15

2022-02-01

2022-01-18

2022-01-04

2021-12-21

2021-12-07

2021-11-23

2021-11-09

2021-10-26

2021-10-12

2021-09-28

2021-09-14

2021-08-31

2021-08-17

2021-08-03

2021-07-20 no meeting

2021-07-06

2021-06-22

2021-06-08

2021-05-25

2021-05-11

2021-04-27

2021-04-13

2021-03-30

2021-03-16

2021-03-02

2021-02-16

2021-02-02

2021-01-21 4th meeting on Dawn planning

2021-01-19

2021-01-05

2020-12-22

2020-12-08 dawn planning

2020-12-08 main project meeting