Time & Location:
Meeting Detail: Times & Joining Info
Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !
NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar)
- Summer Daylight Savings time eventually stabilizes to: 9am PDT | 12pm EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 19:00 EEST | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)
- Winter (non-DST) time eventually stabilizes to: 9am PST | 12pm EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 19:00 EET | 22:30 IST | 01:00 CST (Thurs) | 02:00 JST (Thurs)
- (During Winter→Summer DST changeover we follow US time. Summer→Winter we follow Europe time)
Zoom Bridge : https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Joining the meeting:
- Meeting ID: 890 6970 8424
- Dial in: (Local numbers)
+1 646 558 8656 US (New York)
+49 30 5679 5800 Germany
+49 69 3807 9883 Germany
+353 1 240 8941 Ireland
+46 8 4468 2488 Sweden
+46 8 5016 3827 Sweden
+358 3 4109 2129 Finland
+358 9 7252 2471 Finland
Date
Attendees
- John Keeney
- Martin Skorupski
- Alex Stancu
- Dibas Das
- user-4594e
- Fernando (Fred) Oliveira
- HariomGupta(HCL)
- James Li
- Kamel Idir
- Lasse Kaihlavirta
- Lathishbabu Ganesan
- Marcin Krasowski
- Scott Blandford
- Sonia Sangari
- Swaminathan Seetharaman
- Timo Perala
- Sorry - didn't manage to get a full attendees list for this meeting ... please add/remove yourself
See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
- Co-located with ONAP 2021-04-28 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents:
Recording
Notes:
Housekeeping:
- Reminder from previous weeks:
- OSC SMO calls now move to its own time slot - Thursdays
- See OSC RSAC Calendar: https://wiki.o-ran-sc.org/display/RSAC/calendars
- (Note this meeting to open to anyone, including non-ORAN members)
- We will maintain this slot for ONAP Alignment, and try flag issues/question to/from SMO meetings.
- See OSC SMO Project meeting notes
OSC Project roundup:
NONRTRIC (John Keeney)
- Continuing work as reported in past weeks:
- Helm chart onboarding function - hopefully eventually useful for rApp management once the concept is defined.
- Service exposure function - based on A1 serive exposure gateway for other SMo services - hopefully eventually useful for R1 once the concept is defined.
- O-RU/O-DU helloworld FH recovery use case scripts: 2 different options:
- Standalone script - hopefully eventually deployed as helm chart above
- ONAP policy - exposing ONAP PF as an SMO service - hopefully eventually exposed as above
- Control extensions - Looks similar but redesigned & re-implemented in backend
- Add new support for A1 PMS configuration
- Greatly increased test coverage
- On track for OSC D release delivery
- Thanks to Alex Stancu for feedback re O-DU & O-RU simualtors
SIM (Alex Stancu)
- Docker images improved in Nexus for RU and DU simulation - based on the very simple models for the use cases
- O-RU
- O-DU
- Documentation at "D" Release - Closed Loop Use Case: Simulation of O-RU and O-DU
- All simulators have the same basis - so new simulators are easy to create/configure - DIY
- Lots of variants of other simulators can be created from O1 simulator
OAM (Martin Skorupski)
- New repo: nf-oam-adapter https://gerrit.o-ran-sc.org/r/admin/repos/oam/nf-oam-adopter
- user-4594e has started adding some content
- Likely ODL Aluminium SR3 will be used in CCSDK H Maintenance release.
ONAP Slicing Update (Swaminathan Seetharaman )
- https://wiki.onap.org/display/DW/R9+E2E+Network+Slicing+use+case
- https://wiki.onap.org/display/DW/R8+E2E+Network+Slicing+use+case
- https://wiki.onap.org/display/DW/E2E+Network+Slicing+Use+Case+ONAP+Weekly+Meetings
- Presented Slicing progress from earlier versions & plans for I release
- Honolulu & continuing into plans for Istanbul
- Trying to support multiple versions of ONAP & 3PP NSSMFs, NSMFs, CCMSF
- For RAN slicing the O-RAN Alliance preference seems to be that RAN NSSMF coordinates Transport NSSMF. Currently done in ONAP.
- Some others prefer RAN NSSMF just does RAN slicing, - not transport. Transport Slicing controlled by Transport NSSMF requested via NSMF.
- Working together with ONAP & ORAN stakeholders
- Working on some closed loop use scenarios:
- Working on Slice configuration - not instantiating new Slices/CNFs/VNFs etc. (Instantiation already done) (More sophisticated in J release?) (Want to align with O2 once available)
- ML model learning (via NONRTRIC) - updating configurations to NearRTRIC via A1 (or O1?)
- Current& Ongoing: Slice Analysis uService, triggers ONAP Policy, which invokes SO (RAN NSSMF), to invoke SDN-C (O1) to near-RT-RIC.
- Some operations perhaps by A1 instead? To be confirmed from O-RAN Alliance. O1 v A1 - depends whether configuration or policies.
- Kamel Idir Can the near-RT-RIC do this? Will it be able to access all cells etc for a given NSSAI.
- Swaminathan Seetharaman Currently needs to be configured over O1. Config info also passed to near-RT-RICS.
- John Keeney Need to confirm with O-RAN Alliance. Initial, RAN-Wide (multiple near-RT-RICs) would need to be coordinated in SMO / Non-RT-RIC.
- Swaminathan Seetharaman Working on a Simulation environment
- user-4594e Anything on O2?
- Swaminathan Seetharaman Not yet ... Something coming in Q3?
- Swaminathan Seetharaman Needs to work on RAN service modelling to support Slice creation (e.g. VNF instantiation) - For J release most likely
- Martin Skorupski Where are the code contributions etc?
- Swaminathan Seetharaman Scattered across many functions - e.g. SO mainly, OOF, SDN-C, CPS, SDC, DCAE
- Swaminathan Seetharaman Slice Profile definition needs to be decomposed & translated to be understood by NSSMFs - could be formulated as an optimization problem. Currently in OOF. Currently rule-based in OOF with SDN-R. Still lots to do on consistency checking etc.
ONAP-Configuration Persistence Service (CPS) (user-4594e)
- https://wiki.onap.org/display/DW/Configuration+Persistence+Service+Project
- user-4594e presented slides giving summary & status of ONAP CPS
- Slicing is the first use case ...
- Q: John Keeney What is relationship between SDNC & NCMP? Which to use to configure an xNF?
- Can use either - Can configure via NCMP or SDNC - if use SDNC directly then CM notification will update NCMP - eventual consistency.
- Q: Martin Skorupski Namespaces?
- Not Yang Namespaces ... Vendor namespaces instead - used to identify ownership
- Q: Martin Skorupski Extending/augmenting other models?
- Not yet - but needed. (Partial supported, but more work needed)
- Hopefully we can more requirements from OSC? especially to find corner cases etc. Improvements are use-case prioritized.
ONAP-OSC & QA:
- Skip for this week. Ran out of time.
- Please contact us direct for any questions/comments