QUADS 2.2.0 is released featuring the long-awaited self-scheduling API feature.  GPU hardware filtering to compliment AI workloads, a freshly painted dark theme for quads-web and other features and fixes come along for the ride in this milestone release.

About 2.2.0

🐰 QUADS 2.2 delivers breakthrough enhancements such as the long-awaited self-scheduling API feature and GPU awareness to compliment AI workloads. This release is primarily a major feature release with a slew of fixes as well and a sleek looking dark theme for quads-web.

2.2 is the culmination of nearly a year of parallel development work and we’re really excited about releasing it to the world.

Major Feature Highlights

• New self-scheduling feature via the RestAPI! You can talk directly to the API or use our new Python client library
• QUADS is now aware of GPU devices and they can be added to the metadata model for filtering and systems selection.
• You can now use any hostname convention you like as rack, u-location and blade are part of defining new hosts
• quads-web now has a dark theme
• You can now select a different OS from the default for future clouds from anything available in your Foreman via –os and you can use –os-list to list available operating systems from your Foreman.
• Packaging enhancements: quads-server and quads-web will now auto restart after upgrading and run any database migrations for you.

Development Statistics

• 86 x peer-reviewed Gerrithub patch-sets
• 117 x changed files with 3,929 additions and 1,175 deletions
• Welcome our 13th contributor, @sjug
• This is the 19th release of QUADS since 23-June 2016 when 1.0 was released
• A full list of changes can be found here.

Breaking Changes and Migrations

• Configuration files have been split out into two new files:
  /opt/quads/conf/quadsweb.yml (UI specific options go here now)
  /opt/quads/conf/selfservice.yml (options for self-scheduling feature, disabled by default)
• Please see the Breaking Changes and Migration instructions on the official release changelog.