AHA!!! I believe I have cracked the #Frigate #HomeAssistant #Proxmox nut! I can now get a snapshot from a camera via Frigate to Home Assistant in the correct resolution and then upload that via SSH and RSYNC to a remote server!
The trick was setting up the camera as a second camera with only a detection stream using the full resolution but then turning off detection and adding height and width parameters. Next toot will be the code.
Hey les copains #sysadmin grands sorciers de #proxmox et #ceph question réseaux svp:
- 2 interfaces 10gb en bond0
- bond0 bridgé en vmbr0 (tolerance de panne + répartir 20gb sur vlans (vmbr0.x) (internes ceph et utilisés par VMs)
q1: MTU, je veux jumbo sur le vlan ceph et normal sur le reste. Je mets:
- 9000 sur le bond
- un peu moins sur vmbr0
- ce que je veux sur les differents vmbr0.x mais max <vmbr0
q2: comment gérer les limites de bande passante par vlan?
@fatalerrors obviously ;)
I've finally completed most of the guides I was planning on adding to my #Homelab Wiki - now it's got guides on setting up #Portainer, #Immich, #Jellyfin, #ErsatzTV, #OpenMediaVault (#OMV), and even #HomeAssistant - all of these (besides Jellyfin and ErsatzTV, those are on #Proxmox) are hosted on my #RaspberryPi in my homelab.
Most importantly though, I've organised the wiki a lil better - into different courses. The first course details the type of hardware you're going to want to assemble - a beefy server (with only consumer parts) or a mini server (i.e. an #SBC), or whether you'd like to deploy a #NAS, followed by a course to setting up and managing a hypervisor (including #ESXi, but really, use Proxmox - which is #FOSS and plain better).
There's also a whole course on all sorts of 'host deployment environments' (i.e. where your application is hosted on, like #VM, #Docker, #Kubernetes, and #LXC) you could have in your homelab. (One of the) Most importantly, a course on networking - which covers valuable topics like setting up a domain, free or paid, and setting up a reverse proxy for serving your hosted applications publicly, securely.
There's still some stuffs I gotta add, like a complete guide on setting up #TrueNAS (which I've set up for many years at this point, without much documentation on how I did it - so I gotta find an opp to replicate it, when I have extra hardware maybe), but I'm pretty happy with it at this point. If you're planning to get into homelabbing, or even if you're already in it - maybe check it out 
https://github.com/irfanhakim-as/homelab-wiki
RE: https://sakurajima.social/notes/a9so79m6ze
My #homelab wiki is getting really complicated to organise and write for haha, but it's definitely getting more interesting topics like more #RaspberryPi stuffs, #Docker, and some cool stuffs like #OpenMediaVault and #HomeAssistant. I'm taking my sweet time to update them 'properly' and hope it'll all link/piece together sensibly in the end.
This is partially thanks to me embracing the fact that I just don't (yet) have the resources for a standalone 'mega' homelab (#Proxmox & #Kubernetes based) server cluster that I could simply throw everything to it, hence supplementing that setup with tinier SBC-based servers. Gives me a bit of peace of mind too that things are now more 'spread out'.
The most interesting bit will probably be when I manage to explore replicating a mini version of my #RKE2 Kubernetes cluster, on a single (or at most, two) Raspberry Pi node - maybe based on #k3s, assuming that's better. I'm just not there yet cos I'm kinda reluctant if using something like #k8s on RPi makes much sense since I'm expecting a lot of resources will be wasted that way, when hosting on Docker alone (i.e. on #Portainer) should be leaner. Anyway, if y'all wanna keep an eye on it: https://github.com/irfanhakim-as/homelab-wiki
I'm still trying to figure out the best approach to capture snapshots at regular intervals using #Frigate and possibly #HomeAssistant from the high resolution stream of a bunch of IP cams. Then down-scale them to a smaller resolution. Then RSYNC them to a remote server. And only retain the last ~100 images per IP cam on the remote server (and do cleanup locally).
Of course I cannot use RSYNC or Image Magick on Frigate because of the way it's installed (in a container in #ProxMox
I got that plugin working! Now my #HomeAssistant #Frigate #ProxMox setup is successfully syncing to the remote server.
Wish I had found this plugin last week 
Now I can move on to playing around with the Frigate AI detection.
And I still need to figure out how to make the snapshots pull from the high resolution camera feeds. No clue yet how to do that.
I've gone very far down the #HomeAssistant #Frigate #ProxMox rabbit hole and still haven't found the bottom on this problem. Through copious use of log files and error handling, I figured out that the SSH keys aren't accessible when an automation fires a script in the same way they are when doing it from a terminal. I suspect something wonky is going on with #DreamHost as well but I haven't gone too far in that direction yet.
Maybe tomorrow after work I'll have it working
Hmm... How do I make my #Frigate install serve my #HomeAssistant a high resolution camera stream on my #ProxMox box? Well... I guess it is actually serving a high res stream but when I do a snapshot automation, that only captures the low resolution stream...
At least I've gotten rsync working in the automation so now it uploads the snapshots to a server and yada yada. I only deleted the test website a few times getting rsync sorted out lol
Nice to see that #Proxmox 9.0 Beta finally does actually install the Intel/AMD microcode package from `non-free-firmware`.
That was a pain to add in the past and I'm convinced there's a lot of folk out there didn't know older versions of Proxmox weren't installing microcode updates by default.
I've been observing how my parents use the old Windows10 box that I'm getting ready to cycle out of production. It's supposed to be just for an #NVR but I'm seeing them use it a lot to play music onto some Bluetooth speakers outside.
I guess I need to find a new way for them to do that once I take the machine offline and replace it with a #proxmox box running #Frigate on #Debian where there won't be any way they can deal with to play music easily.
Maybe a very cheap Win11 box?
This weekend I got #proxmox running with a #Debian #docker container running #frigate and a virtual machine running #HomeAssistant on a #BeeLink #EQi12 #miniPC.
I have HA triggering a snapshot every 2 minutes and saving it locally. The next step is to get the snapshots to be on a rolling index that overwrites the old files. Then I need to figure out how to push the files up to an SFTP or similar web server.
I do have Frigate auto detecting but there's still more to do there.
(1/n)
Love the power of Proxmox. I now have a permanent System 7.6.1 instance running on my network... as well as macOS Catalina. #macos #proxmox #retrocomputing
Thinking about spinning up a secure, VLAN-isolated (and firewalled via #UniFi) VM on my #Proxmox #homelab server to act as a public-facing edge node powered by #Tailscale Funnel, custom domain, and Tailscale-issued TLS certs.
For routing multiple services (Gitea, SearXNG, blog, etc.) through Caddy, all sandboxed from my main tailnet + LAN. No open ports, no cloud VPS, no trust leaks.
Any thoughts?
Looking for a dedicated GPU for #transcoding purposes turned out to be the worst rabbit hole.
So, I'm using a AMD Ryzen 4600G in my homelab featuring #ProxmoxVE. The hardware transcoding capabilities of AMD hardware is very much behind Nvidia and #Intel, even though it isn't half as bad as expected. Anyway, the best transcoding hardware (best quality at same size/profile) are Intel devices featuring #QuickSync. Setting up another dedicated transcoding device (featuing a low power Intel APU such as the #N100) device doesn't seem to make much sense for me. There are several Intel Arc GPUs on the market and they all have pretty much the same transcoding capabilities, so I'd like to get the Intel GPU featuring the lowest power draw, especially when idling. (1/?)
Warum Cloud, wenn’s im Keller läuft? Home Assistant auf Proxmox installieren ist der Weg, um dein Smart Home lokal und sicher zu steuern. Ich zeige dir, wie du das Schritt für Schritt umsetzt. Hier geht's zur Anleitung: https://hobbyblogging.de/home-assistant-installieren #HomeAssistant #SmartHome #Proxmox
@BrideOfLinux I installed #proxmox on it and on top of that both Ubuntu and another who's name I forgot
My #homelab wiki is getting really complicated to organise and write for haha, but it's definitely getting more interesting topics like more #RaspberryPi stuffs, #Docker, and some cool stuffs like #OpenMediaVault and #HomeAssistant. I'm taking my sweet time to update them 'properly' and hope it'll all link/piece together sensibly in the end.
This is partially thanks to me embracing the fact that I just don't (yet) have the resources for a standalone 'mega' homelab (#Proxmox & #Kubernetes based) server cluster that I could simply throw everything to it, hence supplementing that setup with tinier SBC-based servers. Gives me a bit of peace of mind too that things are now more 'spread out'.
The most interesting bit will probably be when I manage to explore replicating a mini version of my #RKE2 Kubernetes cluster, on a single (or at most, two) Raspberry Pi node - maybe based on #k3s, assuming that's better. I'm just not there yet cos I'm kinda reluctant if using something like #k8s on RPi makes much sense since I'm expecting a lot of resources will be wasted that way, when hosting on Docker alone (i.e. on #Portainer) should be leaner. Anyway, if y'all wanna keep an eye on it: https://github.com/irfanhakim-as/homelab-wiki
Not even bad the latency (this is just about latency, not overall bandwidth which reaches the full 4.9Gbit via 2x 2.5Gbit links).
Taken inside a Debian VM running on a Proxmox node connected to the storage:
GMKTec G9 NAS
2x 2.5Gbit
NFS 4.2 (with pNFS)
2x WD Back SN7100 NVMe
Mirror mode ZFS
While this are already pretty awesome latencies, let's see how it performs with SPDK and NVMe-oF (TCP).
Here's my new plan for installing #GUIX. First I'm going to take the installer ISO and install on a VM on my #proxmox machine. I'll make that a VM template and clone it to a working machine. That will have no issues with nonfree kernel, so should be fine. Then ill enable #nonguix channel and substitute servers, and enable the VM to serve substitutes to the LAN. Then I'll use the VM to build an ISO and put it on a #Ventoy USB drive, so I can boot it and `guix system init` new machines.
Found this tool called Stirling PDF - big multitool setup very powerful PDF manipulation. Runs as container. 
https://github.com/Stirling-Tools/Stirling-PDF
Set it up on my #Proxmox with easy script from here -> https://homelabber.org/t/stirling-pdf-proxmox-lxc/231
