Versions Compared

Key

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

...

  1. Introductions
  2. Agenda bashing
  3. Level set ChrisC
    1. Presentation by ChrisC
    2. Ranny: Could be an opportunity to expand OOM? Might need approval from TSC, OOM PTL, Architecture Subcommittee. Need participation by OOM PTL/committers. Christophe: Already spoke to Sylvain Desbureaux  about fine tuning charts, but no discussion yet about extending the charts. We already have a PoC requirement but it has not been tied to a particular release. Catherine is aware, Christophe can present to the Architecture Subcommittee as needed. Ranny: First let's start with OOM. Christophe: The idea of packaging O-RAN-SC components as a CNF, the idea came from Sylvain. Martin: Each of the O-RAN-SC components is a CNF, it's not one CNF. Exception could be NONRTRIC that's part of the ONAP platform. So a couple of CNFs for the O-RAN-SC components e.g. simulators. Amar: What are these extra components other than simulators? John: Yes there are NONRTRIC specific components, they are platform components within the NONRTRIC. Kamel: Do we want one deployment with namespace for NONRTRIC and Near-RT-RIC? Christophe: Goal is the deploy the components in the easiest way for the user. We use a chart to deploy in the same name space and use the certificates etc. in a common way. We can let the charts hide the details. Some scope discussion. Deliverable should be just the SMO. John: We need to be careful not to view the SMO as "one" entity. We need to maintain the option to have multiple SMO options. If that's the case, isn't it just a series of OOM deployments? The only key is NONRTRIC. General consensus: the crux of this is to figure out how to deploy external components through OOM. 
    3. So maybe the first task at hand is to figure out override file(s) and install the NONRTRIC through OOM expansion. Then we can worry about testing, simulators etc. 
    4. Martin: Link to an override file used 6 months ago: https://wiki.o-ran-sc.org/display/IAT/Deployment+in+kubernetes 
  4. Which repository All
  5. Logistics for the meeting with respect to O-RAN-SC and O-RAN cross community meeting All
  6. Open discussion All

...