Skip to end of metadata
Go to start of metadata

 | 2am PDT | 5am EDT | 09:00 UTC | 10:00 BST | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |


Web Conference:

https://thorsten-heinze-telefonica-de.webex.com/thorsten-heinze-telefonica-de/j.php?MTID=m849236edb092dffd10071725f5b8839f 

Invited:

(please feel free to correct and update your names (wink) Thank you very much!!!) 

Discussion items

TimeItemWhoNotes
00:00chair topic 
no update 

00:05

Admin

Next meetings

2021-07-21: Martin Skorupski

2021-07-28: Martin Skorupski

2021-08-04: Martin Skorupski

2021-08-11: Martin Skorupski

00:05Continue working on issuesThorsten HeinzeEntry point: https://github.com/openBackhaul/core/wiki/summary-of-issues
00:08Hybrid MW Structure #23

supportedAlarmList to get DefaultValue and *

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

00:10Pure Ethernet Structure #20

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

00:11TDM Container #14

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

00:18WireInterface #33

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

00:27Pure Ethernet Structure #14

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

00:32Pure Ethernet Structure #15

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

00:34Pure Ethernet Structure #16

Object References in CurrentPerformance to be deleted

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

00:38Pure Ethernet Structure #17

Administrative and Operational State at CurrentPerformance

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

00:42TDM Container #9

Object References in CurrentPerformance to be deleted

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

00:43TDM Container #10

Administrative and Operational State at CurrentPerformance

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

00:44TDM Container #11

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

duplicate of TDM Container #9 → closed.

00:48WireInterface #20

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

00:52WireInterface #21

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

00:53WireInterface #22

Object References in CurrentPerformance to be deleted

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

00:57WireInterface #23

Administrative and Operational State at CurrentPerformance

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


End of the meeting





00:15Synchronization

@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:

Info from 2021-07-06:

  • Alexander is going to create issues based on the feedback by vendors
00:00Mediator Instance Manager

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.

Action items