Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2023-04-26 5G-xHaul Meeting notes
Skip to end of metadata
Go to start of metadata

  +  ? | 3am PDT | 6am EDT | 9:00 UTC | 10:00 BST | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |


Web Conference:

Conference Call Link by Telefonica 

Invited:

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

Info to: 

Goals

  • going forward


Mailings

Discussion items

TimeItemWhoNotes
00:00Chair topic 
no update 

00:01

Admin

2023-05-03: Martin Skorupski

2023-05-10: Martin Skorupski

2023-05-17: Martin Skorupski

2023-05-24: Martin Skorupski

00:04EthernetContainerFD #2@all

 Supporting EthernetContainerFc Creation with proper UUID

  • approved as proposed
00:05QoS Profile #10@all

Wrong index in ingress-ip-dscp-to-per-hop-behavior-mapping-list

  • approved as proposed
00:06QoS Profile #13@all

QOS profile configuration: ingress list key parameter

  • approved as proposed
00:07LLDP 

@Eduardo Yusta 
Roberto Servadio 

Next Steps:

  • Create UML and then use UML2YANG tool to generate an augmentation yang to core-model-1-4:control-construct.
    • takes time ....
    • sources for the document are existing

Copyright/License

  • Nader contacted IEEE chairs/representative - waiting for response

UML2YANG tool

  • Function to be checked for the reference statement and its translation
00:30UML2YANG@Prathiba

Multiplicity 

2.0 | Sync #15 | Method for managing mandatory statements to found | addressed | check with P

2.0 | VLAN Fc #5 | RPC operation parameters should be mandatory | check with P

2.0 | VLAN FD #20| mandatory==true at _objectIdRef attributes inside notifications manually corrected | check with P


END of the meeting

00:00Issues@allhttps://github.com/openBackhaul/core/wiki/priority-of-issues
00:00Modelling Roadmap

all, Nader Zein 

latest version in wiki:
Q: timeline?

Modelling Roadmap

update sequence to pre-MW-2.0-yangs

all currently implemented pre-TR532 2.0 -> PACs (existing today, including RMON, PM)

Sync and the updates of the CoreModel 1.4 yang (target to be available as YANG in 2022-10)

Centralized Alarm List (available now)

Mediator Instance Manager (available now) (REST for Mediators not for devices) (reusable component to be prepared)

based on the ApplicationPattern

proposed official ONF TR532 2.0

Sync and the updates of the CoreModel 1.4 yang

Centralized Alarm List - needs to be in 2.0 because it has impact on all PACs

Equipment Augment Module

all currently implemented pre-TR532 2.0 -> PACs

Mediator Instance Manager (REST)

proposed official ONF TR532 2.1

Backup and Restore

LLDP -> related automatic link discovery

SVLAN

proposed official ONF TR532 3.0

CoreModel 1.6

NMDA alternative

Target: start ONF review mid of November 2022 for TR532 2.0

zip file with folder structure

top-level document 

gendoc

uml

yang


00:00Backup and Restore@Senthilvel 

Requirements from TEF:

https://github.com/openBackhaul/firmware/blob/tsp/BackUpAndRestore/BackUpAndRestoreRequirements.md

Comments could be addressed by adding issues in GitHub.

Backup and Restore Operations

backup configuration to FTP server

restore configuration from FTP server AND activate

abord operation individual for backup and restore

rollback to previous configuration stored in the device

applyRestoreOperation

Note: Mediator Instance Manager backup-and-restore functions are covered by app and cloud functions

status

backupOperationStatus

restoreOperationStatus

Action items