Versions Compared

Old Version 538

changes.mady.by.user Thoralf Czichy

Saved on

compared with

New Version 539

changes.mady.by.user Thoralf Czichy

Saved on

Key

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

...

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

...