Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2023-05-24 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-31: Martin Skorupski

2023-06-07: Martin Skorupski

2023-06-14: Martin Skorupski

2023-06-21: Martin Skorupski (o-ran f2f in osaka)

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)

LLDP -> related automatic link discovery


proposed official ONF TR532 2.1

Backup and Restore

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


Next Steps towards 2.0

  • UML (almost done)
  • YANG (to be updated and generated: revision 2023-06-?? including the core-model)
  • YANG Tests
  • init implementation and test with the current test functions
  • feedback from Implementation to UML/YANG and iterate
  • Creation of TR-532 v2.0
    • with references to UML - gendoc
    • with references to yang ?
    • creating the (word) documentation
00:15LTP Augment

Thorsten Heinze @Prathiba

new UML and yang created

  • yang mandatory statement
    • all augments must not be mandatory - of cause as augments are addons (also mentioned in RFC)
  • problems solved
  • discussion item
    • supportedLayerProtcolNames
    • issue created to remove supportedLayerProtcolNames
    • new UML to be provided
00:15LLDP

Thorsten Heinze @Prathiba

LLDP UML → YANG

  • system capabilities are represented as containers
    • bits vs attributes


Status "tracking"

  • missing when-statement for the augment for LLDP
    • should be similar to the LayerProtocolName

  • "ProtocolCollection" class to core-model-1-4

    • UML vs. PostProcessing /control-contruct/protocol-collection/protocol/lldp

    • protocol-collection and protocol are defined in EquipmentAugment

    • status: bug-free according to pyang

  • An LldpSpec class needs to be added

  • YANG defined a protocol-name-type-def better to use identify
    • Prathiba to check the process
    • first analysis: post-processing needs to be enhanced
    • will be 
00:xxUML2YANG@Prathiba

 require-instance

  • Sync #16  | Method for managing require-instance statements to found
  • VLAN-IF #28 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected
  • VLAN-FD #19 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected
  • VLAN-FC #6 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected

The mechanism is required for AttributeValueChange Notification and ObjectCreate Notification but not for ObjectDeletion Notification

@Prathiba is going to check for other cases

Thorsten Heinze : Is an issues required for all UMLs?


END of the meeting

00:00Issues@allhttps://github.com/openBackhaul/core/wiki/priority-of-issues
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