Versions Compared

Key

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

...

 check from here: Project meetings

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

  1. Cherry status. See Cherry Release (Dec 2020) - 12 items status unclear, 18 items done, some amount of items moved out from Cherry TODO-link
  2. Dawn filter: link
  3. Dawn - another planing meeting next week or two weeks from now? One meeting two weeks from now. Thoralf to schedule.
  4. 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).
  5. 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
  6. CLI footprint
    1. no data yet.
  7. RICAPP agenda: RICAPP Meetings.

2020-11-10

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_11_10.mp4

  1. After this meeting we had  Dawn planning meeting. Updated slideset (v6 - same link as before): https://wiki.o-ran-sc.org/download/attachments/3605124/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
  2. 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.
  3. Status updates
    1. HCL
        • 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.
  4. 5min Subhash (Samsung) to present CLI plan. More discussion needed. check progress in two weeks from now.
  5. RICAPP agenda: RICAPP Meetings.

2020-10-27

Recording: RIC_and_RICAPP_dawn_planning_2020_10_27_part2.mp4

  1. 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
  2. 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.
  3. Dawn planning slide: https://wiki.o-ran-sc.org/download/attachments/3605124/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.
  4. RICAPP agenda: RICAPP Meetings.

2020-10-13

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_10_13.mp4

  1. note the presentations on RIC and xApps from ONeS (link) and in O-RAN. 
  2. demo on Thursday Sprint demos → 2020-10-15 Cherry R6.2 (please add agenda items)
  3. asn1-py as separate repo or as part of xapp-frame-py? Discussion to be continued over e-mail.
  4. 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://wiki.o-ran-sc.org/display/RICP/E2+Manager+R4+Interface+Design#E2ManagerR4InterfaceDesign-X2SetupRequest(Deprecated)

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

...

  1. Note that previous demo was on Thursday, 2020-08-13 Cherry R5.4. Recording available on the confluence page.
  2. 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.
  3. 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."
    1. 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

    2. None of the components except ric-plt-a1 (scanned 3 months ago) is onboarded to NexusIQ.

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

    1. T1 (Antti)
      1. RIC-114 scope change
    2. T2 (Abdulwahid)
      1. Routing Manager now supports route distribution to multiple RMR control ports.
    3. T4 (Avinoam)
      1. E2M - Get node list API changed and now return also the node connection status - completed. Swagger : https://wiki.o-ran-sc.org/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)

    4. 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
    5. T6 (Lusheng)
    6. T7 (Bharath)
    7. Subteam-h1 (Alok, Sangeetha)

      1. Ticket NumberTicket Summary8/18 Updates
        RIC-109DB: 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-360Plan and prototype helm (and k8s) upgrade with xApp manager, REC, RIC infrastructureUnderstood 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-509Components supporting continuous integration infrastructure, e.g., static code analysisLocal 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-150Perform e2e RIC benchmarkingUnderstanding 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-149Define and implement automated test cases for flows to be defined early in Bronze-R4Understood 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.


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

...