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

Compare with Current View Page History

« Previous Version 310 Next »

Meeting Info

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

Zoom 1 Info:

UTC-timeevery 2nd Tuesday, check from calendar

https://zoom.us/j/9644759813

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

+358 341092129

Other international numbersWorld Time Zone Map

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


2021-05-25

Recording:

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. https://gerrit.o-ran-sc.org/r/c/ric-plt/rtmgr/+/5990 (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)
    13. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6081 (replaced by other review, anyway contains test cases, but will likely be abandoned anyway)
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports

      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)

      6. ric-plt/e2 0,0 // no bugs (2021-04-23)

      7. ric-plt/e2mgr 88,4 // no bugs (2021-01-30)

      8. ric-plt/lib/rmr 86,1 // no bugs (2021-05-25)

      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-05-18)

      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,7 // 2 blocker bugs (2021-05-19)

      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.
    3. How to get reports more frequently?
    4. ric-plt/e2 is already being handled via RIC-731 (expected to complete in Dawn)
  3. 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"
  4. Sunil. RIC-723 further input needed from Thoralf
  5. 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
  6. RICAPP agenda: RICAPP Meetings.

2021-05-11

Recording: link to zoom recording

  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. 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.
  2. 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
  3. 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.
  4. Thoralf still to update or CII evaluation
    1. I added RC-5
  5. Heewon's xApp python framework issue related to RIC-773 - some issues still
  6. 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
  7. No progress done on E2APv1.1 support as Naman cannot work on it yet.

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

  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/+/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).
  2. 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.
  3. Thoralf still to update or CII evaluation
  4. Heewon's xApp python framework issue related to RIC-773 - check agian two weeks from now.

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

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

  7. RIC-731- [Static code and test coverage for E2] -  90% Completed. Blocked on RIC-760 for test coverage. Same status as in last meeting

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

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

  10. .RIC-743 Create multiple e2sim for RIC benchmarking Same status as in last meeting

  11. RIC-744 Verify the E2E communication for multiple e2sim  Same status as in last meeting

  12. 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.
  13. 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
  14. RICAPP agenda: RICAPP Meetings.

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

Older meeting minutes

check from here: Project meetings (old)

  • No labels