1. Pages
2. …
3. Open Transport Configuration and Control Home
4. 5G-xHaul
5. 5G-xHaul Call-in Details & Notes

2021-07-14 5G-xHaul Meeting notes

00:05

supportedAlarmList to get DefaultValue and *

proposal made for → on the agenda for approval 2021-07-28

supportedAlarmList to get DefaultValue and *

same subject as Hybrid MW Structure #23 → same solution

proposal made for → on the agenda for approval 2021-07-28

supportedAlarmList to get DefaultValue and *

same subject as Hybrid MW Structure #23 → same solution, but min element 2 → multiplicity goes to *

proposal made for UML and YANG → on the agenda for approval 2021-07-28

supportedAlarmList to get DefaultValue and *

same subject as Hybrid MW Structure #23 → same solution

proposal made for UML and YANG → on the agenda for approval 2021-07-28

All Attributes at all Notifications should be IsReadOnly==1

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28

objectClass of CurrentPerformace and HistoricalPerformance data type is not needed

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28

Object References in CurrentPerformance to be deleted

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28

Administrative and Operational State at CurrentPerformance

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28!

Object References in CurrentPerformance to be deleted

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28

Administrative and Operational State at CurrentPerformance

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28

object-class, name-binding, packages, allomorphs are present in UML for historical and current performances

duplicate of TDM Container #9 → closed.

All Attributes at all Notifications should be IsReadOnly==1

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28

objectClass of CurrentPerformace and HistoricalPerformance data type is not needed

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28

Object References in CurrentPerformance to be deleted

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28

Administrative and Operational State at CurrentPerformance

UML and YANG are already corrected - to be closed → on the agenda for approval 2021-07-28

@Alexander Wenk

@Prathiba

Current status:

• UML-to-yang - synch_Pac - to generate a yang
• create a workspace - with new - specify/augmentation to the core-model-1.4
• there is a need to create a "new" UML-project

First try to generate yang model-

• some manually modification
  • stereotype "experiment" - update of OpenModelProfile
  • then some issues found by pyang
    • duplicate of attributes - same attribute but different description
    • issue on a class which is not required - maybe we simply remove it from yang generation
    • feedback by Thorsten - UML/YANG header info missing

See feedback from Kam:

• https://github.com/openBackhaul/core/wiki/2021-06-22-Interface-call#synchronization-model

Info from 2021-07-06:

• Alexander is going to create issues based on the feedback by vendors

Pre- Discussion happened yesterday 

• info send by Thorsten on Monday 2021-05-17
• in addition Thorsten will send the "background discussion slide"....

Mediator Instance Manager 

• What is the protocol? NETCONF or REST or RESTCONF or ...
  • Working Assumption:  not decided
  • SIAE would like to decide based on efforts after analysis. 
  • UML include the "service" - but not the operational and maintenance layer
  • YAML (OpenAPI3) → UML (papyrus) → YANG → 

2021-05-25

• Any questions?
  • no questions

2021-06-16

• please see "App layer on top of the SDN controller" above.