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

 | 2am PST | 5am EST | 09: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

2022-09-28: Martin Skorupski (Thorsten ooo)

2022-10-05: Martin Skorupski

2022-10-12: Martin Skorupski

2022-10-17: Martin Skorupski


Approval session

00:05

Sync #23 (left over from Sep7)

@all

IEEE 1588 default profile missing

approved as proposed

00:08Sync #26@all

Inconsistent definition of "switch-type" LOCK_OUT

closed

00:11Sync #27@all

destinationMacAddress to be detailed 

approved as proposed

00:14Sync #33@all

priority attribute

approved after small modification of the proposal

00:17Core #20@all

Need to include configuration-and-switch-control grouping to support sync-model

approved as proposed


Working session

00:30

Equipment #24

Alex Stancu 

Statement about Technology specific operationalState attributes to be double checked | Create a proposal and go for it.

proposal made for 5th of October

00:40

Equipment #22

Martin Skorupski 

Wrong class diagram in TransmitterEquipment specification | Create a proposal and go for it.

proposal made for 5th of October

00:50

Equipment #18


Sequence-id examples as annex to TransmitterEquipment document | Create a proposal and go for it.

proposal made for 5th of October ( Thomas Seitz should be part of the decision)

00:55Issues@alllooking to the next 10 issues for next week
https://github.com/openBackhaul/core/wiki/priority-of-issues
01:05Feedback from Event last weekThorsten Heinze 

Focus on Implementation

  • Thursday call to be cancelled 

END OF THE MEETING


Equipment #12


Name of the Vendor | | Create a proposal and go for it - see also comment

Equipment #11


Expansion towards a general Equipment specification | Create a proposal and go for it.

Equipment #10


Empty occupying-fru - WireEquipment | bug -> Prathiba should have a look, if the situation can be solved by UML2YANG.

Equipment #9 


UUID | see comments

Equipment #8


Root instantiation | go with the proposal
00:05Modelling 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@Sentival 

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