Community discussion is located here: http://community.pbspro.org/t/pp-702-design-document-review-for-rpm-based-install-under-cle-5-2/456

Overview:

The process of installing PBS Pro on Cray systems no longer utilizes the INSTALL script as it had in previous versions. The new installation method uses the RPM file directly, together with a set of instructions to configure the software under Cray CLE 5.2 and older versions. The process of installing PBS Pro under CLE 6.0 and newer is beyond the scope of this document and will be covered in a separate design document. It should also be noted that the practice of installing multiple versions of PBS Pro in different directories and using a symbolic link to indicate the "active" version has been discontinued. The new packaging and installation process makes PBS Pro more consistent with mainstream practices utilized by other Linux software.

Note: The RFE does not require what has traditionally been referred to as a migration upgrade. This design focuses on overlay upgrade procedures, as are common with RPM based packages.

Interface 1:

• Visibility: Public
• Change Control: Stable
• Synopsis: Default installation directory is /opt/pbs
• Details: The default installation directory used to be /opt/pbs/<VERSION> where <VERSION> was the current version of PBS Pro. A symbolic link named /opt/pbs/default was then created to point to the directory of the current release. This is no longer the case, and the default directory for PBS Pro shall be /opt/pbs on Cray systems as it is on other supported non-Windows platforms.

Interface 2:

• Visibility: Public
• Change Control: Stable
• Synopsis: Update the modulefile to reflect new installation directory
• Details: When PBS Pro is installed on systems utilizing the modules package (e.g. module load pbs) the PATH is updated to include /opt/pbs/bin and the MANPATH variable is updated to include /opt/pbs/man. The modulefile is now auto-generated based on the prefix set during build.

Interface 3:

• Visibility: Public
• Change Control: Stable
• Synopsis: Avoid unconfiguring PBS Pro during upgrade
• Details: The order in which spec file scripts are run during an upgrade is described here: https://www.ibm.com/developerworks/library/l-rpm2/ As a result, the spec file scripts were removing the PBS Pro init script during an upgrade. The spec file scripts have been updated to avoid deleting this file and disabling PBS Pro via chkconfig when an upgrade occurs. For an uninstall (e.g. rpm -e), these instructions do get called and PBS Pro is disabled.

Interface 4:

• Visibility: Public
• Change Control: Stable
• Synopsis: Do not print information message during upgrade
• Details: The message "NOTE: /etc/pbs.conf and the PBS_HOME directory must be deleted manually" is only printed when the PBS Pro package is uninstalled (e.g. rpm -e), and not during an upgrade.

Interface 5:

• Visibility: Public
• Change Control: Stable
• Synopsis: All PBS Pro services are disabled by default in /etc/pbs.conf
• Details: On non-Cray systems, PBS Pro services are enabled based on the type of installation performed. On Cray systems, additional configuration steps are required to "specialize" /etc/pbs.conf on various nodes where the services will be run. As a result, PBS_START_SERVER, PBS_START_SCHED, PBS_START_COMM, and PBS_START_MOM are all set to zero by default on Cray systems only.

Interface 6:

• Visibility: Public
• Change Control: Stable
• Synopsis: Add $alps_client entry in MoM config file for Cray systems
• Details: When the MoM config file is initially created on Cray systems, there was no entry added for $alps_client. This was left as a manual configuration step for the administrator. The lines "$vnodedef_additive 0" and "$alps_client /opt/cray/alps/default/bin/apbasil" are now added automatically on Cray systems only.

Interface 7:

• Visibility: Public
• Change Control: Stable
• Synopsis: Installation instructions
• Details: New installation and upgrade instructions are required to install PBS Pro on Cray systems with the interface changes described above. The following instructions are proposed:

Site Map

Developer Guide Pages