MastodonTech.de

gyptazyProxLB v1.1.3 just got released!ProxLB is a VM load-balancer for your Proxmox clusters also supporting affinity & anti-affinity rules.GitHub: github.com/gyptazy/ProxLB Version 1.1.3: <a href="https://github.com/gyptazy/ProxLB/releases/tag/v1.1.3" rel="nofollow noopener" translate="no" target="_blank">https://github.com/gyptazy/ProxLB/releases/tag/v1.1.3</a><a href="https://mastodon.gyptazy.com/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> <a href="https://mastodon.gyptazy.com/tags/vmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#vmware</a> <a href="https://mastodon.gyptazy.com/tags/virtualization" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualization</a> <a href="https://mastodon.gyptazy.com/tags/ProxLB" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProxLB</a> <a href="https://mastodon.gyptazy.com/tags/loadbalancing" class="mention hashtag" rel="nofollow noopener" target="_blank">#loadbalancing</a> <a href="https://mastodon.gyptazy.com/tags/enterprise" class="mention hashtag" rel="nofollow noopener" target="_blank">#enterprise</a> <a href="https://mastodon.gyptazy.com/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://mastodon.gyptazy.com/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#ipv6</a> <a href="https://mastodon.gyptazy.com/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://mastodon.gyptazy.com/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://mastodon.gyptazy.com/tags/python3" class="mention hashtag" rel="nofollow noopener" target="_blank">#python3</a> <a href="https://mastodon.gyptazy.com/tags/proxmoxve" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmoxve</a> <a href="https://mastodon.gyptazy.com/tags/VM" class="mention hashtag" rel="nofollow noopener" target="_blank">#VM</a> <a href="https://mastodon.gyptazy.com/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPS</a> <a href="https://mastodon.gyptazy.com/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#devops</a> <a href="https://mastodon.gyptazy.com/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a>

ThomasWas haltet ihr vom Beelink ME Mini NAS mit 6 NVMe-Slots und bis zu 24 TB? Beelink bringt mit dem ME Mini ein kompaktes NAS auf den Markt, das bis zu sechs NVMe-SSDs (insgesamt 24 TB) aufnehmen kann. Es kommt mit 12 GB RAM, Intel N150 Prozessor und unterstützt verschiedene Betriebssysteme wie Windows, Proxmox und Linux. Neben zwei schnellen 2,5 Gbit/s Ethernet-Ports gibt es auch WiFi 6, Bluetooth 5.2 und mehrere USB-Anschlüsse.Mich interessiert eure Meinung: - Ist das ME Mini für euch als Selbsthoster oder Bastler interessant? - Gibt es Alternativen, die ihr bevorzugen würdet? Quelle: notebookcheck.com/beelink-me-mini-nas-mit-bis-zu-24tb-und-6-ssd-slots-jetzt-vorbestellbar.1014161.0.html<a href="https://anonsys.net/search?tag=Beelink" class="mention hashtag" rel="nofollow noopener" target="_blank">#Beelink</a> <a href="https://anonsys.net/search?tag=NAS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NAS</a> <a href="https://anonsys.net/search?tag=NVMe" class="mention hashtag" rel="nofollow noopener" target="_blank">#NVMe</a> <a href="https://anonsys.net/search?tag=Selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Selfhosting</a> <a href="https://anonsys.net/search?tag=Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://anonsys.net/search?tag=Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> <a href="https://anonsys.net/search?tag=MiniPC" class="mention hashtag" rel="nofollow noopener" target="_blank">#MiniPC</a> <a href="https://anonsys.net/search?tag=Frage" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frage</a>

Chris :damnified:Die Aussage vom <a href="https://metalhead.club/tags/Broadcom" class="mention hashtag" rel="nofollow noopener" target="_blank">#Broadcom</a> CTO in EMEA, dass der Preis fuer VMware zu hoch sei, weil viele nicht alle Features nutzen finde ich witzig. Ich stelle mir vor, ich bin ein Unternehmen nutzte vorher alle Features von <a href="https://metalhead.club/tags/VMware" class="mention hashtag" rel="nofollow noopener" target="_blank">#VMware</a> z.b. von vSphere und muss jetzt 150% mehr bezahlen ... dann habe ich den kompletten Vendor-Lock-In und komme so schnell nicht weg und muss einfach nur mehr zahlen. Schoene neue Welt und schoene Ansichten werden hier versucht runterzuspielen. Source: <a href="https://www.golem.de/news/vmware-broadcom-liefert-einfache-antwort-auf-preiskritik-2506-197329.html" rel="nofollow noopener" translate="no" target="_blank">https://www.golem.de/news/vmware-broadcom-liefert-einfache-antwort-auf-preiskritik-2506-197329.html</a>Mein Hint: <a href="https://metalhead.club/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a>, <a href="https://metalhead.club/tags/kvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#kvm</a>, <a href="https://metalhead.club/tags/hypervisor" class="mention hashtag" rel="nofollow noopener" target="_blank">#hypervisor</a>

RonaldWie man so den Feiertag verbringt: Neben dem Stress mit dem Handy habe ich einen <a href="https://brettspiel.space/tags/Cluster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cluster</a> aus drei Nodes im <a href="https://brettspiel.space/tags/Homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#Homelab</a> gebaut. <a href="https://brettspiel.space/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> kannte ich schon, verclustert habe ich noch nicht draus gebastelt. Und <a href="https://brettspiel.space/tags/Ceph" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ceph</a> ist für mich noch Neuland. Es gibt noch viel zu entdecken... 🤓

gyptazy<a href="https://mastodon.gyptazy.com/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> Cluster Creation with the New <a href="https://mastodon.gyptazy.com/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a> Module `proxmox_cluster`.<a href="https://gyptazy.com/from-scripted-chaos-to-clean-api-proxmox-cluster-setup-with-ansible-done-right-with-the-new-proxmox_cluster-module/" rel="nofollow noopener" translate="no" target="_blank">https://gyptazy.com/from-scripted-chaos-to-clean-api-proxmox-cluster-setup-with-ansible-done-right-with-the-new-proxmox_cluster-module/</a>

Larvitz :fedora: :redhat:Little trick:Server backup by using proxmox-backup-client inside a Linux container by running it with podman :podman: . Volume-mounting the entire root-fs of the server into the container read-only:[root@argon ~]# sudo podman run --rm --name pbs-backup-job \ --security-opt label=type:spc_t \ --hostname argon \ --entrypoint /usr/bin/proxmox-backup-client \ --secret pbs_repo_password,type=env,target=PBS_PASSWORD \ --secret pbs_key_passphrase,type=env,target=PBS_ENCRYPTION_PASSWORD \ -v /:/mnt/root:ro \ -v /root/argon-backup.key:/etc/proxmox/argon-backup.key:ro,Z \ docker.io/ayufan/proxmox-backup-server:latest \ backup root.pxar:/mnt/root --repository backup@pbs@neon.edelga.se:data --keyfile /etc/proxmox/argon-backup.keyWorks incredibly well :-) <a href="https://burningboard.net/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://burningboard.net/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysadmin</a> <a href="https://burningboard.net/tags/containers" class="mention hashtag" rel="nofollow noopener" target="_blank">#containers</a> <a href="https://burningboard.net/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> <a href="https://burningboard.net/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmox</a>

gyptazySome insights how my BoxyBSD project for the BSD Community boosted the Proxmox ecosystem and let me create several tools that were simply missing.<a href="https://mastodon.gyptazy.com/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> <a href="https://mastodon.gyptazy.com/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://mastodon.gyptazy.com/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.gyptazy.com/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#NetBSD</a> <a href="https://mastodon.gyptazy.com/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a> <a href="https://mastodon.gyptazy.com/tags/RUNBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#RUNBSD</a> <a href="https://mastodon.gyptazy.com/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a> <a href="https://mastodon.gyptazy.com/tags/ProxLB" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProxLB</a> <a href="https://mastodon.gyptazy.com/tags/Community" class="mention hashtag" rel="nofollow noopener" target="_blank">#Community</a> <a href="https://mastodon.gyptazy.com/tags/BSDCan" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSDCan</a> <a href="https://mastodon.gyptazy.com/tags/Hosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hosting</a> <a href="https://mastodon.gyptazy.com/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPS</a> <a href="https://gyptazy.com/how-my-boxybsd-project-boosted-the-proxmox-ecosystem/" rel="nofollow noopener" translate="no" target="_blank">https://gyptazy.com/how-my-boxybsd-project-boosted-the-proxmox-ecosystem/</a>

Martin PughThe evenings this week have been a bit of an adventure with the home lab. I'm migrating a number of random services onto a pair of new VM's, one on each of my two Proxmox hosts. They'll become DNS servers (authoritative using nsd and recursive using Unbound), including basic DNS filtering of the bad stuff as well as DNS64/NAT64 services so I can move to more IPv6 mostly systems at home. They'll probably also pickup NTP and any other services that make sense along the way.My challenge has been to perform as much of the setup as possible using Ansible. I'm still very much a beginner but I seem to be making good progress. I've been fighting with NSD/Unbound and reverse DNS but after a couple of days that's on hold. Forward resolution is working so I've moved some of the home VLAN's over to add some load. Holy crap they are fast. There's a little delay for a new site not in the cache but it soon picks up. It feels like an order of magnitude faster than my venerable pi 3b+ running pihole with the same DNS filtered list.I'll crack the reverse DNS stuff at some point and now I've realised the reason I couldn't restart NSD after a change (so I was rebooting the VM) was because I didn't realise the "remote control" options are also needed for local control on the VM, it's a lot faster to get updates on place. More work tomorrow night on the Ansible playbook with some better tags to manage operations without updating everything.<a href="https://bsd.network/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a> <a href="https://bsd.network/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a> <a href="https://bsd.network/tags/Unbound" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unbound</a> <a href="https://bsd.network/tags/nsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#nsd</a> <a href="https://bsd.network/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> <a href="https://bsd.network/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#ipv6</a> <a href="https://bsd.network/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a>

alsterRecovery mit Proxmox, wenn mal ne Platte ausfällt und man die Backups auf nen anderen Host ziehen will geht echt super. Migration direkt ging nicht, weil das eine zfs hat und der andere nicht. Das mögen die wohl nicht so. Was aber geht: Backup machen, alle Daten zu dem gerade erstellten Backup mit scp oder sowas von einem Host (liegen in /var/lib/vz/dump/ ) auf den anderen ziehen und dann aus dem Backup wiederherstellen und dabei das zfs auswählen. Starten, fertig. Und ja, das war auch noch von Proxmox VE 7 auf Proxmox VE 8. <a class="hashtag" href="https://akkoma.alster.space/tag/proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a>

Hobbyblogging.deMal ehrlich, die Installation von Home Assistant kann eine ziemliche Herausforderung sein, besonders wenn man nicht weiß, wo man ansetzen soll. Ich hab's für mich getestet und empfehle eine virtuelle Maschine auf Proxmox. Schneller und effizienter geht’s nicht! <a href="https://hobbyblogging.de/home-assistant-installieren" rel="nofollow noopener" translate="no" target="_blank">https://hobbyblogging.de/home-assistant-installieren</a> <a href="https://mastodon.social/tags/HomeAssistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeAssistant</a> <a href="https://mastodon.social/tags/SmartHome" class="mention hashtag" rel="nofollow noopener" target="_blank">#SmartHome</a> <a href="https://mastodon.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> <a href="https://mastodon.social/tags/Automation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Automation</a>

AS 396507We've been hard at work the past few months!1. Leaving the Westin datacenter in downtown Seattle and moving on from expensive co-location2. Moving our gear to Fremont, California3. Bringing on board a few new Advisory Board members, including <a href="https://disobey.net/@whil" class="u-url mention" rel="nofollow noopener" target="_blank">@whil</a> who has been an incredible help deploying our <a href="https://disobey.net/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> infrastructure, and <a href="https://infosec.exchange/@alexhaydock" class="u-url mention" rel="nofollow noopener" target="_blank">@alexhaydock</a> who has been instrumental in deploying our new <a href="https://disobey.net/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a> infra, new recursive <a href="https://disobey.net/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> resolution infra, and new <a href="https://disobey.net/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> exit relays in California! See: <a href="https://infosec.exchange/@alexhaydock/114687688286984967" rel="nofollow noopener" translate="no" target="_blank">https://infosec.exchange/@alexhaydock/114687688286984967</a> with more updates to follow4. Installing new co-location with some older low-power systems in Amsterdam for our self-hosted <a href="https://disobey.net/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> infra @ <a href="https://disobey.net" rel="nofollow noopener" translate="no" target="_blank">https://disobey.net</a>, where we just moved our <a href="https://disobey.net/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a> profile to!5. Deploying a new <a href="https://disobey.net/tags/XMTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMTP</a> node @ <a href="https://xmtp.disobey.net" rel="nofollow noopener" translate="no" target="_blank">https://xmtp.disobey.net</a>, and testing a new <a href="https://disobey.net/tags/DeltaChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeltaChat</a> relay!6. Deploying some new <a href="https://disobey.net/tags/obfs4" class="mention hashtag" rel="nofollow noopener" target="_blank">#obfs4</a> private bridges for use in a country who's conducting heavy internet surveillance and censorship, blocking access to <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> and today is our birthday!!! we're 8 years old today ^_^ stay tuned for more updates to come!

Da lazy beardudeI can't believe I've been running PiHole on the network for 2 years and a month now.I asked the people at our home if they noticed anything and they said they had some trouble accessing very few websites. I just said they're probably malicious domains but otherwise, they noticed ads are gone.I told them it's for security and privacy purposes. It's also to prevent them form being scammed. Don't want them getting scammed out of their money..<a href="https://mastodon.social/tags/pihole" class="mention hashtag" rel="nofollow noopener" target="_blank">#pihole</a> <a href="https://mastodon.social/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> <a href="https://mastodon.social/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmox</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>

Dendrobatus Azureus<a href="https://mastodon.bsd.cafe/tags/Hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hardware</a> <a href="https://mastodon.bsd.cafe/tags/failure" class="mention hashtag" rel="nofollow noopener" target="_blank">#failure</a> <a href="https://mastodon.bsd.cafe/tags/Gigabyte" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gigabyte</a> <a href="https://mastodon.bsd.cafe/tags/enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#enshittification</a> <a href="https://mastodon.bsd.cafe/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.bsd.cafe/tags/remote" class="mention hashtag" rel="nofollow noopener" target="_blank">#remote</a> <a href="https://mastodon.bsd.cafe/tags/servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#servers</a> <a href="https://mastodon.bsd.cafe/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> <a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

Crazy-to-Bike<a href="https://brettspiel.space/@deloco" class="u-url mention" rel="nofollow noopener" target="_blank">@deloco@brettspiel.space</a> Basteln ist das eine, der Stromverbrauch das andere. Wäre mir too much. Bin gerade dabei alles auf ein <a href="https://fediworld.de/tags/Ugreen" rel="nofollow noopener" target="_blank">#Ugreen</a> <a href="https://fediworld.de/tags/NAS" rel="nofollow noopener" target="_blank">#NAS</a> mit 2x M.2 und 2x SATA umzuplanen. Darauf <a href="https://fediworld.de/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a>, <a href="https://fediworld.de/tags/VMs" rel="nofollow noopener" target="_blank">#VMs</a> mit <a href="https://fediworld.de/tags/TrueNAS" rel="nofollow noopener" target="_blank">#TrueNAS</a>, <a href="https://fediworld.de/tags/HomeAssistant" rel="nofollow noopener" target="_blank">#HomeAssistant</a> und was sonst so gebraucht wird. M.2 und SATA im ZFS Z1 RAID, Backup dann nur extern von den Daten und VMs. Dabei eher kein <a href="https://fediworld.de/tags/PBS" rel="nofollow noopener" target="_blank">#PBS</a>, um keinen weiteren <a href="https://fediworld.de/tags/Server" rel="nofollow noopener" target="_blank">#Server</a> zu brauchen.

Crazy-to-Bike<a href="https://bunt.social/@blog_reloaded" class="u-url mention" rel="nofollow noopener" target="_blank">@blog_reloaded@bunt.social</a> <a href="https://peering.social/@tioan" class="u-url mention" rel="nofollow noopener" target="_blank">@tioan@peering.social</a> Das Entscheidendste ist natürlich, dass das <a href="https://fediworld.de/tags/Datengrab" rel="nofollow noopener" target="_blank">#Datengrab</a> und die <a href="https://fediworld.de/tags/Backups" rel="nofollow noopener" target="_blank">#Backups</a> der <a href="https://fediworld.de/tags/Rechner" rel="nofollow noopener" target="_blank">#Rechner</a> in eimem verschlüsselten <a href="https://fediworld.de/tags/Volume" rel="nofollow noopener" target="_blank">#Volume</a> / <a href="https://fediworld.de/tags/Partition" rel="nofollow noopener" target="_blank">#Partition</a> liegen. Grundsätzlich will ich <a href="https://fediworld.de/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a> und die VMs auf die M.2 packen und die beiden HDs an die VM mit z.B. <a href="https://fediworld.de/tags/TrueNAS" rel="nofollow noopener" target="_blank">#TrueNAS</a> als Datenspeicher durchreichen. Ich habe TrueNAS noch nicht verwendet, aber wenn ich aus den HDs unter Proxmox ein RAIDZ 1 machen, dieses dann TrueNAS als Datenspeicher zur Verfügung stellen kann und TrueNAS darin ein LUKS verschlüsseltes Volume machen kann, wäre das ok und easy.

Crazy-to-Bike<a href="https://peering.social/@tioan" class="u-url mention" rel="nofollow noopener" target="_blank">@tioan@peering.social</a> Aber wie unlocke ich die automatisch? Was meinst du mit Privatkopie? Ah, gerade was gefunden: <a href="https://schroederdennis.de/storage/proxmox-backup-server-mit-verschluesselten-zfs-dataset/" rel="nofollow noopener" target="_blank">https://schroederdennis.de/storage/proxmox-backup-server-mit-verschluesselten-zfs-dataset/</a> Was für den <a href="https://fediworld.de/tags/PBS" rel="nofollow noopener" target="_blank">#PBS</a> geht, sollte ja auch für <a href="https://fediworld.de/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a> selbst gehen. Und <a href="https://blog.berrnd.de/proxmox-voll-verschluesselt-luks-lvm-dropbear-initramfs" rel="nofollow noopener" target="_blank">https://blog.berrnd.de/proxmox-voll-verschluesselt-luks-lvm-dropbear-initramfs</a> Dann wäre Proxmox auf den M.2 verschlüsselt und das <a href="https://fediworld.de/tags/Dataset" rel="nofollow noopener" target="_blank">#Dataset</a> auf den HDs auch und ich kann Proxmox remote und das Dataset automatisch entschlüsseln. Die VMs selbst müssen dann ja gar nicht mehr verschlüsselt werden. Allerdings laufen die M.2 so nicht mit einem <a href="https://fediworld.de/tags/ZFS" rel="nofollow noopener" target="_blank">#ZFS</a> RAID 1 🤔

Crazy-to-Bike<a href="https://peering.social/@tioan" class="u-url mention" rel="nofollow noopener" target="_blank">@tioan@peering.social</a> Was ich da allerdings nicht bedacht habe: Bei mir ist jede <a href="https://fediworld.de/tags/Festplatte" rel="nofollow noopener" target="_blank">#Festplatte</a> in jedem <a href="https://fediworld.de/tags/Rechner" rel="nofollow noopener" target="_blank">#Rechner</a> und auch die <a href="https://fediworld.de/tags/HD" rel="nofollow noopener" target="_blank">#HD</a> im <a href="https://fediworld.de/tags/QNAP" rel="nofollow noopener" target="_blank">#QNAP</a> <a href="https://fediworld.de/tags/NAS" rel="nofollow noopener" target="_blank">#NAS</a> voll <a href="https://fediworld.de/tags/verschlüsselt" rel="nofollow noopener" target="_blank">#verschlüsselt</a>. Das soll zwingend auch so bleiben. Grundsätzlich geht das wohl auch mit <a href="https://fediworld.de/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a> / bei <a href="https://fediworld.de/tags/ZFS" rel="nofollow noopener" target="_blank">#ZFS</a>, kostet aber wohl deutlich <a href="https://fediworld.de/tags/Performance" rel="nofollow noopener" target="_blank">#Performance</a> und ist etwas komplex, da man u.a. immer händisch entschlüsseln muss. Hm... 🤔

nullbyte-fullbyte👋 Hi Fediverse! I’m Martin — project manager with a focus on cybersecurity, IT/OT convergence, and systems thinking. Exploring resilient infrastructure, compliance frameworks, and hands-on learning in my homelab.Expect posts on <a href="https://mastodon.world/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurity</a> <a href="https://mastodon.world/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> <a href="https://mastodon.world/tags/SystemsThinking" class="mention hashtag" rel="nofollow noopener" target="_blank">#SystemsThinking</a> <a href="https://mastodon.world/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://mastodon.world/tags/Compliance" class="mention hashtag" rel="nofollow noopener" target="_blank">#Compliance</a>.Let’s connect and share thoughts!

Crazy-to-Bike<a href="https://peering.social/@tioan" class="u-url mention" rel="nofollow noopener" target="_blank">@tioan@peering.social</a> So ungefähr stelle ich mir das auch vor: OS auf 2 NVME im RAID 1, dazu das <a href="https://fediworld.de/tags/Datengrab" rel="nofollow noopener" target="_blank">#Datengrab</a> auf HD, mittelfristig dann - zusätzlich zu einem echten Backup - ebenfalls als RAID 1. Die <a href="https://fediworld.de/tags/RAID" rel="nofollow noopener" target="_blank">#RAID</a> würde ich mittels <a href="https://fediworld.de/tags/ZFS" rel="nofollow noopener" target="_blank">#ZFS</a> machen. Als OS käme wahrscheinlich <a href="https://fediworld.de/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a> zum Einsatz. Das habe ich früher schon mal beruflich eingesetzt, bin also etwas damit vertraut, auch wenn sich da inzwischen viel getan hat (so eben ZFS). Dann kommt in eine <a href="https://fediworld.de/tags/VM" rel="nofollow noopener" target="_blank">#VM</a> <a href="https://fediworld.de/tags/HomeAssistant" rel="nofollow noopener" target="_blank">#HomeAssistant</a> und in eine andere VM z.B. <a href="https://fediworld.de/tags/TrueNAS" rel="nofollow noopener" target="_blank">#TrueNAS</a>, an das ich das Datengrab durchreiche. Dann spare ich mir, händisch <a href="https://fediworld.de/tags/Freigaben" rel="nofollow noopener" target="_blank">#Freigaben</a> über <a href="https://fediworld.de/tags/Samba" rel="nofollow noopener" target="_blank">#Samba</a> zu erstellen und das ganze <a href="https://fediworld.de/tags/Usermanagenent" rel="nofollow noopener" target="_blank">#Usermanagenent</a> auf der Konsole.

Florian Haller-CasagrandeBonjour le Fédivers !<a href="https://piaille.fr/tags/JeRecrute" class="mention hashtag" rel="nofollow noopener" target="_blank">#JeRecrute</a> un⸱e sysadmin chez <a href="https://piaille.fr/tags/3Liz" class="mention hashtag" rel="nofollow noopener" target="_blank">#3Liz</a>, ça vous intéresse ?Au menu : du <a href="https://piaille.fr/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>, du <a href="https://piaille.fr/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a>, du <a href="https://piaille.fr/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a>, du <a href="https://piaille.fr/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a>, du <a href="https://piaille.fr/tags/Lizmap" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lizmap</a>, du <a href="https://piaille.fr/tags/QGIS" class="mention hashtag" rel="nofollow noopener" target="_blank">#QGIS</a> et pas mal d'autres petites choses !En priorité dans la région de Vannes (56) mais on reste ouverts (le télétravail fait partie de notre ADN !).=> <a href="https://www.linkedin.com/jobs/view/4248435284/" rel="nofollow noopener" translate="no" target="_blank">https://www.linkedin.com/jobs/view/4248435284/</a>ou=> (pdf) <a href="https://office.3liz.com/s/WRW8sLYwAWiL25L" rel="nofollow noopener" translate="no" target="_blank">https://office.3liz.com/s/WRW8sLYwAWiL25L</a>N'hésitez pas à faire tourner ! :boost_request:

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#proxmox