Automation concepts
Overview
Automation concepts
Background on infrastructure-as-code and configuration-management tooling on Quake AI: which tool fits which job, how OpenTofu and Terraform compare, and how Ansible layers on top of provisioning. For step-by-step walkthroughs, see the how-to guides.
Concepts
- Ansible on Quake AI: Ansible is the configuration-management layer for Quake AI infrastructure. Where OpenTofu provisions instances, networks, and volumes, Ansible installs software, deploys applications, and manages OS...
- Authoring IaC Templates for Quake AI: You write OpenTofu or Terraform templates against the OpenStack provider the same way you would on any Antelope-era cloud. Quake AI adds a small, fixed catalog of flavors, networks, and volume types...
- Cloud Automation and Orchestration: Cloud automation replaces manual, click-through provisioning with code that describes your infrastructure. Instead of logging into a dashboard to create a VM, a network, and a security group one at a...
- IaC on Quake AI: OpenTofu and Terraform: OpenTofu is the default Infrastructure as Code tool for Quake AI. It is fully open source (MPL-2.0), backed by the Linux Foundation, and compatible with Terraform providers, modules, and state files...
- Terraform and OpenTofu on Quake AI: Terraform and OpenTofu use HashiCorp Configuration Language (HCL) to define infrastructure as code. You describe the resources you want (instances, networks, volumes, security groups) in .tf files...
Quick answers
See Also
Was this page helpful?