QUADS 1.1.3

About 1.1.3

QUADS 1.1.3 is a major bugfix and minor enhancement release for the 1.1 gaúcho series and is highly recommended. This comes around 3 months after 1.1.2 and building on the the landmark, next-generation 1.1.0 series.

1.1.3 is comprised of around 5 x enhancements and 28 x bug fixes, it also adds support to badfish for the Dell fc640 blade hardware and auto-generation of OpenShift inventory metadata to help automate OpenShift deployment on bare-metal.

🐰 1.1.3 arrives just in time for the Easter Bunny 🐰

Feature Highlights

• Add Support for OpenStack Inventory for assisting in automated OpenShift on bare-metal deployments.

Similar to ironic-based OpenStack deployments you can now download the equivalent OCP inventory file to feed into your installer for automated deployments.

• Support for Dell fc640 bladecenters is now present.
• More flexible Redfish / iDRAC behavior via querying and using supported reset types.
• Better readability for notifications.
• Page revisions are limited in the Wordpress wiki container images for better performance.

Major Bug Fixes

• Badfish Fixes for Dell fc640 blade servers.
• Fix for heat map visualizations calculating and displaying data for the next four months into the future.
• Fix for ordering interfaces for verify_switchconf.py
• Fix for sorting order for --ls-interfaces
• VLAN fix for clearing --vlan with --define-cloud
• Fix for Juniper automation dealing with changeset commits
• Fixes for managing public VLANS and verify_switchconf.py for the Juniper platform.
• Fix for premature notifications when cloud assignments are being validated
• Fix for badfish graceful restart functionality on supported systems
• Backport fixes/updates from upstream Badfish into QUADS badfish.py library.
• Fix for no wipe assignments and new hosts being added and not validated as they should.
• Please see changelog below for all changes

New Configuration Options (Read before Migrating from 1.1.x)

• You'll need to define openshift_management: parameter in quads.yml. By default this is set to openstack_management: false.

• You'll need to set a password prefix, this is to tackle some vendors like SuperMicro imposing an IPMI password length policy. New user IPMI and Foreman passwords are now infra_location@ticket

  • Setting to add: 4-character string for infra_location in quads.yml
  • Typically most people would just use the airport code here, or some other short identifier
  • Prior to 1.1.3 if your user IPMI/Foreman password was 12345 (--cloud-ticket number) then it will now be rdu2@12345.

infra_location: rdu2

• If you have a request URL or form for users to submit assignment requests for QUADS-managed environments you can enter that in quads.yml (optional):

quads_request_url:

• If you were previously using rt_url (and the RT ticketing system like us) this has changed as we've moved to JIRA. The following parameters are now changed/added:

  • rt_url is now ticket_url
  • ticket_queue is now required for rt_url to support the base URL path corresponding to your ticket queue.

• In general it's always a good idea to diff your running quads.yml with the new version to compare any new options that might have been added:

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

All Changes

You can view the full changelog here