-
Notifications
You must be signed in to change notification settings - Fork 0
Home
A private cloud you build yourself, on a machine you rent by the hour.
Three layers, each doing one job:
| Layer | Tool | Job |
|---|---|---|
| Host | Terraform | Creates one Azure VM, its network and its firewall |
| Platform | Ansible | Installs OpenStack on that VM, through DevStack |
| Workload | Terraform | Creates instances, networks and security groups inside it |
Terraform and Ansible are clients. They call an API, they do not create machines out of thin air. On AWS or Azure that API is rented. On your own hardware, something has to provide it, and that something is OpenStack.
Running this lab is the shortest way to see that boundary for yourself: what the cloud provider does, where the API sits, and what your tooling actually talks to.
DevStack is a learning and development tool. It builds every service from source on a single machine and does not survive a reboot. A production OpenStack is deployed with Kolla-Ansible or OpenStack-Ansible across at least three control nodes. Nothing here should be copied into production.
- Prerequisites what to install, and how, in one block
- Makefile every target, in the order you will use them
-
How it works what happens between
make one-shotand a running instance - Terraform layout why three stacks, and how to reason about your own
- Troubleshooting the failures this lab actually hit
- References the documentation that matters
git clone https://github.com/WhiteMuush/Simplon-OpenStack.git
cd Simplon-OpenStack
make env # write .env and the tfvars, generate a password
make one-shot # host VM, then DevStack, about an hour
make demo # create an instance and log into it
make stop # deallocate, or billing keeps running