QUADS 2.2.2

About 2.2.2

😎 QUADS 2.2.2 provides the ability to set/manage BIOS boot order modes for new future environments, fixes and improvements to the self-scheduling API and additional performance improvements. This is a minor feature release that focuses on simplifying some internal orchestration workflows as well and in some cases reduces the bare-metal release time by a whopping 25-30%.

Major Feature Highlights

• We have revamped how BIOS boot order management works so that it's now configurable, with the default now being foreman but still supporting director boot mode for OpenStack workloads still using ironic-based PXE orchestration. This provides the following tenant and operator benefits via #599
  • Reduction of bare-metal systems delivery time by 25-30%, eliminating a reboot cycle if using foreman_default_boot_order: foreman which is our default
  • Reduction of tenant post-delivery and day zero orchestration needs by eliminating the need to perform badfish --boot-to calls for re-provisioning in Foreman (it's enough to mark for build and reboot now).
• Additional performance improvements be removing some sleep mechanics if boot order matches what's requested #590
• Removed a few unneeded dependencies and files
• Additional fixes to self-scheduling API

Development Statistics

• 25 x peer-reviewed Gerrithub patch-sets
• 31 x changed files with 508 additions and 199 deletions.
• This is the 20th release of QUADS since 23-June 2016 when 1.0 was released

Full Change List

• A full list of changes can be found here

System and Infrastructure Requirements

• A supported version of Fedora is required if using our RPM packages
• Recommended VM with 8 x vcpu and 8 x GB of memory.
• Foreman for managing your DNS, DHCP, PXE and systems lifecycle

Breaking Changes and Migrations

• QUADS 2.2.2 requires Fedora 41 or higher, upgrade your Fedora OS before trying to upgrade QUADS.
• Upgrading from 2.2.0 to 2.2.2 performs a database migration, this happens automatically via the upgrade process for you.

Important

Be sure to address any changed configuration values prior to upgrading

Changed Configuration Values

• Added to /opt/quads/conf/quads.yml

foreman_default_boot_order: foreman
badfish_interfaces_path: /opt/quads/conf/idrac_interfaces.yml

• Added to /opt/quads/conf/selfservice.yml

ssm_description_prefix: "[SSM]"

Checking Configuration File Differences

• It's a good idea to diff the updated config files with your existing ones to make note of any breaking changes

diff -u /opt/quads/conf/quads.{yml,yml.rpmnew}
diff -u /opt/quads/conf/quadsweb.{yml,yml.rpmnew}
diff -u /opt/quads/conf/selfservice.{yml,yml.rpmnew}

Known Issues or Limitations

• If tenants using the self-scheduling API abort their reservation after an assignment is created but before host schedule(s) are added then there is currently no cleanup that occurs automatically. We have added documentation on managing active but orphaned assignments and will be addressing this in RFE #605

Packaging and Support

Note that the RPM attached this release may contain some additional fixes since the 2.2.2 release in the future.

If you run into issues or have questions please open an Github issue or find us on libera.chat IRC #quads