Time & Location:

New Meeting Slot

We have now moved to new meeting slot Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !


Please note our new Zoom Bridge

https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09

Meeting ID: 890 6970 8424



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)

  • 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

See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)

Contents:


Recording

Notes:

Housekeeping:

  • 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.

OSC Project roundup:

NONRTRIC (John Keeney)

  • Wrapping up A1 Policy contributions in ONAP Honolulu as M3 approaches - of course integration, documentation, testing etc will continue.
  • Control panel re-engineering ongoing - backend mainly
  • Starting some prototyping around rApp execution platform & packaging.
    • Will present a more detailed proposal in coming weeks.

SIM (Alex Stancu)

  • New RAN Simulator (NS-3 based simulator)Alex Stancu
    • Facebook? & Berkeley ? Alex Stancu will begin joining calls
      • Meeting times are challenging.
    • Alex Stancu continuing to try get more information.
  • No other update at this stage

OAM (Martin Skorupski)

  • Continuing to work on Alarm Management
    • Mapping netconf alarm managment events in ODL to VES.
    • Ref https://wiki.onap.org/display/DW/ODLUX+Alarm+mappings

      • Discussion with Swaminathan Seetharaman about use of alarm messages in SON OOF PCI collisions usecase

      • Alarm used in PCI Collision OOF use case 
        {
  "event": {
    "commonEventHeader": {
      "version": "4.0.1",
      "vesEventListenerVersion": "7.0.1",
      "domain": "fault",
      "eventName": "Fault_RansimAgent-Wipro_RanPCIProblem",
      "eventId": "fault000001",
      "sequence": 1,
      "priority": "High",
      "reportingEntityId": "de305d54-75b4-431b-adb2-eb6b9e546014",
      "reportingEntityName": "ncserver2",
      "sourceId": "cc305d54-75b4-431b-adb2-eb6b9e541234",
      "sourceName": "Chn0025",
      "startEpochMicrosec": 1451772223000000,
      "lastEpochMicrosec": 1451772403000000,
      "timeZoneOffset": "UTC-05:30",
      "nfNamingCode": "RansimAgent",
      "nfVendorName": "Wipro"
    },
    "faultFields": {
      "faultFieldsVersion": "4.0",
      "alarmCondition": "RanPciCollisionConfusionOccurred",
      "eventSourceType": "other",
      "specificProblem": "Collision",
      "eventSeverity": "CRITICAL",
      "vfStatus": "Active",
      "alarmAdditionalInformation": {
        "networkId": "NTWK005",
        "collisions": "1",
        "confusions": "1"
      }
    }
  }
}
      • Swaminathan Seetharaman user-4594e Martin Skorupski Discussed different options correlating & ordering of multiple messages related to same alarm.
        • Ref Fault_RansimAgent-Wipro_RanPCIProblemCleared when alarm is cleared, etc. 

ONAP - OSC:

Other


  • Lasse Kaihlavirta What is, and why does ONAP A1 Policy Management Service have a DMaaP interface. It doesn't do much.
    • John Keeney Correct, it is quite simple, Just a pass-thru to the REST interface. Support Asynchronous requests over DMaaP as an alternative to REST.
      Pointless? ... Functionality is based on requirements from users, even though it is difficult to see why such a requirement exists.
    • Lasse Kaihlavirta John Keeney Is there any other examples? e.g. a Read Topic & Write Topic.  Can't recall off-hand. (After meeting. This this is the appraoch used by DMaaP request/responses for some ONAP Control loop examples)
    • Martin Skorupski Struggled with similar requirments in SDNR. Eventually mapped the use case to use a VESmessage instead.
    • The use of DMaaP is sometimes used to support load-balancing, but not obvious that this is the right way to do load balancing ...


  • Hieu Nguyen: ONAP A1 Policy Management Service direct to near-RT-RIC vs via A1 Adapter
    • John Keeney Both are possible. Currently A1 adapter is a straight-thu connector.
      • Reasons to use A1 Adaptor
        • Co-locate A1 terminate with O1 CM/Netconf connections in same controller instance.
        • Good Interception/integration point to add implement specific load-balancing or security functions etc.
        • Good Interception/integration point todo O1/A1 coordination - e.g. no A1 if function is in locked administrative state. SLI can be used for this check.


  • Hieu Nguyen: What is the HTTP/S proxy support in ONAP A1 Policy Management Service and A1 Adapter?
    • John Keeney Some operators maintain a proxy between their RAN domain & OAM layer. It is not common (prior to A1) to have a REST interface between RAN & OAM - so this requirement in CCSDK is only now becoming apparent.
    • user-4594e Sees this requirement in operator networks, e.g. connecting through Bastion.
    • John Keeney HTTP/S Proxy support is added to A1 Policy Management Service (specifically for A1 connection only) - Configurable via configuration files. See documentation for details.
    • John Keeney HTTP/S Proxy support is not yet added to A1 Adapter, since it uses the CCSDK SLI node function to perform REST calls southbound. This function needs to be extended in CCSDK (or a new one added). This changes, and associated regression testing will be quite tricky.


  • Konrad Bańka Still looking for interesting topics to contribute in A1 Policy work in ONAP
    • John Keeney Many of our requirement already done for Honoloulu
    • If interested, we're examining how to add HTTPS proxy support for A1 Adapter (e.g. user-4594e Bastion in a real world deployment) but may have serious knock on effects for other functions & regression testing using SLI graphs etc ....
    • John Keeney Any other ideas, requirements or contributions are very welcome from the community (smile)


  • Vidhu Shekhar Pandey Whats the plan & whats needed for O-DU for new O-RU-FH usecase?
    • Martin Skorupski Need a  (custom?) Yang model for O-DU ....
    • Martin Skorupski Needa list of initial configurations, ... even a spreadsheet?  How to set up the neconf connection? See OSC SMO/OAM Docker Compose file for a first simple environment setup for netconf client etc. Martin Skorupski will provide a link ...
    • Vidhu Shekhar Pandey Can we do  manual provisioning/configuration first to get started. Martin Skorupski ... Of course. Lets discuss off line to do this as easily as possible.