Feature #1601
closed
VTY parameters become active when?
Added by laforge about 8 years ago.
Updated over 3 years ago.
Description
Document which VTY parameters become active immediately, and which require an OML re-start of the BTS.
Maybe we can even improve this to a point where we can apply OML changes to a BTS without a full re-connect, so that we don't lose all current users.
Alternatively introduce a way where we can schedule a BTS re-start as soon as all active transactions are finished.
It might make sense if the information on 'when a change becomes active' was somehow explicit when using the VTY.
- Related to Bug #77: Fix/Define when VTY changes take effect added
- Assignee set to wirelesss
- Priority changed from Low to Normal
- Description updated (diff)
- Status changed from New to In Progress
- % Done changed from 0 to 10
- Assignee deleted (
wirelesss)
- Project changed from OsmoNITB to OsmoBSC
- Status changed from In Progress to New
- Assignee set to Hoernchen
- Status changed from New to In Progress
- Assignee changed from Hoernchen to fixeria
- Assignee changed from fixeria to dexter
- % Done changed from 10 to 90
Status update:
All VTY commands in the osmocom applications that are related to the ran (osmo-bts, osmo-trx, osmo-pcu, osmo-bsc, osmo-mgw, libosmo-sccp, libosmo-abis) are reviewed and tagged with appropriate attributes. The attributes tell the user (and the scripts that generate the VTY reference manuals) when a configuration change takes effect. Also the work on the infrastructure (vty commands to display the attributes / xml generation) is done.
- % Done changed from 90 to 100
- Status changed from In Progress to Resolved
Also available in: Atom
PDF
