We developed a software tool to cope with this synchronization. It is based on a central database containing the needed information about our backbone caches and about some additional caches at the university level, which are cooperating with our system. Because there are some aspects depending on local conditions, we decided to divide configuration into two parts. Other commands are moved to the local part. Configuration management scheme Figure 4 depicts the creation of configuration.
Central manager modifies the database and runs the master program.
The configuration is activated off-line. Configuration changes are usually not very dramatic and time distance between them is in range of weeks. It means that the activation is not time-critical. If so, it makes backup of the running configuration, merges the submitted part with the local one and activates the result. But the operation is still not consolidated to provide significant statistical data.