Skip to content

Release Notes

2023.4.0 (23-11-23)

  • New Feature - Internal object store
  • New Feature - Internal database
  • Fix - Migrated Portal to Vue 3
  • Fix - Updated dependencies
  • Fix - Correctly constrain jobs based on SLC version specified
  • Fix - Hubctl output formatting improvements

2023.2-2.3.3.1 (24-5-23)

  • Fix - Timeout behaviour
  • Fix - Templating LDAP imports
  • Fix - Auth token not in local storage
  • Fix - Facets improvements

2023.2-2.3.1.45 (09-5-23)

  • New Feature - Execution Profile Facets

2023.1-2.3.0.462 (18-04-23)

Upgrading from 5EA-2.2.0.108 or earlier, please follow these upgrade instructions.

  • New Feature - Altair Licensing
  • New Feature - Hubctl Verify helpers
  • Documentation Improvements
  • Fix - Security Improvements

5EA-2.2.0.108 (15-12-22)

  • New Feature - Library Server

5EA-2.1.3.186 (22-11-22)

  • New Feature - Set IntermediatefilesDirectory per execution profile

5EA-2.0.22.488 (08-11-22)

  • MSI Fix - Missing files

5EA-2.0.22.473 (30-09-22)

Upgrading from 5EA-0.1.45 or earlier, please follow these upgrade instructions.

  • New Feature - Altair Naming
  • New Feature - Execution profiles
  • New Feature - Namespaces
  • New Feature - Library Server (experimental)
  • New Feature - Workload diagnostics
  • Fix - Access control Improvements
  • Fix - Improved how Operating System user used to run workload is selected (removal of "default user")
  • RPM Fix - Move to fewer RPMs, new name and locations
  • MSI Fix - New name and locations

5EA-0.1.45 (03-08-22)

  • MSI Fix - Issues installing example programs
  • Fix - Issue with LDAP when re-syncing

5EA-0.1.42 (06-07-22)

Upgrading from 5EA-0.1.33 or earlier, you must run dnf upgrade wpshub-* in order to update all RPMs correctly.

  • MSI Fix - issues starting link sessions
  • RPM Fix - upgrade RPMs incorrect
  • Fix - Ldap Sync improvements

5EA-0.1.33 (16-06-22)

Upgrading from 5EA-0.1.11 or earlier. If upgrading to this version, or any later version, from 5EA-0.1.11 or earlier it is necessary to run the following command:

hubctl scheduler --algorithm spread

This is regardless of whether the upgrade is done using a "dnf upgrade", or whether it is done by uninstalling and reinstalling the RPMs. Although a fix in this release changes the default scheduling algorithm to spread, this does not affect existing installations, and instead the above command must be run.

  • MSI Fix - Spaces in directory name
  • MSI Fix - Path fixes to allow demo deployment
  • Fix - Ensure hostname is lowercase for browser compatibility
  • Fix - Change the default workload scheduling algorithm from "binpack" to "spread"

5EA-0.1.11 (16-05-22)

  • Vault integration
  • Windows MSI installer
  • Allow single machine install of RPMs

5EA-0.0.24 (08-04-22)

  • Public availability of RPMs