Software Delivery Repository
Software Delivery Repository | Getting Started | FAQSGI® REACT™ - HPE Update Server Setup
Oct.2019 Update: SGI REACT 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.
SGI REACT is the only hard real-time performance solution for standard Linux distributions, for which no special custom kernels are required. SGI has successfully achieved a real-time latency guarantee of 30 µsec for up to 64 threads, which is similar to more specialized hardware-software real- time solutions. With SGI REACT, system administration is easier, since the Linux used on the developer's systems is the same as the production system. The hardware system used as the developer system can also be identical to the production system. And software development is also easier, since the same compilers and tools used in non-real-time applications are also used for real-time programming. SGI REACT includes the SGI REACT library for Linux hard real-time performance, the SGI Linux Trace debugger for real-time applications, frame rate scheduler, the SGI shield runtime anti-jitter capability, user level interrupt support and the external interrupt driver.
An active warranty or support contract is required to access SGI REACT
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 REACT 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 SGI REACT repository
Red Hat Enterprise Linux
Cut-n-paste the following section (substituting ditribution, architecture and project version) into/etc/yum.repos.d/react.repo
on your RedHat system:
[react]
name=SGI-REACT
baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/react/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, 7.2, 7.3 arch x86_64 project_ver 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/react.repo
on your SUSE system:
[react]
name=SGI-REACT
baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/react/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 arch x86_64 project_ver 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 REACT packages
List available packages
# yum --disablerepo="*" --enablerepo="react" list available
# zypper search --repo react
Show available updates
# yum --disablerepo="*" --enablerepo="react" check-update
# zypper list-updates --repo react
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 - = - _ = _ ~ = ~