| 3am PST | 6am EST | 10:00 UTC | 10:00 GMT | 11:00 CET | 12:00 EET | 15:30 IST | 18:00 CST | 19:00 JST |
(please feel free to correct and update your names Thank you very much!!!)
Mailings
Time | Item | Who | Notes |
---|---|---|---|
00:00 | Chair topic | no update | |
00:01 | Admin | 2023-01-18: Martin Skorupski 2023-01-25: Martin Skorupski 2023-02-01: Martin Skorupski 2023-02-09: Martin Skorupski | |
00:05 | AirInterfaceConfiguration/polarization | Martin Skorupski | polarization attribute is removed from 2.0 - why?
Such documentation could be done in the "air-interface-name" |
00:05 | Core #31 | Thorsten Heinze | Generic grouping of attributes, which can just be configured together /sko/ The discussion was related to schedulerProfile which was solved on be individual RPCs. I still like the idea and concept behind but propose to postpone the issue until TR532 3.0 (on hold?) |
00:10 | Sync #16 | Thorsten Heinze | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected /sko/ This is just a reminder for the future. For TR532 2.0 a manual fix is available - the issue should be postponed until TR532 3.0. (on hold?) |
00:10 | VLAN interface #28 | Thorsten Heinze | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected /sko/ This is just a reminder for the future. For TR532 2.0 a manual fix is available - the issue should be postponed until TR532 3.0. (on hold?) |
00:15 | VLAN FC #6 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected /sko/ same solution as for VLAN interface #28 (on hold?) | |
00:45 | Sync #15 | Method for managing mandatory statements to found
| |
00:45 | VLAN FC #5 | Thorsten Heinze | RPC operation parameters should be mandatory / This issue is just for documenting that the VlanFc model is also affected.
|
00:45 | VlanFd #20 | mandatory==true at _objectIdRef attributes inside notifications manually corrected
| |
00:25 | LTP Augment #6 | label information at LTP to be harmonized with Holder /sko/ What is the status of UML/YANG today? - how to proceed? → proposal made for Feb1 | |
END OF MEETING | |||
00:30 | LTP Augment #5 | Thorsten Heinze | Original LTP name as a dedicated attribute |
00:55 | Issues | @all | https://github.com/openBackhaul/core/wiki/priority-of-issues |
00:00 | 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) 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: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 |