| 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 |
Invited:
- Andrea Delmonte
- @Andreas Lattoch
- @Alexander Wenk
- Daniela Spreafico
- Daniel Perez Calvo
- Danilo Pala
- Eduardo Yusta
- Hubing
- Hsudarsa
- Jorge Lopez
- Istvan Vencz
- Jasper Yang
- Leo
- Ma Yong
- Michael Binder
- Nader Zein
- Paul Parva
- Pawel Krecicki
- Petr Jurcik
- Prathiba Jeevan
- Roberto Servadio
- Senthilvel
- Shuzhan
- Thomas Seitz
- Thomas Schulze
- Tian Zhu
- Thorsten Heinze
- Yossi
- Zhang Dong
(please feel free to correct and update your names 
Thank you very much!!!)
Info to:
Goals
- going forward
Mailings
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 00:00 | Chair topic | no update | |
00:01 | Admin | 2023-06-07: Martin Skorupski 2023-06-14: Martin Skorupski 2023-06-21: Martin Skorupski (o-ran f2f in osaka) 2023-06-28: Martin Skorupski | |
| 00:01 | CoreModel | @Prathiba | https://github.com/openBackhaul/core/issues/14 is obsolete and was closed |
| 00:05 | UML2YANG | @Prathiba | require-instance
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
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". |
| 00:30 | Modelling Roadmap | all, Nader Zein | latest version in wiki: Q: timeline? Modelling Roadmapupdate 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
|
| 00:45 | hybridMwStructure #29 | Roberto Servadio | https://github.com/openBackhaul/hybridMwStructure/issues/29 → proposal made |
| 00:55 | Instance Manager | @Senthilvel | Status information missing in the Instance Manager |
| END of the meeting | |||
| 00:00 | Issues | @all | https://github.com/openBackhaul/core/wiki/priority-of-issues |
| 00:00 | Backup 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
Overview
Content Tools
Activity