Feature #1670
closedFeature #1668: NAT: Scalable configuration management
NAT: Re-load BSC configuration file
0%
Description
Given the previous (#1668) it is important that there is a way to re-load the BSC configuration file at runtime leading to:
- New BSCs added (trivial)
- Change of token should re-set existing BSC connection and calls should drop
- Old BSC configurations remove and the associated BSC connection and calls dropped
The easiest might be to set a flag on each bsc_cfg before loading the bscs-cfg-file, reset it if the BSC cfg has been touched and if not remove it.
Updated by msuraev about 8 years ago
- Status changed from New to Feedback
What should we do with bsc which were configured using vty and not included configuration file?
Updated by zecke about 8 years ago
ms wrote:
What should we do with bsc which were configured using vty and not included configuration file?
That is no concern. They will then be removed on reload and we can deal with it.
Updated by msuraev about 8 years ago
What needs to be done to make sure all calls are dropped - is calling bsc_close_connection() enough for that?
What's the right way to reset bsc connection - do we have to send particular message or just closing and allocating it again is ok?
Updated by zecke about 8 years ago
Yes, bsc_close_connection() is enough, no need to call reset. The connection will close immediately and you will need to use llist_for_each_entry_safe as the connection will go away while you close it.
Updated by msuraev about 8 years ago
- Status changed from Feedback to In Progress
- Remove the requirement to assign BSCs in order
- Change bsc_config_alloc to include the nr to be assigned
- change cfg_bsc_mcd to first search the given BSC and then create one
Updated by msuraev about 8 years ago
- Status changed from In Progress to Feedback
- Assignee changed from msuraev to zecke
Updated by zecke over 7 years ago
- Status changed from Feedback to Closed
Merged with 4936448761a6ca42ab661d130f5202dfdabca426
