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

2023-06-21: Thorsten Heinze supported by Alex Stancu (o-ran f2f in osaka; Martin Skorupski on b-trip)

2023-06-28: Martin Skorupski

2023-07-05: Martin Skorupski

00:05UML2YANG@Prathiba

 require-instance

  • Sync #16  | Method for managing require-instance statements to found → Proposal made - TR531 already describes the mechanism 
  • VLAN-IF #28 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected - proposal made - to be rejected
  • VLAN-FD #19 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected - proposal made - to be rejected
  • VLAN-FC #6 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected - proposal made - to be rejected

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?

The stereotype Lifecycle Aggregate Association should be added to all shared Association for AttributeValueChange Notification and ObjectCreate Notification.   

In RPCs all references should be tagged with require-instance==false (as today - no change)


The statement above

  • the mechanism is required for AttributeValueChange Notification and ObjectCreate Notification, ...

should be reverted. Reason is that the asynchrous implementation of the NETCONF server can not guarantee the exactions of an instance. This will simplify the implementation.

As a consequence all open issues in this regard can be "rejected" as there is no change in UML and UML2YANG needed. 

All leafrefs will be tagged with "required-instance = false". 

INFO: to be approved next week

00:08hybridMwStructure #29Roberto Servadio 

https://github.com/openBackhaul/hybridMwStructure/issues/29 → proposal made

INFO: to be approved next week

00:10UML/YANG tracking@Prathibaupdates for tracking
- https://github.com/openBackhaul/core/wiki/summary-of-issues
00:20Instance Manager@Senthilvel

Status information missing in the Instance Manager

  • state info should be added
  • operational state could be added (up/down/connected) → similar to the controller configuration state
    • API change
    • integration into implementation
      • call-back - includes also a kind of health-check of the instance itself
  • the instance manager does not have such info but it needs to go to upper level
  • info should indicate the connectivity between MediatorInstance and device
  • should be handled by an issue in the https://github.com/openBackhaul/ApplicationPattern


  • in addition a "start/stop/reset" operation - reconnection attempt - second issue!
    • stop is already covered by create/remove?!?!??! to be thought about

END of the meeting

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