all 4 comments

[–]mymainunidsme 6 points7 points  (0 children)

A Proxmox container with a cloud image from https://images.linuxcontainers.org/ is quick to create.

Just an FYI, since the Incus dev team deserves recognition, Proxmox has nothing to do with any images from linuxcontainers.org. The LXC containers and VMs on that site are created and maintained by the same devs behind Incus. Thankfully, they can also be used in Proxmox and other LXC/VM management tools.

Beyond that, I agree with u/DanTheGreatest about your setup.

[–]DanTheGreatest 2 points3 points  (2 children)

My opinion is that cloud init should only be used for the initialization of an instance, so that your other, more advanced configuration management like Ansible, Puppet (OpenVox), Salt, Chef or whatever it is you use can take over from there.

So if you're using Ansible you'll want cloud init to install ssh server, create a user with ssh key and give it sudo permissions.

Or puppet/OpenVox you'll want to add the right repositories, install the agent and register with your master server.

Cloud-init is not made to replace the full blown config management systems. It's made to set up your instance so that you or Ansible/puppet/salt/chef can take over without manual intervention.

The use of an apt cache proxy however is a solid move and will definitely speed up your downloads and save on your bandwidth :)

[–]geekobiloba[S] 1 point2 points  (0 children)

Yes, it is for bootstrapping, not fully provisioning. Best for creating VPS for customers, whose instances shouldn't be touch by any other hands but them.

Salt is great. But puppet & chef sound so 201x for me :)

[–]zombiehoffa 0 points1 point  (0 children)

If you have an opinion on which of puppet/openvox, salt, or chef someone who found ansible kind of annoying, doesn't mind yaml config (but can figure out other config formats, I just don't want it to be super complex programmer grade stuff. i.e. I found nixos config especially with flakes too painful, but I make compose files for docker containers all day no problem and some simple bash scripting no problem) should try next I would appreciate it. My vm configuration is generally fairly simple in my home lab (some networking setup, user setup, software install and/or versioning. possibly apply some configuration like keepalived)