Bootstrapping a new server takes too many steps? #35
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While I was thinking about #34...
This is what you have to do to make a new server today:
abra server new hetzner autonomic-foobar
(create new VPS)abra server add foo.autonomic.zone <myuser> <mysshport>
(setup context)abra server init foo.autonomic.zone
(install swarm/networking)This seems like too much stuff. I don't think we've faced this issue because we create all our VPSs with Ansible automation outside of
go-abra
but other folks won't have all that.Maybe we could also design a flow here for creating a new server?
I raised this cloud-init related ticket over in Capsul land, that is relevant for the bootstrapping of Docker, user accounts, firewalls etc. without the use of Ansible. People can just write a YAML cloud-init file and then
abra server new
would take that into account perhaps?There was talk of
abra server dns gandi <host> <ip>
in #106.Sounds amazing.
We could automate this fairly easily, right? Maybe using Lego, like Traefik does? https://go-acme.github.io/lego/
Terraform based approach sounds really interesting: