search

openBackhaul / core

Core Information Model that consolidates all technology specific extension
Apache License 2.0
1 stars 0 forks source link

Firmware Release and Licenses might influence Interface Capabilities #15

Open openBackhaul opened 4 years ago

openBackhaul commented 4 years ago

Currently, the characteristics expressed by the attributes at the ManufacturedThing class of the Core IM are the base for deciding, which Capability attributes to attach to a new instance of an LTP.

This expresses the dependency also to the hardware release.

Dependencies between interface Capabilities and firmware release or licenses are not documented.

Proposal 1 Currently, there is a 0..1 association from ExpectedEquipment and ActualEquipment classes to ManufacturedThing class. It is proposed to change this towards a * association and document firmware as well as licenses also as instances of the ManufacturedThing class. The device would then have to regard all instances of ManufacturedThing for choosing the correct set of Capability values, while instancing the LTP.

Proposal 1.1 In the plan-build-operate process, the operator has to decide, whether to document firmware and licenses.

Proposal 1.2 While plugging a new hardware component, ActualEquipment is instantiated including ManufacturedThing instances for hardware, firmware and licenses. If there would be differences between ActualEquipment and ExpectedEquipment, the new hardware component would not become operational.

Proposal 1.1.1 If there would be no instances of ManufacturedThing for firmware and licenses at the ExpectedEquipment, status of firmware and licenses would not be regarded for deriving the operational status.

demx8as6 commented 2 years ago

Moved to version 3.0 - on_hold.