Altair One 2024.1.0.16

The release notes provides details about the enhancements and resolved issues in Altair One 2024.1.0.16

Access 2024.2 Enhancements

  • The issue of the first job to fail on new clusters is resolved.
  • Starting a session on a power-provisioned node no longer requires reconnecting in a new tab
  • Implemented security fixes identified during penetration testing.

NavOps (pclm) 1.93.3 Enhancements

  • Improved formatting and corrected the appliance deployment email for better clarity.
  • Corrected core count display for Azure HBv and HX instance families.

    The pclm logic previously failed to convert Azure vCPUs to physical cores correctly. Since Azure reports vCPUs, accurate core counts required conversion for proper use by Altair applications and PBS. This issue is now fixed, ensuring correct core display and node utilization.

  • Access Launch workflow directly from the appliance detail page.
  • Enhanced node selection, you can manually select a head node, matching the behavior for execution nodes. Automatic head node selection has been removed.
  • Improved the node selection dialog during appliance creation to display license count and required features.
  • License checkout for BYOC appliance creation is now based on selected node's resources enabling customers to use all available instances provided by CSPs. Altair Unit (AU) checkout for the node in BYOC is calculated as:
    • AU = ROUNDUP(nc/8,0)+2*ng
    • where nc is the number of CPU cores and ng is the number of GPUs.

Resolved Issues in NavOps (pclm) 1.93.3

  • Resolved an issue where a node was preselected during appliancecreation and scale up, even when only one option was available.
  • Resolved an issue with power provisioning behavior on AWS nodes.
  • Removed multi-GPU instances from selection for GUI-based applications in remote desktop sessions to ensure optimal compatibility and performance.