Software Delivery Repository
Software Delivery Repository | Getting Started | FAQHPE Performance Cluster Manager - HPE Update Server Setup
Oct.2019 Update: HPE Performance Cluster Manager patches are moving to a more secure system, update1.linux.hpe.com, which requires both an email and a token for access. As new products are released, patches for those products will be released to the new server; patches for older releases will be available at the new location as well as at the current locations at download.linux.hpe.com.
HPE Performance Cluster Manager delivers an integrated system management solution for Linux®-based high performance computing (HPC) clusters. It provides complete provisioning, management, and monitoring for clusters scaling to 100,000 nodes. The software enables fast system setup from bare-metal, comprehensive hardware monitoring and management, image management, software updates and power management. It reduces the time and resources spent administering HPC systems - lowering total cost of ownership, increasing productivity and providing a better return on hardware investments. For more information, about the latest release, please visit the HPE Performance Cluster Manager page on the HPE website.
An active warranty or support contract is required to access HPE
Performance Cluster Manager product updates. The email associated with
the HPE Passport account must be supplied as the username, and a
user-generated token must be supplied as the http password to access this
repository. If you have a valid warranty or support contract, login with
your HPE Passport credentials and
generate your token here. Once you have a valid token, you may access the HPE Performance Cluster Manager repository with your web browser (or yum, or zypper) using the following http URL syntax:
|
Generate_Token
then
Browse token as password |
Subscribe your system to the HPE Performance Cluster Manager repository
Red Hat Enterprise Linux
Cut-n-paste the following section (substituting ditribution, architecture and project version) into/etc/yum.repos.d/hpcm.repo
on your RedHat system:
[hpcm]
name=HPE-Performance-Cluster-Manager
baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/hpcm/rhel/dist_ver/arch/project_ver/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/GPG-KEY-HPE-SDR
Where:
EMAIL Email for HPE Passport account; must be URL encoded (e.g., SysAdmin%40some-company.com) (see note below) TOKEN Generated here dist_ver 6.9, 6.10, 7.4, 7.5, 7.6 arch x86_64, aarch64 project_ver 1.0, 1.1, 1.2
SUSE Linux Enterprise Server
Cut-n-paste the following section (substituting ditribution, architecture and project version) into/etc/zypp/repos.d/hpcm.repo
on your SUSE system:
[hpcm]
name=HPE-Performance-Cluster-Manager
baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/hpcm/sles/dist_ver/arch/project_ver/
enabled=1
autorefresh=1
type=rpm-md
keeppackages=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/GPG-KEY-HPE-SDR
Where:
EMAIL Email for HPE Passport account; must be URL encoded (e.g., SysAdmin%40some-company.com) (see note below) TOKEN Generated here dist_ver 11sp4, 12sp3, 12sp4, 15 arch x86_64, aarch64 project_ver 1.0, 1.1, 1.2
Import the GPG Key
Copy the GPG-KEY-HPE-SDR key to /etc/pki/rpm-gpg/
and then import the key with the following command:
rpm --import /etc/pki/rpm-gpg/GPG-KEY-HPE-SDR
Creating Local Mirrors
Many cluster administrators find it helpful to have a local mirror of the update repositories on the admin node or other local network accessible storage. For instructions on how to create a local mirror, please refer to the instructions in the support article, "How to Obtain Linux Software Patches from HPE".
Installing HPE Performance Cluster Manager packages
List available packages
# yum --disablerepo="*" --enablerepo="hpcm" list available
# zypper search --repo hpcm
Show available updates
# yum --disablerepo="*" --enablerepo="hpcm" check-update
# zypper list-updates --repo hpcm
Install a specific package
# yum install packagename
# zypper install packagename
URL Encoded Emails
In order for the yum and zypper to pass the correct email address to the authentication protocols on the Software Delivery Repository, email addresses in the *.repo files must be URL encoded. For most email addresses, changing the "@" to "%40" is sufficient. For instance, "john.smith@company.com" would be entered as "john.smith%40company.com" in the *.repo file. You may use the URL encoded values from the list below or use an online tool like URL Decode and Encode to help encode your email address.
@ = %40 & = %26 / = %2F ` = %60 space = %20 ! = %21 ' = %27 = = %3D { = %7B , = %2C # = %23 * = %2A ? = %3F | = %7C . = . $ = %24 + = %2B ^ = %5E } = %7D % = %25 - = - _ = _ ~ = ~