Software Delivery Repository

Software Delivery Repository | Getting Started | FAQ

HPE Message Passing Interface (MPI) - HPE Update Server Setup

Oct.2019 Update: HPE Message Passing Interface (MPI) 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 Message Passing Interface (MPI) is Hewlett Packard Enterprise's high performance MPI library. Centered around the Message Passing Toolkit (SGI MPT), HPE MPI contains complementary tools enabling application acceleration, with SGI MPT as the core MPI performance engine.

HPE MPI includes SGI Message Passing Toolkit, Perfcatcher MPI profiling tool, easy launch of MPI applications with Array Services, accurate shared memory measurement, SHMEM PGAS library, xpmem cross process memory mapping, SGI MPI PerfBoost which enables applications compiled against other MPIs - Platform MPI, Intel MPI, Open MPI and MPICH 1 - and enables them to run with SGI MPI, checkpoint restart for SGI MPT, MPIplace MPI rank placement tool and MPInside MPI profiling and performance analysis tool.

An active warranty or support contract is required to access SGI or HPE MPI 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 SGI MPI repository with your web browser (or yum, or zypper) using the following http URL syntax:

https://EMAIL:TOKEN@update1.linux.hpe.com/repo/mpi

SGI and HPE MPI releases are available via the HPE Support Center. View your existing contracts and warranties or get help linking contracts or warranties to your HPE Support Center user profile. To obtain additional support coverage, please contact your local HPE office, HPE representative, or visit Contact HPE. Click here for more information.

Generate_Token then
Browse
with email as username,
token as password

Subscribe your system to the SGI MPI or HPE MPI repository

Red Hat Enterprise Linux

Cut-n-paste the following section (substituting ditribution, architecture and project version) into /etc/yum.repos.d/mpi.repo on your RedHat system:


        [mpi]

        name=MPI

        baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/mpi/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.7, 6.8, 6.9. 6.10, 7.2, 7.3, 7.4, 7.5, 7.6
   arch          x86_64, aarch64
   project_ver   1.1_hpmi, 1.2_hmpi, 1.3_hmpi, 1.4_hmpi, 1.12, 1.13, 1.14

SUSE Linux Enterprise Server

Cut-n-paste the following section (substituting ditribution, architecture and project version) into /etc/zypp/repos.d/mpi.repo on your SUSE system:


        [mpi]

        name=MPI

        baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/mpi/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, 12sp1, 12sp2, 12sp3, 12sp4, 15
   arch          x86_64, aarch64
   project_ver   1.1_hpmi, 1.2_hmpi, 1.3_hmpi, 1.4_hmpi, 1.12, 1.13, 1.14

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

Installing SGI MPI packages

List available packages

# yum --disablerepo="*" --enablerepo="mpi" list available
# zypper search --repo mpi

Show available updates

# yum --disablerepo="*" --enablerepo="mpi" check-update
# zypper list-updates --repo mpi

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      - = -        _ = _        ~ = ~

Contact