Red Hat NETWORK 3.2 - PROVISIONING Reference Manual

Also see for NETWORK 3.2 - PROVISIONING: Reference guide

Contents

52 Chapter 4. Red Hat Network Websitefrom the profile. To install specific packages, select the checkboxes of packages from the pro-file. To remove specific packages already installed on the system itself, select the checkboxes ofpackages showing a difference of "This system only." To synchronize the system’s packages withthe compared profile entirely, select the master checkbox at the top of the column. Then click theSync Packages to button. On the confirmation screen, review the changes, select a timeline forthe action, and click the Schedule Sync button.• Channels — Manage the channels associated with the system.• Software — Provides a predetermined method for systems to obtain regular updates, based upontheir operating systems, packages and, functionality. Click a channel name to view its ChannelDetails page. To modify the child channels associated with this system, use the checkboxes nextto the channels and click the Change Subscriptions button. You will receive a success messageor be notified of any errors. To change the system’s base channel, select the new one from thepulldown menu and click the Modify Base Channel button. Refer to Section 4.6.1 SoftwareChannels for more information.• Configuration — Assists in managing the configuration of the system. Like software channels,configuration channels store files to be installed on systems. Unlike software packages, variousversions of configuration files may prove useful to a system at any given time. In addition, thesetools provide the means to manage what systems allow remote commands to be run on themthrough the RHN website. For this reason, the tools needed to manage these files must be morerobust.These tools may already be installed on your system, especially if you kickstarted the system withconfiguration management functionality. If not, they can be found within the RHN Provisioningchild channel for your distribution. Download and install the latest rhncfg* packages.To allow remote commands to be run on the client through RHN, first create the necessary direc-tory:mkdir -p /etc/sysconfig/rhn/allowed-actions/scriptThen create a run file in that directory to act as a flag to RHN signaling permission has beengranted to allow remote commands:touch /etc/sysconfig/rhn/allowed-actions/script/runNext, you must place a config-enable file on the system to have config actions scheduled. Thisfile is required to allow configuration management on the system while preventing inadvertentand 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/configfilesThen, you should decide exactly what actions should be allowed by system administrators. Thefollowing modes are available:• deploy — Install configuration files from the central repository on the system. Without thisset, 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 associatedwith it in the central repository.• upload — Send any files from the system to the central repository. This is similar to grantingroot privileges on the machine.• mtime_upload — Send files modified since a certain date and time from the system to thecentral repository.• all — Enable all of these modes for configuration management on the system.