How to Access HPE Software Delivery Repository (SDR)

Creating an HPE Support Center Passport Account and User Token

Accessing SDR will require an HPE Passport Account with an HPESC user profile. If you don’t have the proper permissions, please work with your site admin to coordinate package access.

To sign in or create an HPE Passport Account:

Access a Web browser, and go the HPE Support Center (HPESC) website.
After you access an HPESC website, click HPE Sign in. The HPE Sign In screen appears.
Do one of the following:
- If you do not already have an account, click Sign up to get started, and follow the on-screen prompts.
- Enter your credentials, and click Sign in.

To obtain a user token:

Visit the HPE Support Center User Token Web page.
Sign in, if needed, using your single sign-on user ID and password. The system-generated token appears.
Copy and securely store this token, as it may not be retrievable later. This token can then be used to authenticate API calls or access-subscribed software services later in the SUPS installation process.

Contact the HPE Support Center portal for assistance or refer to the official HPE Support Center documentation for detailed instructions if you encounter issues.

Web Browser

You can access the HPE Software Delivery Repository (SDR) via a web browser. Navigate to https://update1.linux.hpe.com/repo/sups in a web browser. Enter your HPE Passport email and token generated above in the pop-up window. You will then be able to navigate the site and download packages.

Command-line Tool

You can access the HPE Software Delivery Repository (SDR) via a command-line tool such as curl. The following example uses curl to download an RPM from the SDR.

curl --fail --user <email-address>:<token> \
    --output sups-1.0.0-1.el9.noarch.rpm \
    https://update1.linux.hpe.com/repo/sups/1.0/base/rhel/9.6/noarch/sups-1.0.0-1.el9.noarch.rpm

Package Manager

To configure your package manager to access SUPS SDR, you will need to create a repository file on your system.

You can cut and paste the following section (substituting <email-address>, <token>, <version>, <subtype>, <os_type>, <os_version>) into /etc/yum.repos.d/sups.repo on your RHEL based system or /etc/zypp/repos.d/sups.repo on your SUSE based system

[sups]
name=SUPS
baseurl=https://<email-address>:<token>@update1.linux.hpe.com/repo/sups/<version>/<subtype>/<os_type>/<os_version>
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://<email-address>:<token>@update1.linux.hpe.com/repo/sups/HPE-RPM-PROD-KEY-FIPS.public

The package manager will then be able to access the SUPS SDR and install RPM packages.

On SUSE based systems, install a specific SUPS package with zypper via

zypper install <package>

On RHEL based systems, list the available packages in the SUPS repository via

dnf --disablerepo="*" --enablerepo="sups" list available

or install a specific package via:

dnf install <package>

General Repository Structure

The general structure of the SUPS SDR is as follows:

https://update1.linux.hpe.com/repo/sups/<version>/<subtype>/<os_type>/<os_version>

Near the top level, we provide a SUPS version (e.g., 1.0) for released software within the same release circle.

Within a specific SUPS version, there are three subtypes: base, updates, and experimental.

base: The base release version of the SUPS software. This generally mirrors what is, or will be, officially released to HPE support center.
updates: Updates to the base release that are validated and tested to work with the base release. These updates are generally released as patches or hotfixes.
experimental: Experimental component updates of the SUPS software. These updates are generally released as pre-release or beta software. These updates are not supported by HPE and are provided for testing and evaluation purposes only.

Below these levels, we provide OS type, OS version, and then architecture breakdown.

Example of the repository structure:

sups
 \_ 1.0
 |   \_ base
 |   |   \_ sle
 |   |   |   \_ 15.7
 |   |   |       \_ aarch64
 |   |   |       \_ noarch
 |   |   |       \_ x86_64
 |   |   \_ rhel
 |   |       \_ 8.6
 |   |           \_ x86_64
 |   \_ updates
 |   |   \_ rhel
 |   |       \_ 8.6
 |   |           \_ x86_64
 |   \_ experimental
 |       \_ rhel
 |           \_ 8.7
 |               \_ aarch64
 \_ 2.0
     \_ base
     |   \_ sle
     |   |   \_ 15.7
     |   |       \_ aarch64
     |   |       \_ x86_64
     |   \_ rhel
     |       \_ 8.7
     |           \_ x86_64
     \_ updates
     |   \_ rhel
     |       \_ 8.7
     |           \_ aarch64
     \_ experimental
         \_ rhel
             \_ 8.8
                 \_ x86_64

FAQ

Q: I can’t generate a token; I’m getting an error (e.g., Only HPESC user profiles are authorized to generate user tokens, please log in with your HPESC user profile and try again.)

A: If you can download SUPS’s current software in HPE Support Center, you should have access to the repository after following these instructions. If you do not have access to SUPS via https://myenterpriselicense.hpe.com/cwp-ui/software, please work with your internal site admin to gain access. If you are a site admin and do not have access, you can contact your HPE sales representative.

Q: I’m able to access the web repo, but I’m unable to use package manager.

A: For some package managers (dnf/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 found on an online tool like URL Decode and Encode to help encode your email address.

Q: What is a dnf/zypper/apt repository?

A: Dnf, zypper and apt are software configuration managers for Linux systems. They find, download and install software packages. Also, and more importantly, they also find any dependency packages and install those as well. Dnf is found on RHEL based systems, zypper is found on SUSE based systems, and apt is strictly for Debian-like (Ubuntu) systems. Dnf and zypper work with RPM packages, while apt installs Debian packages.

Q: I don’t know the exact name of the package, how do I search a repository?

A: You can search for packages in the SUPS SDR using the package manager’s search command: dnf search for RHEL based systems and zypper search for SUSE based systems. For example:

zypper search cce
dnf search cray-mpich

Q: Are these signed?

A: All RPM headers are signed by HPE. Repository metadata are signed as well.

Q: How do I import HPE public keys to verify indexes and packages?

A: All HPE public keys for SDR may be found here: https://update1.linux.hpe.com/repo/sups/HPE-RPM-PROD-KEY-FIPS.public

Q: Why do I have to “login” to get SUPS software?

A: An active warranty or support contract is required to access the SUPS SDR.

Q: I have linked a contract to my HPE Passport account on HPESC, why am I still unable to access entitled content?

A: Contracts newly linked to your HPE Passport account may take up to 24 hours to reflect when accessing content on the Software Delivery Repository. After this time, if you continue to have issues accessing content for which you have linked a relevant contract, please contact support for assistance.

Q: I have another question not answered here or by a support center staff member, are there any other avenues to ask questions?

While our public Slack Workspace is not actively monitored by SUPS engineers, many other SUPS users have access and post there. Please join our Slack Workspace and start a discussion in our #hpe-cray-programming-environment channel.