Meeting Info

All meeting notes

2022-09-13 (Tuesday, cancelled) → 2022-09-20 (Tuesday)

Recording Link: TBA 

Presentation: TBA

Agenda: 

1. Holding regular meetings every other week
   
   1. hoejoo lee wants to have an official meeting every other Tuesday. 
   2. It is also possible to arrange unschedules meeting if needed
   3. we can discuss offline by email or confluence pages for a certain issue.
2. Sprint 
   1. The first sprint has started (Sprint #1)
      1. https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=57377588
   2. Repo creation 
      1. For this sprint
         1. portal/aiml-dashboard
            aiml-fw/awmf/tm
            aiml-fw/athp/tps/kubeflow adapter
            aiml-fw/athp/sdk/feature store
            aiml-fw/athp/sdk/model storage
            aiml-fw/athp/data extraction
      2. Next sprint

         1. aiml-fw/dep

         2. ricapp/qp-aimlfw
3. Action item of the previous meeting
   1. about deployment repository
      1. keep the separate repository from it/dep as RICPLT
4. About F2F Demo
   1. Joseph will share the situation and then we need to discuss the demo scope and quality.
5. Discussion about cooperation with Keysight (Eng Wei Koo)

2022-09-06 (Tuesday)

Recording Link: https://zoom.us/rec/share/aGhbxgdk6Ql6J-tGxi_Nb87znEDESSOhlV5Iwi1M0IQ53owkoNDpan0O3YRB5-Hr.hYHSHbfEyFrDc5-J 

Presentation: 

1. Greetings
2. hoejoo lee The First sprint will start on the 12th -  O-RAN SC's dev sprint2 begins on the 12th and ends on the 30th Sep.(Releases - Releases - Confluence (o-ran-sc.org)
3. hoejoo lee Jira Task creation is in progress. For seed code contribution, we will use an epic name as 'seed code', after that I will bring the names for the next features. 
4. G release 
   1. G Release
      1. G Feature Scope / Achievements:
         
         • Stand-alone installation with Kubeflow as a Training host backend and Kserve as an Inference host backend
         • Manual Deployment of ML rApp and ML xApp
         • Initial Training Job Management (Data extraction/feature management)
         • Sample ML pipeline and ML xApp: QoE Prediction model using LSTM with data from ricapp/qp) => will bring this issue as a discussion point to RICAPP project
5. Introduction of the project
   1. Initial Repositories :
      1. Joseph Thaliath  said that we would create aiml-fw/dep repository and link to it/dep
      2. James Li worried about the separate deployment repository from it/dep. He thinks of integrating all deployment flows and manage together in the same repository.
      3. Avinash Bhat  suggested discussing in the 'integration' meeting
   2. Architecture Flow for Initial Seed Code Contribution
      1. James Li said that about the seed code, for python language, it is required to put on the dependencies in the requirements.txt to check on the license standing in the dependencies quickly.
      2. James Li also said that there might be some researchers who are interested in this project. They are mostly focusing on developing models, they might want to see the data set availability. 
      3. Joseph Thaliath said that currently, this project focuses on the development of the framework, and we try to show the demonstration with a sample use case and test the framework. Jack from the TOC meeting also worries about data management. After the G release we can discuss data management as well because then we secure the basic version framework.
      4. Sridhar Rao suggests working with ITU-T since there is data for many RAN use cases.
6. Discussion with projects
   1. MVP contribution related to AIML workflow
      1. Joseph Thaliath mentioned that we would provide some feedback to get a better understanding of the expected end-to-end workflow
      2. Joseph Thaliath/ Avinash Bhat said that we will be following the discussion from the MVP-C meeting and presenting our views.
   2. EMCO framework
      1. Joseph Thaliathsaid that we are checking the cooperation with EMCO project, and they would be presenting a demo in the follow-up meeting. We will keep an eye on it. 
7. CII badging
   1. Joseph Thaliathsaid that we also need to keep in mind about this