Versions Compared

Old Version 11

changes.mady.by.user Thoralf Czichy

Saved on

compared with

New Version 12

changes.mady.by.user Thoralf Czichy

Saved on

Key

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

...

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


2022-04-26

Recording: link to zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. 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
  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. We did not do this today.
  3. 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?
  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.
      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
  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.
  6. 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 user-30c9d reported in TOC that this work is done.
  7. 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
  8. 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.
  9. 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.
  10. 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
  11. 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.
  12. RICAPP agenda: RICAPP Meetings.

2022-04-12

Recording: link to zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. 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.
  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. We did not do this today.
  3. 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?
  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.
      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. 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)
  6. 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 user-30c9d reported in TOC that this work is done.
  7. 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.
  8. 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
  9. RICAPP agenda: RICAPP Meetings.

2022-03-29

Recording: link to zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/7955 ok, removal of deprecated code
  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. We did not do this today.
  3. 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?
  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.
    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?
  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-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
  6. 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 user-30c9d reported in TOC that this work is done.
  7. RIC-641 Sandeep (HCL) is working on this. Work is progressing
  8. 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
  9. RICAPP agenda: RICAPP Meetings.

2022-03-15

Recording: link to zoom recording

...

  1. 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.
  2. 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.
  3. 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

  4. 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
  5. Initial discussion on alpine base images. We handle by e-mail. At least QP xApp uses alpine (the same was as A1)
  6. 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.
  7. InfluxDB issue (simple single-instance should be enough).
  8. configuration handling in E2AP seems to settle down. Rahul (not in meeting today) will finalize via e-mail.
  9. Subhash (Samsung) asked about t-lab access. About VMs OSC Community Lab -Labs Note that HCL is also working on this. Matti looking for someone from ATT to help (Felix busy).
  10. RICAPP agenda: RICAPP Meetings.

...