Hi, I have a home server (basically a NAS) currently running Debian. Basically it’s configuration is as follows

  • debian host running 3 VMs

  • debian running inside each VM as docker host

I just manually install KVM on the host then docker on each VM after creating each of them. I documented the process so I know how to replicate it in case I need to rebuild.

I now dream of being able to automate the rebuild process using config files. I know this is done using Ansible.

But I’ve now heard of Talos… (A thin layer for kubernetes) and intrigued. But I suppose I need a setup for the VM host to achieve automation through config files…

What setup are you guys using?

Thank you.


Thanks for all your suggestions! I’ve chosen to go with just bash scripting (given my simple setup) and keep the setup as it is… Just gotta learn bash and virsh :)

4 points
*

~~Stop. Docker is not a hypervisor and shouldn’t be used as one.

Either use a docker compose file to do automated deployments or move to Proxmox and use host templates to deploy VMs which then can host docker.

There is zero reason to run KVM in docker.~~

Never mind, I misread. What you are looking for is Ansible. You can create a VM template that has your SSH keys configured and then you use Ansible to spin up a VM and do stuff instead the VM. I know how to do this under Proxmox but I have no idea how to do it under pure Debian. A lot of it is probably the same.

permalink
report
reply
1 point

Thanks… Just for clarification, you can use Ansible to control Proxmox as well… and automate the entire VM bring up?

permalink
report
parent
reply
2 points

Proxmox is basically a VM management software that runs in a Debian install. You may be able to add it to your current install, but I am not certain about that.

permalink
report
parent
reply
3 points

Yes

permalink
report
parent
reply
3 points

I just use a few shell scripts. Basically some simple bash scripts that do all the work after a fresh install.

Kubernetes/Ansible are great to learn, but are also more complicated for simple setups.

permalink
report
reply
2 points

haven’t thought about it. I guess I’ll learn some bash :)

BTW what is a good OS for the VM host? many here are running proxmox… would you recommend it for this purpose of bash automation to bring up VMs?

permalink
report
parent
reply
2 points

I use Debian and Ganeti. I’ve not toyed with much else, so I dont know how they compare.

permalink
report
parent
reply
2 points

thanks for the info… I’m thinking of sticking with just Debian (as my simple usecase) and use virsh commands…

permalink
report
parent
reply
3 points

Proxmox is built on Debian and is great. My second choice would just be plain Debian.

permalink
report
parent
reply
2 points

Okay 👍 Thanks for your suggestions. Think I’ll just stick with Debian 🙂

permalink
report
parent
reply
3 points

Personally, if you’re considering it already, kubernetes might be something to look into. It’s a lot. Like a lot to learn. But I can honestly say I could do it for a job now with how much I’ve learned. Then it’s less about how to set up machines and more about just reapplying your infrastructure.

permalink
report
reply
4 points

When I change my server, I always start from scratch, hoping that it will come out better.

I don’t know what I’m expecting, it was always working well…

permalink
report
reply
1 point
*

I’m now using Fedora CoreOS which can be deployed from config files. It’s really neat to be able to define everything the way you need it and just start up the VM with no further config necessary. I’m using podman to manage my services.

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5.2K

    Monthly active users

  • 1.8K

    Posts

  • 19K

    Comments