Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Proxmox VE Helper Scripts

community-scripts.github.io

Post reply on HN
Print view View original

51–60 of 90 posts

Re: Show HN: Proxmox VE Helper Scripts

#51

Post by stephen_g »

TheSmiddy wrote: post #29
sgc wrote: post #17

I have been looking into setting up my first Proxmox box, here is my take as a newcomer. I wanted to do what I think is a very basic and very common setup: Modem > proxmox box > OPNsense VM > physical wifi router via onboard 10Gb NIC + internal network VMs like OMV etc. The goal is to add a full network filter via OPNsense, and allow access to a media sever and backup etc from the internal network. I see no OPNsense,…

> I don't see any glue scripts to get VMs talking to each other I'm confused by what you mean here? Don't they just use the network like any other computer? I haven't had to do any special configuration to get my VMs to talk to each other.

VMs usually have their virtual NICs connected to a bridge interface on the host (like a virtual switch) so they can communicate. Proxmox creates one up by default that is also bridged to the physical NIC you set up for management when you install it, so it just works.

In the router case, you'd likely want this default one to be the 'internal' network and have a separate interface (either physical or VLAN) for the WAN.

Re: Show HN: Proxmox VE Helper Scripts

#52

Post by gerdesj »

sgc wrote: post #17

I have been looking into setting up my first Proxmox box, here is my take as a newcomer. I wanted to do what I think is a very basic and very common setup: Modem > proxmox box > OPNsense VM > physical wifi router via onboard 10Gb NIC + internal network VMs like OMV etc. The goal is to add a full network filter via OPNsense, and allow access to a media sever and backup etc from the internal network. I see no OPNsense,…

No it isn't basic and common (it is for me but perhaps not for you and certainly not for most people)

OK, so you want to virtualise a router and firewall. That's fine. I have deployed roughly 200 pfSense firewall/routers as VMs and physical boxes and OPNSense is similar, so I can probably help.

At a minimum you will need two physical interfaces (one will actually do but you will need to know what you are doing!). You need "WAN" and "LAN". OPNSense is still FreeBSD based, I think, so it will not run in a L[inux]XC container for obvious reasons.

Your last paragraph seems rather confused. I don't know what you mean by "glue scripts". VMs communicate via networks

I suggest you try a few experiments to get to grips with virtualisation properly and then move on from there. If you swing by the Proxmox forums with specific issues we'll try to help out but in the end you need to dive in full on ... or not.

Re: Show HN: Proxmox VE Helper Scripts

#53

Post by stephen_g »

jdboyd wrote: post #36
xrd wrote: post #23

Am I right that proxmox takes over your entire machine? I have been using a combination of docker and lxc/lxd to manage my VMs. But, cockpit (on ubuntu) does not give me a perfect experience for managing running VMS, etc. I wish there was a good solution for all of this. But, it feels like you need to cobble together a bunch of kibana tools to get true monitoring.

Usually, proxmox is the base OS (meaing replaces whatever Linux/Windows/FreeBSD/etc that there was before). It is possible to run Proxmox inside KVM, but that isn't the usual choice.

Specifically, running Proxmox in a VM (for me at least) I'd only recommend for testing Proxmox itself, not for any production setup (even "production" in my homelab)

Re: Show HN: Proxmox VE Helper Scripts

#54

Post by gerdesj »

daqnz wrote: post #13
prettyStandard wrote: post #2

A bit of a tangent. I've been trying to manage libvirt& Unraid through terraform, but have run into issue after issue. I'm about given up, and will just manage the virtual machines manually... What's the virtualization technology on proxmox? What's the advantage to using something like this as opposed to terraform or salt stack or Ansible?

It is also worth mentioning that Proxmox uses ZFS making snapshotting quick and Proxmox also has a very good backup system. If you want to treat your self-hosted applications as "sheep" (1) , then terraform k8s etc. is a better bet. But if you are happy to manually restore from a backup or snapshot when something goes wrong, or automatically have your LXC container shifted to different hardware if you have a cluster,…

"It is also worth mentioning that Proxmox uses ZFS"

No it does not enforce ZFS or any other filesystem. That's up to you. ZFS or BTRFS are fine when indicated - and you need to know your stuff.

Cephs for clustering (hyperconverged) is very much a first class citizen. I generally only use EXT4 as a filesystem - keep it simple. XFS is lovely too, especially for reflinks if you need them.

(1) Wal and Cooch know how to run a farm (and so do I, in the UK!)

Re: Show HN: Proxmox VE Helper Scripts

#55

Post by stephen_g »

jamifsud wrote: post #37

Tangential question - what are people using their homelab for / what are some interesting or useful projects you've spun up on them? I've been thinking about setting one up but not 100% sure I'd find use out of it :)

I have Proxmox on my older (11th gen) Intel NUC - it runs my Unifi network controller for my WiFi APs, an Unbound DNS cache (because my router doesn't support DNS over TLS or DNS over HTTPS), a NAS (using ZFS on some hard drives in a USB 3.2 Gen 2, 6-drive disk chassis - the ZFS managed directly by Proxmox and then a Debian container just doing Samba).

That's all for now but I've just installed Home Assistant but haven't set that up yet. I also intend to try out Jellyfin as a media server and Frigate as a video recorder when I get some cheap cameras.

Re: Show HN: Proxmox VE Helper Scripts

#57

Post by brainfish »

sgc wrote: post #45
TheSmiddy wrote: post #29

Earlier quoted context omitted.

> I don't see any glue scripts to get VMs talking to each other I'm confused by what you mean here? Don't they just use the network like any other computer? I haven't had to do any special configuration to get my VMs to talk to each other.

I am not perfectly informed, but in my case, OPNsense would need to be the only vm with access to the incoming NIC port, and all other VMs and the router would need to use virtual network interfaces only coming from OPNsense for incoming. The router would be the only device with direct access to the outgoing NIC port. None of that seemed incredibly difficult looking into it, but still, it was the type of recipe I was…

VMs already use virtual network interfaces, which are by default bridged to `vmbr0`, a bridge that proxmox creates by default which is also bridged to the hardware NIC. For your use case, you simply want to create a second bridge, e.g. `vmbr1`, which is not bridged to the hardware NIC. You would then assign two virtual NICs to opnsense, one on each bridge (WAN and LAN, essentially) and then choose `vmbr1` as the bridge each time you create an "internal" service behind opnsense.

Since selecting the bridge for a service's NIC is part of setting up each service, the only thing such a "glue script" would be doing is creating the `vmbr1` bridge. That's already a one-liner.

Re: Show HN: Proxmox VE Helper Scripts

#58

Post by eddieroger »

midtake wrote: post #56

What capabilties does Proxmox have that are missing from simple KVM? Just a web interface?

Clustering, migration, high availability, backups, Ceph integration, virtual networks as of recent, can do containers as well as VMs to name a few off-hand. The web interface is optional, too. You should check out their webpage for more.

Re: Show HN: Proxmox VE Helper Scripts

#59

Post by spott »

KAMSPioneer wrote: post #10
WaxProlix wrote: post #5

I decided to run proxmox on my homelab rather than having a k8s setup, and I've come to sort of regret it. LXCs are awesome, but being bound to just them or qemu VMs doesn't fit all of my needs. With Kubernetes I could just add support for lightweight VMs (Firecracker hypervisor, or unikernels or something) with a project like Kata. Proxmox is just not extensible. It's also just not amenable to automation or reproduc…

It's certainly a different model of deployment. I like it, though it does have its warts. However there is a (community) TF module...? https://registry.terraform.io/providers/Telmate/proxmox/late... (I have no experience with it as I typically reach for Ansible). Also, easy-to-install ZFS makes it hard for me to cajol myself into trying something else. And if I want k8s for play time I can always spin up (a/some) VM(…

There is also this one: https://github.com/bpg/terraform-provider-proxmox

Re: Show HN: Proxmox VE Helper Scripts

#60

Post by all2 »

WaxProlix wrote: post #5

I decided to run proxmox on my homelab rather than having a k8s setup, and I've come to sort of regret it. LXCs are awesome, but being bound to just them or qemu VMs doesn't fit all of my needs. With Kubernetes I could just add support for lightweight VMs (Firecracker hypervisor, or unikernels or something) with a project like Kata. Proxmox is just not extensible. It's also just not amenable to automation or reproduc…

I have a single VM on my proxmox server that I spin up all my docker containers in... This is the simplest thing I could think of in terms of config. I haven't had to wire containers together, though, so maybe I've found the sweet spot for my deployment needs.
Post reply on HN