Versions Compared

Old Version 15

changes.mady.by.user Jackie Huang

Saved on

compared with

New Version 16

changes.mady.by.user Martin Skorupski

Saved on

Key

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

...

Please see:  Use Case Flow tests for E-Release

Operation and Maintenance (OAM)

Primary Goals:

  • Support of RASC VES architecture updates of OAM related interface definitions based on
    • YANG from WG4 - O-RAN Management Plane Specification - YANG Models 5.0 - November 2020 (with dependencies to IETF data models)
      • status: done
    • YANG from WG5 - O-RAN O1 Interface for O-DU 1.0 - YANG Models - November 2020 (with dependencies to 3GPP data models) 
      • status: after feedback of WG5, related merge request was abandoned - instead a pipline will be establish with O-RAN bitbuckets.  
    • YANG from WG1 - O1-interface (November 2020 train)
      • status: not approved by O-RAN
    • VES from ONAP DCAE - VES 7.2
      • status: done
    • Notification syntax from 3GPP TS 28.532 V16.6.0
  • support D-Release use case "O-RU recovery"
    • see Feature Scope below
    • Deployment of VES-Collector and Message Bus at the edge
  • Support of O-DU use case ()
    • Definition of the to be used yang model. 
  • Support of pre-spec PM streaming - VES like approch (see https://wiki.o-ran-sc.org/download/attachments/35881433/E_rel_v3.pptx?api=v2 page #97)
    • creation of a CR to WG10 OAM Interface Specification - "Model-driven PM streaming"
    handover SMO artifacts to new SMO project

E Feature Scope: 

  • Update Switch to OpenDaylight Silicon
  • Support of Callhome via TLS
  • CallHome to VES:pnfRegistration 
  • Opendaylight version Silicon -SR2
  • Standard-defined VES for
    • NotifyNewAlarm
    • NotifyAlarmCleared
    • NotifyHeartbeat
    • NotifyMoiChanges
    • PerfDataStreamingMNS
    o-ran-fm.yang/alarm-notif to VES:fault

PTL: Martin Skorupski

E release source code, container images and deployment instructions (and status)

Jira: Count of Epics ( 15 issues ), User Stories, Tasks, and Issues:  166 issues

Source Code:

Integration:

  • E-Release Integration (and its sub pages)
  • Test Topologyto be done

Release notes:

  • to be done


O-RAN Central Unit (OCU)

Primary Goals: 
  • In the absence of O-CU, Radisys commercial CU image to be used for E2E testing

D Release Feature Scope: 

  • Radisys Commercial CU being used as a test fixture for E2E testing
PTL:

Status:

Radisys Commercial CU being used as a test fixture.

H/W and S/W requirements have been shared and awaiting the same to be configured.

D release source code, container images and deployment instructions

not applicable

...