| 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 |
(please feel free to correct and update your names Thank you very much!!!)
|00:00||Chair topic||no update|
|00:01||CoreModel||@Prathiba||https://github.com/openBackhaul/core/issues/14 is obsolete and was closed|
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".
all, Nader Zein
latest version in wiki:
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
proposed official ONF TR532 3.0
Target: start ONF review mid of November 2022 for TR532 2.0
zip file with folder structure
|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||Backup and Restore||@Senthilvel|
Requirements from TEF:
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
Note: Mediator Instance Manager backup-and-restore functions are covered by app and cloud functions