| United States-English |
|
|
|
![]() |
HP XC System Software : Administration Guide > Chapter 1 HP XC Administration EnvironmentHP XC Configuration File Guidelines |
|
Configuration files tune the structure and the operation of the HP XC System Software. Some of these files configure Linux; some configure a third-party application, such as SLURM or Nagios; and some apply specifically to the HP XC System Software. While you can modify some configuration files to solve a site-specific issue, do not change other configuration files so that the integrity of the HP XC System Software is maintained. Typically, configuration files are modified during reconfiguration, that is, when the cluster_config utility is run, or during an rpm upgrade operation. This section describes how modifications to configuration files are treated during reconfiguration and upgrade operations. Linux configuration files pertain to the configuration of the operating system. ReconfigurationFor a system reconfiguration, the policy in effect is to preserve any customizing you have done to a Linux configuration file unless the change undermines the proper operation of the HP XC System Software. In that case, the HP XC System Software overwrites the configuration file and the changes you made are deleted. Some configuration parameters can be expressed in terms of a range. If you make a change to such a parameter and that change is within the operational range required by the HP XC System Software, the change to the configuration file is preserved. If the change is not within that range, the HP XC configuration application modifies the configuration file to adhere to the specified range. An example of a modification to a Linux configuration files that will not be preserved is any of the scripts in the /etc/sysconfig/network-scripts directory. An nconfigure script determines the device names to associate with the admin, internal, and external devices; any customization made to the device name configuration files are overwritten. Additions made to the Linux configuration files that are not fundamental to proper HP XC system operation are preserved during reconfiguration. Software UpgradeDuring a software upgrade, the HP XC System Software defers to the Linux rpm software, which has the responsibility for ensuring the preservation of any Linux configuration files you have customized. For more information, see rpm(8). Configuration files comprise the configuration files for the HP XC System Software and the configuration files for integrated third-party software For more information on these configuration files, see “HP XC Configuration Files”. ReconfigurationDuring reconfiguration, changes you made to all HP XC configuration files are preserved if you modified the data according to the procedures in the HP XC documentation set. For example, if you change the syslog-ng configuration information, (perhaps, filters or ports) you must modify both the syslog-ng.conf and the syslog-ng template files so that the changes persist after a reconfiguration. Software UpgradeDuring a software upgrade, customizations to the HP XC configuration files are preserved but might need to be merged back into the configuration files. HP XC preserves configuration files using standard RPM methods. The rpm upgrade process preserves customizations by saving a copy of the old or new configuration file with either the .rpmsave or .rpmnew suffix. To retain your changes, you must manually merge the saved customizations into the new configuration file as documented in the upgrade and patch documentation. Table 1-3 lists the configuration files for a given component alphabetically. It also provides a reference to the chapter in this document that references it. Table 1-3 HP XC Configuration Files
Client nodes receive their image from the HP XC system's golden master. Unless you either update the golden master or set an override file, the changes made locally to configuration files on the client nodes are lost the next time the node is re-imaged. For more information on the golden master and how to distribute software throughout the HP XC system, see Chapter 11. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||