| 6am PST | 6am EST | 10:00 UTC | 11:00 CET | 12:00 EET | 15:30 IST | 18:00 CST | 19:00 JST |
https://thorsten-heinze-telefonica-de.webex.com/join/andreas.lattoch.external
(please feel free to correct and update your names Thank you very much!!!)
Time | Item | Who | Notes |
---|---|---|---|
00:00 | chair topic | no update | |
00:00 | Admin | Next meetings 2020-12-02: Thorsten Heinze 2020-12-09: Martin Skorupski 2020-12-16: Thorsten Heinze(@Alex Stancu for meeting minutes) 2020-12-23: Thorsten Heinze(@Alex Stancu for meeting minutes) 2020-12-30: ??? 2020-01-06: canceled 2020-01-13: Martin Skorupski | |
00:05 | INFO: Demo Day | 2020-12-03 16:00 CET- 18:00 CET Joint PoC "Proof of Concept" O-RAN/OSC/ONAP
| |
00:10 | In VlanInterface historical-performance-data attribute name to be corrected | The following issue incl. proposal has been introduced https://github.com/openBackhaul/vlanInterface/issues/24. Decision has been scheduled for 9th of December. | |
00:15 | Firmware | @Eduardo Yusta | Eduardo explained his proposal about how to describe firmware (https://groups.google.com/a/opennetworking.org/g/wireless-transport/c/3BJHnPa5PRU) and addressed a couple of questions to the vendors. Vendors gave details about their implementations. Thorsten explained two different ways of modeling Eduardo's proposal. AP Thorsten Heinze: List attributes in Excel and send Excel to vendors to mark supported attributes. (done) AP all vendors: Respond until Monday e.o.b. so discussion about way of modelling can be continued on Tuesday 8th of December Working assumption
|
End of the meeting Discussions to be continued: | |||
00:00 | VLAN FC creation | Thorsten Heinze | Creation of objects S1 use case
new proposal by SIAE: In order to provide to the application the "next" uuid an option could be the following: 1) Add in the model in the section "status" the "next-uuid" parameter 2) In case this "next-uuid" is influenced by some value: add in the section "configuration" the corresponding "influencer" values i.e. with reference to the VLAN creation, in VlanFd we could have something like: - In section "configuration": "next-vlan-fc-vlan-id" - In section "status": "next-vlan-fc-uuid" |
00:00 | Issues in General | INFO: https://github.com/openBackhaul/core/wiki/summary-of-issues | |
00:00 | Firmware | @Eduardo Yusta | Use case discussion challenging the model proposal: Please see updated slides (thanks Eduardo). Feedback from vendors:
Firmware inventory
Firmware operations
|
00:00 | Reboot | As a result of the discussion about Firmware, their might be a need for a "restart" trigger. The "software activation trigger" usually also leads to a "restart" but with new software, which a "restart" reboots using the currently running software. Other terms for the same? or similar? function:
Questions:
General reboot
| |
@Eduardo Yusta | License Management | Questions:
First proposal:
2020-11-18
| |
00:00 | PureEthernetStructure, HybridMwStructure | Daniela Spreafico | Please see email_ Please see related issues:
Please confirm by email to Martin Skorupski by end of this week (Nov6) that keeping FM and PM for xyzStructure is ok? Status: positive feedback to keep it as it is: Decision: we keep xyzStructure as they are and close the issues above. |
00:00 | Centralize RMON counters | RMON counter
Update: Support is welcome to consolidate with respect to RMON | |
00:00 | Layering discussion (FCs, FDs etc.) | Thorsten Heinze |
Agenda: 2020-09-30 Discussion and agreement about the following proposal: Discussion The following aspects are proposed to be decided by the 5G-xhaul subproject. - The ForwardingDomain shall be interpreted as a Potential for Forwarding (e.g. SDH Matrix). [sko] Potential: something which allows the creation of “forwarding” based in the FD:LTP - The ForwardingConstruct shall be interpreted as an Actual Forwarding (e.g. Connection between two VC-12 endpoints at the SDH Matrix). [sko] Actual: configured Forwarding – check operational states and traffic flow - There might be 0 .. * ForwardingConstructs inside a ForwardingDomain. [sko] ok Discussion on dependencies between LTPs, FD, FC and between the layers will continue... Agenda: 2020-10-07
|