On Mon, 3 Jun 2019 13:50:55 +0200 Thorsten Kukuk wrote:
RPM has a really very simple configuration file
the config, move it away and write the new config or write the new
config in a different file (*.rpmsave and *.rpmnew).
If the rpm contains a configuration file marked as %config, and the
packager fixes a typo in a comment, RPM will move the by the admin
modified and adjusted configuration file away and put's the default
configuration file there, which means, your service will not work
until you merge the configuration files.
This is already bad, but it's getting really worse if you think about
atomic updates (transactional-updates on openSUSE):
- admin modifies configuration files
- admin starts an transactional update, the configuration file will
- admin makes changes to the configuration file
- admin reboots to active the changes
-> admin needs to find out which changes where done by whom and needs
to merge them all to get the service working again
While this shouldn't happen very often, more really seldom, if it
happens, it's really bad. Especially, if you think about big clusters
with many machines and not only a few workstations.
So I started looking into different solutions.
The first thing is: we are not alone with the problem, every
distribution with atomic updates has it, but every distribution has
their own solution. Which reminds me on the pre-FHS times, when you
had to learn for every distribution again where the configuration
files and other tools could be found.
So we need something, which helps everybody and is good enough
specified, that people will use this solution.