A few weeks ahead of schedule, QUADS 2.1 brings immense improvement and simplicity to QUADS design by removing our WordPress component entirely and serving all automated wiki/inventory/visuals natively via quads-web
What’s Changed?
Over the course of ~6 months of parallel development up to and through the 2.0 release of QUADS we rewrote all of the functionality previously provided by WordPress (automated wiki/inventory/etc) in pure Python, Flask and Jinja2. This resulted in some of the following changes and improvements:
- Complete removal of the WordPress component/dependency from QUADS
- Removal of large parts of the code-base dedicated to automating the sync of QUADS status/wiki/inventory over the WordPress XMLRPC/Python API.
- The quads-web service will now handle our dynamic inventory and wiki component directly via Flask
- 13 x commits, 74 changed files with 1,724 additions and 2,045 deletions
- Full release notes here
Major Feature Highlights
- Full removal of WordPress as the QUADS automated wiki component
- Removal of large parts of the code-base dedicated to automating the sync of QUADS status/wiki/inventory over the WordPress XMLRPC/Python API.
- The quads-web service will now handle our dynamic inventory and wiki component directly via Flask
- Wiki content and navigation menus are now instantly generated
- Ability to serve your own static content and menus is documented here
- Huge performance improvements in quads –regen-heatmap using asyncio
- Much easier adoption for new users
Architecture Overview
This is what the QUADS 2.1 architecture looks like now:

Breaking Changes and Migrations
System Requirements
- A supported version of Fedora Server is required if using our RPM packages
- Recommended VM with 8 x vcpu and 8 x GB of memory.
- For full features, an existing Foreman that manages your DNS, DHCP, PXE and systems lifecycle
Migrating from 1.1.8
- You should follow the upgrade instructions from 2.0.5 for the steps and data migration needed to move to 2.1.
Migrating from 2.0.5
- Several conf/quads.yml changes have been completed removed.
- Nginx vhost configuration files have been simplified, see upgrade notes.
See the bottom of the changelog for full details