Versions Compared

Key

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

...

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

...