Re: Conceptual question on configuration management

SALT is your best friend. You can use pillars, grains or just jinja2 format for your salt states. Best Regards,Strahil Nikolov On Tue, Feb 9, 2021 at 15:11, Martin Willisegger wrote: Hello List Suppose I were to manage 100 servers with Uyuni and had to roll out a system configuration that looked like this: parameterA=value1 parameterB=value2 parameterC=value3 parameterD=value4 On most servers it would look the same, but some servers would need e.g. parameterB=value5 parameterD=value6 Other servers would need an additional line: parameterE=value7 And other servers would not need a single parameter #parameterA=value1 Can this requirement be easily managed and clearly displayed via Uyuni's configuration management, and can it be adapted at any time for further requirements or omitted exceptions? Would it only work with fully supported clients (SLES), or also with openSuSE/Uyuni clients via salt? Best regards Martin