(please feel free to correct and update your names Thank you very much!!!)
|00:00||chair topic||no update|
|End of the meeting|
Discussions to be continued:
|00:05||FC VLAN Creation|
RPC for FD:VLAN-FC creation
now the FC:uuid is known to all application.
The FC has no FCports at this point in time.
Continue the discussion on 2020-10-21
YANG provided by email and openBackhaul (link)
new: RPC at the end - please check!!!
renamed: "llc-address" to "llc-address-list"
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.
Continuing the discussion about firmware. NEC provided input and it was consolidated in the proposal.
How to activate a software package: leaf or RPC?
Discussions still needed, RPC is preferred, need to see how to model and how to integrate in our processes (Papyrus, UML2YANG etc.)
Alex Stancu to provide example from O-RAN FH model about how it is done in o-ran-software-management; then we can assess how we can adapt it to our needs.
SIAE is checking if RPC is feasible; Nokia will also do some checking. → maybe RPCs will be useful in other situations as well, we need to see
Do we need also a Download RPC? Probably. But this could be considered outside of the package model, does not really influence the inventory part.
Is ImageName (string) and ImageVersion (string) combination enough for uniquely identify a software image?
ImageSize proposed to be eliminated. No objections.
ImageClass - need tot see what happens if the case vendors do not support it; same for ImageIdentifier
ImageComparison proposed to be eliminated. No objections.
Need further discussions.
Parameter (status report and further discussion)
Package and Image class should inherit from GlobalClass - same as for Profile
UML for Firmware
Firmware model as on conditional package for Controlconstruct