Configuration Management for Salt
This matrix shows supported and unsupported configuration management features.
Several Web UI tabs will be missing for Salt Configuration Management. These features are not suitable for Salt clients. |
Configuration Management Features | Salt Support Status |
---|---|
Global Configuration Channels |
Supported |
Deploying Files |
Supported |
Comparing Files |
Supported (but the logic is currently inverted) |
Locally Managed Files |
Unsupported |
Sandbox Files |
Unsupported |
Applying the Highstate |
Apply the highstate and configuration channels will be deployed to all subscribed systems. |
File Import from a Client |
Unsupported |
Configuration Macros |
Unsupported |
Prepare Systems for Configuration Management [Management]
To manage traditional client configuration with Uyuni, the client must have the appropriate tools and the config-enable
file installed.
These tools will be available if you installed the system with the configuration management functionality using AutoYaST or Kickstart.
If not, they can be found in the Tools child channel for your distribution.
Download and install the latest mgr-cfg*
packages:
-
mgr-cfg
— the base libraries and functions needed by allmgr-cfg-*
packages, -
mgr-cfg-actions
— the RPM package required to run configuration actions scheduled via Uyuni, -
mgr-cfg-client
— the RPM package with a command line interface to the client features of the Configuration Management system, -
mgr-cfg-management
— the RPM package with a command line interface used to manage Uyuni configuration.
Installation of these packages can also be accomplished during bootstrapping if you enable Configuration File Deployment
on the Details
page of the activation key after creating that activation key.
For more information about activation keys, see
reference:systems/activation-keys.adoc#s3-sm-system-keys-manage.
Create Configuration Channels
To create a new central configuration channel:
-
In the Uyuni Web UI, navigate to
, and click Create Config Channel. -
Enter a name for the channel.
-
Enter a label for the channel. This field must contain only letters, numbers, hyphens (
-
) and underscores (_
). -
Enter a mandatory description for the channel that allows you to distinguish it from other channels.
-
Click the Create Config Channel button to create the new channel.
-
The following page is a subset of the
Channel Details
page and has three tabs:Overview
,Add Files
, andSystems
. TheChannel Details
page is discussed in [config-config-channels-channel-details].
To create a new state channel with an init.sls
file:
-
In the Uyuni Web UI, navigate to
, and click Create State Channel. -
Enter a name for the channel.
-
Enter a label for the channel. This field must contain only letters, numbers, hyphens (
-
) and underscores (_
). -
Enter a mandatory description for the channel that allows you to distinguish it from other channels.
-
Enter the
SLS Contents
for theinit.sls
file. -
Click the Create Config Channel button to create the new channel.
-
The following page is a subset of the
Channel Details
page and has four tabs:Overview
,List/Remove Files
,Add Files
, andSystems
. TheChannel Details
page is discussed in [config-config-channels-channel-details].
Add Configuration Files, Directories, or Symbolic Links
After you have created a configuration channel you can add a configuration file, directory, or symbolic link:
-
In the Uyuni Web UI, navigate to
, and click the name of the configuration channel where you want to add a configuration file. -
Navigate to
subtab, and in theFile Type
section choose whether you want to create a text file, directory, or symbolic link. -
In the
Filename/Path
text box, set the absolute path to where the file should be deployed. -
If you are creating a symbolic link, indicate the target file and path in the
Symbolic Link Target Filename/Path
text box. -
Enter the
User name
andGroup name
for the file in theOwnership
section, and theFile Permissions Mode
. -
If the client has SELinux enabled, you can configure
SELinux contexts
to enable the required file attributes (such as user, role, and file type). -
If the configuration file includes a macro, enter the symbol that marks the beginning and end of the macro.
-
Enter the configuration file content in the
File Contents
text box, using the script drop-down box to choose the appropriate scripting language. -
Confirm with clicking the Create Configuration File button.