- Gemaakt door Farheen Cefalu, laatste wijziging door Martin Skorupski op mei 15, 2021
Je bekijkt een oude versie van deze pagina. Bekijk de huidige versie.
Vergelijk met huidige Toon pagina historie
« Vorige Versie 26 Volgende »
Scope
According to the O-RAN-SC-OAM-Architecture document, all ManagedElements (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the O1-interface.
The O-RAN-OAM-interface specification defines
- a NetConf-Server for Configuration Management (CM) and
- a http-client for Fault Managment (FM), Performance Management (PM) and other events
on each Management-Service-Provider (MnS-Provider) running on the ManagedElement (ME).
The O-RAN-SC-OAM project provides reference implementation according to the O-RAN OAM (WG1) documents. In addition we provide a common MnS-Consumer for development and module test purposes. The assumption is that the projects for the ManagedElements can concentrate on the more important user-plane.
Of course each project needs its own OAM repo to address the specific needs of the ManagedElement.
Messenger
You can find us on Slack: https://onapproject.slack.com/archives/C01K8CNUJA2
Development
Jira: https://jira.o-ran-sc.org/projects/OAM/summary
Gerrit: https://gerrit.o-ran-sc.org/r/q/oam
Jenkins: https://jenkins.o-ran-sc.org/view/oam/
Nexus: https://nexus.o-ran-sc.org/#nexus-search;quick~oam
Sonar: OAM, Modelling, RIC Dashboard, O1-TR069-Adapter
CII:
Mailing list and #oam
We use main@lists.o-ran-sc.org with hashtag "oam" in the subject of emails.
Please make sure that you add somewhere in the subject of your email "#oam".
Example subject: "#oam Please help!"
More examples: https://lists.o-ran-sc.org/g/main/search?q=%23oam&ct=1
O-RAN-SC members who are not interested in OAM email conversations can mute the hashtag "#oam": https://lists.o-ran-sc.org/g/main/hashtags
Space contributors
- Geen labels