OpenStack stacks
OpenStack support lets you run OwnStack on private clouds and the many public clouds that expose an OpenStack API (OVH Public Cloud, IBM Cloud, etc.). Provisioning shape mirrors AWS and GCP: connect credentials, pick a flavor, hit provision.
Prerequisites
- An OpenStack project with quota for one Nova instance, one floating IP, and one security group.
- Application credentials — easier to manage and revoke than user passwords. Create under Identity → Application Credentials in Horizon.
- An
openrcfile or the equivalent values:OS_AUTH_URL, project ID, region, application credential ID + secret.
Connect
In the dashboard, Cloud accounts → Add → OpenStack. Paste your auth URL, application credential ID, and secret. The control plane validates the credentials by listing flavors.
Create the stack
| Field | What to set |
|---|---|
| Region | Whichever region the credentials are scoped to. |
| Flavor | 2 vCPU / 2 GiB minimum. Most providers expose Heroku-equivalent sizes (s1-2, b2-7, etc.). |
| Image | Ubuntu 22.04 LTS — the only image OwnStack provisioning is hardened for. Newer LTS is on the roadmap. |
| Volume size | 30 GiB minimum, 50 GiB comfortable. |
| Floating IP | Required for external access; OwnStack allocates one and attaches it. |
| Network | Either an existing tenant network with router → external, or accept the defaults if your project is preconfigured. |
Security group
Same shape as AWS: 22, 80, 443 open from 0.0.0.0/0. Restrict 22 to known IPs in production.
Decommissioning
$ ownstack stack destroy <stack>
Deletes the instance, releases the floating IP, removes the security group. Volumes are released too unless you flagged the data volume to persist (advanced; ask in the dashboard).
Read next
- Stack backups
- SSH-provider stacks — if your OpenStack provider doesn't expose API access, but you can SSH to the host you provision manually.