Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Date:

 

Bridge:

 https://zoom.us/j/91642200926?pwd=cjNOSjIwYndySEpWSEd0MjA4bTlPdz09 

Attendees

Notes

  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, without forking OOM (so we can keep taking advantage of the OOM work).
    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. Inclusion of the NONRTRIC is mandatory since without it there is no value, the override already exists.
    4. Martin: Link to an override file used 6 months ago: https://wiki.o-ran-sc.org/display/IAT/Deployment+in+kubernetes for ONAP OAM parts of the SMO. The NONRTRIC parts were deployed together with that chart to form a single combined SMO/OAM/NONRTRIC deployment.
    5. Next step is to discuss with the OOM team and figure out what their recommended solution is.
  4. Which repository All
  5. Logistics for the meeting with respect to O-RAN-SC and O-RAN cross community meeting All
    1. John: keep the meeting separate at least initially
    2. Martin: Yes agree, at least initially
    3. We can keep the meetings separate for now with cross-reporting, and merge later if needed
  6. Open discussion All
  7. Next week
    1. Invite OOM team members for the next call to resolve the issue. in 3c. Christophe to invite OOM team members.


Recordings

Recording link

Action items

  •  


  • No labels