Proper OML MO (managed object) using osmo_fsm
The BTS side of the TS 12.21 managed objects is a big hack. Having proper finite state machines as outlined in TS 12.21 for each MO would be a great win.
Updated by pespin over 1 year ago
- Status changed from In Progress to Feedback
- Priority changed from Low to High
- % Done changed from 10 to 90
Initial set of patches adding initial OMl FSMs in osmo-bts can be found here:
https://gerrit.osmocom.org/c/osmo-bts/+/20407 Change NM Channel availability Dependency->Offline when RadioCarrier becomes ...
https://gerrit.osmocom.org/c/osmo-bts/+/20408 Introduce NM BTS Site Manager FSM
https://gerrit.osmocom.org/c/osmo-bts/+/20409 Introduce NM BTS FSM
https://gerrit.osmocom.org/c/osmo-bts/+/20284 Introduce NM Radio Carrier and Baseband Transceiver FSMs
https://gerrit.osmocom.org/c/osmo-bts/+/20311 Introduce NM Channel FSM
PS: I changed the priority of the ticket since current status (before FSM) actually affects sysmobts not working properly after some osmo-bsc OML fixes (for in turn osmo-bts-trx OML issues) a few days ago.
Once those patches above are merged, we can close the ticket and keep going with the multiple smaller tickets pointing at specific issues.
Updated by pespin about 1 year ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100
I just submitted a small fix making TS not enabled under some situations (RSL link up quite late):
https://gerrit.osmocom.org/c/osmo-bts/+/20824 bts_trx.c: Dispatch missing NM_EV_RSL_UP/DOWN to the bb_transc object