One thing I was a little disappointed with was the ignition provisioning system (https://coreos.com/ignition/docs/latest/) -- it's revolutionary (I mean not really, but it is to me) in the amount of the setting-up-the-server routine that you can skip, but I was disappointed that you can only run it once (by design, that's exactly what it's supposed to do, set up the machine ONCE). I currently manage one larger dedicated host that is more pet than cattle, but if I was truly in someone's cloud spinning up instances, then I could take time to build my perfect ignition config, but I only got one shot (and it worked the first time so), and didn't want to wipe the harddrive.
[1]: https://coreos.com/tectonic/docs/latest/install/aws/manual-b...
I really want to use Terraform, but it just doesn't look like it really wants to do the single server use case.
I’m running my system currently on Ubuntu (I’d have to pay extra for additional iSCSI drives), and I had to recreate the system hundreds of times due to mistakes.
So I built an automated system to do that, and tested it hundreds of times. So I’m at least sure that mine works.
I haven't tested the re-build process, which is why I'm almost certain it would fail me/require a lot of terrible manual steps.
I’ve done something very similar myself, and you’re exactly right.
The effort to set up a new project, or tear it down, is basically zero. I can properly version my entire system via git, by just exporting the configs as json, putting them in a git repo, and importing them back if I want to.
I honestly recommend everyone to at least try it out, it’s immensely useful (and a good skill to have)