| United States-English |
|
|
|
![]() |
HP XC System Software : Administration Guide > Chapter 1 HP XC Administration EnvironmentUnderstanding and Maintaining the File System |
|
The proper maintenance of the file system is crucial to the operation of the HP XC system. This section offers guidelines for the maintenance of the file system and describes key directories. Figure 1-2 illustrates the top of the file system hierarchy for an HP XC system. The basic file system layout is the same as that of the Red Hat Advanced Server 3.0 Linux file system. Additions to the layout for the HP XC system are described in later sections. The file system layout is structured to isolate the cluster-specific files from base operating system files, described in “General File System Layout”. This isolation allows for flexibility and ease of potential upgrades of the system software and keeps software from conflicting with user-installed software. The files are segregated into the following types:
The HP XC system relies on key files. Interfering with these files can cause the system to fail. The best way to avoid this situation is to respect the placement of directories and files, especially when installing software packages. You can avoid many pitfalls by strictly maintaining separation between the HP XC System Software and other software. Following are the key files and directories:
New third-party software packages may break the system. Be sure to assign individual areas when using Relocatable software packages, that is, do not intermingle other vendors' software with the HP XC system files directories. The /hptc_cluster directory is the global file system on an HP XC system. This file system is shared and mounted by all nodes. This directory contains configuration and log file information that is applicable across the system; various services rely on the files in this directory. These log files are in the /hptc_cluster/adm/logs directory. During system installation, you are given an option to locate the /hptc_cluster file system somewhere other than the installation on the head node. For example, you can place it on a partition on the head node's disk, on a networked disk, on an HP SFS server, or on a SAN. This directory is mounted on the head node. You must ensure the persistence of this file system mount.
Software installed in the /opt/hptc directory is for the exclusive use of the HP XC System Software. Do not install or replace any other software in this directory unless it is an officially supported patch. Software packages are installed in directories under the /opt/hptc directory under their own names.
Four subdirectories under the /opt/hptc directory contain symbolic links to files included in the packages: Each package directory has a subdirectory corresponding to each of these directories. In each subdirectory, every file has a symbolic link to the corresponding directory. For example, the SLURM package has a directory /opt/hptc/slurm with subdirectories /opt/hptc/slurm/bin, /opt/hptc/slurm/sbin, /opt/hptc/slurm/lib, and /opt/hptc/slurm/man. Every file in /opt/hptc/slurm/bin has a symbolic link to /opt/hptc/bin, and the files in the other subdirectories have links into their corresponding directories. Figure 1-3 shows the hierarchy under the /opt/hptc directory. Software packages are shown in boxes with dashed lines. The example directory below the packages contains symbolic links to /opt/hptc/bin, /opt/hptc/sbin, /opt/hptc/lib, and /opt/hptc/man, and are shown in grey. The /opt/hptc/etc/ directory includes two subdirectories containing scripts used to configure services on nodes at installation time. The /opt/hptc/etc/gconfig.d directory contains scripts used to gather information needed to configure a service on the HP XC system. The /opt/hptc/etc/nconfig.d directory contains scripts associated with specific services, which configure nodes that run these services. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||