Conceptual question on configuration management
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
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
El dt. 09 de 02 de 2021 a les 14:11 +0100, en/na Martin Willisegger va
escriure:
Hello Martin,
Uyuni is also a Salt Master as the Salt configuration management stack
is integrated in it.
Salt has several components, one of them is called "pillar", it can do
exactly what you are asking. Have a look at:
https://docs.saltproject.io/en/latest/topics/tutorials/pillar.html
After you have pillar values declared, you can reference them from
states that will apply configuration (highstate) to your systems.
https://docs.saltproject.io/en/latest/topics/tutorials/starting_states.html
https://docs.saltproject.io/en/latest/ref/states/highstate.html
Templating is very useful, by using jinja in your states you can
consume your key-value pairs to fill configuration declarations:
https://docs.saltproject.io/en/latest/topics/jinja/index.html
At last you can assign these states to all systems or to systems that
belongs to some group or on individual systems.
These are my two cents, hope this helps you.
regards,
Jordi Bruguera
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
participants (3)
-
Jordi Bruguera i Cortada | Prisco Electronica
-
Martin Willisegger
-
Strahil Nikolov