The infrastructure deployment time machine
Badfish has received substantial updates and fixes in the 1.6/1.7 release, including its own Redfish emulator for developing/testing against a mock iDRAC without bare metal. iDRAC10 support, configurable REST timeouts, multi-vendor detection and a lot more are within, come have a look! Continue reading “New Badfish Features!”
Since the release of our self-scheduling API we’ve gotten fantastic feedback! To add to the many ways of consuming it we’ve authored a robust Ansible playbook for a quick and dirty way to self-schedule sets of hosts via the SSM API. Continue reading “Self-Schedule QUADS Hosts with Ansible”
Badfish gets the Asyncio treatment. With the move of QUADS to asynchronously provisioning the servers on our lab, much of the functionality from Badfish was already converted to use asyncio in the process. This has now been the first effort in the road to unifying the Badfish standalone tool with the code used from within QUADS. Continue reading “Badfish is Superboosted!”
You can now run Badfish very quickly and easily in a docker container. There’s no need for Python libraries or git you simply need Docker installed. This is useful for people on Mac OSX or Windows for example or older Linux distributions who may not have Python libraries required like python-requests or python-pyyaml. Continue reading “Badfish is now Containerized”
Badfish is a vendor-agnostic, redfish-based API tool used to consolidate management of IPMI and out-of-band interfaces for common server hardware vendors. Badfish is also a popular song from Sublime, this may be a coincidence. Read more about Badfish here.
We’ve revamped our QUADS Jenkins CI to use Docker containers and instantiate a full QUADS stack (wiki, wiki_db, quads, quads_db, nginx) for every patchset committed to Gerrit code review. Below is a not-so-artistic diagram of how it all works. Continue reading “QUADS CI is Revamped”
