54
To manage the configuration of a system, it must have the latest
a config-enable created on it. Refer to Section 4.6.6.1 Preparing Systems for Config Management
for instructions.
These tools may already be installed on your system, especially if you kickstarted the system with
configuration management functionality. If not, they can be found within the RHN Provisioning
child channel for your distribution. Download and install the latest
refer to Section 4.6.6.1 Preparing Systems for Config Management for instructions on preparing
the target system.
You must place a config-enable file on the system to have config actions scheduled. This file
is required to allow configuration management on the system while preventing inadvertent and
potentially dangerous changes. To create this file, issue the following commands as root. First,
create the necessary directory:
mkdir -p /etc/sysconfig/rhn/allowed-actions/configfiles
Then, you should decide exactly what actions should be allowed by system administrators. The
following modes are available:
deploy — Install configuration files from the central repository on the system. Without this
•
set, the configuration management interface provides no real value for this system.
verify — Identify any differences between configuration files on the system and those associ-
•
ated with it in the central repository.
diff — Display differences between configuration files on the system and those associated
•
with it in the central repository.
upload — Send any files from the system to the central repository. This is similar to granting
•
root privileges on the machine.
mtime_upload — Send files modified since a certain date and time from the system to the
•
central repository.
all — Enable all of these modes for configuration management on the system.
•
To set individual modes, issue this command (repeatedly, as root), appending the mode name to
the end:
touch /etc/sysconfig/rhn/allowed-actions/configfiles/mode
To grant full configuration management access, issue this command:
touch /etc/sysconfig/rhn/allowed-actions/configfiles/all
Your system should now be ready for config management through RHN. The central configura-
tion repository is covered more extensively in Section 4.6.6 Manage Config Channels. Command
line options also exist for many of these functions. Refer to Appendix A Command Line Config
Management Tools for instructions. Here are the system's Configuration subtabs:
Managed Files — List all configuration files currently associated with the system.
•
Verify — Validate the configuration files installed on the system by comparing them to ver-
•
sions stored in RHN's central configuration manager. Select the files to be verified and click
Verify.
Config Channels — Set the subscription and rank of configuration channels that may be as-
•
sociated with the system. Enter numbers in the Rank fields to establish the order in which
channels are used. Channels with no numeric value are not associated with the system. Your
local configuration channel will always override all other channels for this system and there-
fore cannot have its rank adjusted from 1. All other channels are created in the Manage Con-
fig Channels interface within the Channels category. Refer to Section 4.6.6 Manage Config
Channels for instructions. When satisfied, click Update.
Local Overrides — View and manage the default configuration files for the system. If no files
•
exist, click the add, edit, or remove files link within the description to access the system's
Config Channel Files page. If a file exists, click its name to go to the Configuration File
Chapter 4. Red Hat Network Website
packages installed and
rhncfg*
rhncfg*
packages. Then
Need help?
Do you have a question about the NETWORK 3.4 - PROVISIONING and is the answer not in the manual?
Questions and answers