Meeting Info

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

Zoom 1 Info:

• Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/9644759813
• Meeting ID for dial-in: 9644759813

2021-01-19

1. 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.
2. 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
3. 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.
4. 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.
5. going through current list of Dawn items and checking commitments - meeting on Thursday, 8am, ET.
6. RICAPP agenda: RICAPP Meetings.

2021-01-05

Recording: near_rt_ricplatform_and_ricapp_meeting_2021_01_05.mp4

1. 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.
2. 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, )
3. 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).
4. 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.
5. RICAPP agenda: RICAPP Meetings.

2020-12-22

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_12_22.mp4

1. we started 15 minutes late
2. next meeting Jan-5-2021
3. 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).
4. A1/EI implementation plan A1-EI-HLD.pptx
5. 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

1. CII badging status (end of Cherry) needs to be filled in: CII status: near-RT RIC
   1. nobody volunteered. Thoralf to do this.
2. committers changed for E2T and E2Mgr. For A1, for ric-dep
   1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/5249 ric-dep
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/5196 e2mgr
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/5195 e2
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/5238 a1
3. 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
4. demos in December for Dec-17? let me know if there's something to demo.
   
   1. HCL proposed demo of benchmarking
5. meeting on Dec-22? We will keep the meeting. What about Jan-5? Also ok.
6. 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.
7. Samsung: no updates related to Cherry.
8. RICAPP agenda: RICAPP Meetings.

For Dawn planning meeting:

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

Older meeting minutes

check from here: Project meetings (old)