home.social

#minilab — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #minilab, aggregated by home.social.

  1. Neue Episode ist raus!

    150 Nerds und eine Torte (SFW)

    Hier der Link: podcast.smarthuette.de/episode

    #homeassistant #selfhosting #homelab #meetup #community #bufferbloat #unifi #mikrotik #minilab #makerfaire

    Wir berichten vom HA Meetup in Köln und blicken voraus auf die Maker Faire Ruhr. Andrej macht sich sein Leben als Wanderkünstler leichter und Thomas sagt dem Bufferbloat den Kampf an. Dazu werfen wir noch einen Blick auf HA 2026.2 und widmen uns dann, gut geladen, den Rantthemen.

    Viel Spaß!

  2. Neue Episode ist raus!

    150 Nerds und eine Torte (SFW)

    Hier der Link: podcast.smarthuette.de/episode

    #homeassistant #selfhosting #homelab #meetup #community #bufferbloat #unifi #mikrotik #minilab #makerfaire

    Wir berichten vom HA Meetup in Köln und blicken voraus auf die Maker Faire Ruhr. Andrej macht sich sein Leben als Wanderkünstler leichter und Thomas sagt dem Bufferbloat den Kampf an. Dazu werfen wir noch einen Blick auf HA 2026.2 und widmen uns dann, gut geladen, den Rantthemen.

    Viel Spaß!

  3. Das #Minilab ist erstmal fertig 😁. #Proxmox ist installiert und der #Cluster konfiguriert. Angebunden ist das Rack erstmal per WLAN. Mal schauen, ob ich das noch ändere. Die Alternative wäre, dort wo es aktuell steht, nur DLAN 🫣
    #homelab #minirack #minipc #ubiquiti

  4. Das #Minilab ist erstmal fertig 😁. #Proxmox ist installiert und der #Cluster konfiguriert. Angebunden ist das Rack erstmal per WLAN. Mal schauen, ob ich das noch ändere. Die Alternative wäre, dort wo es aktuell steht, nur DLAN 🫣
    #homelab #minirack #minipc #ubiquiti

  5. @timm Das #Minilab wird ein Cluster, wobei das nur zum Testen da ist. Prod. sind hier ein #Minisforum MS-01 (Core 19, 64GB RAM, 2TB NVMe) und im Wesentlichen eine #Synology DS923+

    #Nextcloud läuft im #Docker Container in einer VM, in der auch weitere Dienste (#Immich) laufen. Ich finde das Backup so einfacher (#Proxmox Backup Server). In dieser VM Disk sind auch nur Dateien gepeichert. Die DB ist auf einer VM Disk auf der SSD des Hosts. Das wäre ansonsten ein Performance Killer 😉

  6. @timm Das #Minilab wird ein Cluster, wobei das nur zum Testen da ist. Prod. sind hier ein #Minisforum MS-01 (Core 19, 64GB RAM, 2TB NVMe) und im Wesentlichen eine #Synology DS923+

    #Nextcloud läuft im #Docker Container in einer VM, in der auch weitere Dienste (#Immich) laufen. Ich finde das Backup so einfacher (#Proxmox Backup Server). In dieser VM Disk sind auch nur Dateien gepeichert. Die DB ist auf einer VM Disk auf der SSD des Hosts. Das wäre ansonsten ein Performance Killer 😉

  7. @timm
    #Minilab: 3x HP Elitedesk G2 Mini (Core i5, 8GB RAM, 256GB SSD), Ubiquiti Flex Mini 2.5G, Rack: #DeskPi Rackmate T0. Netzwerk kommt von einer #UDMPro.

    #Nextcloud: 1x Lenovo ThinkCentre Tiny m920q (Core i5, 16GB RAM, 256GB SSD). Darauf läuft #Proxmox, Nextcloud ist eine VM. Als Storage ist eine ältere Synology via NFS angebunden. Dort liegt auch die virt. HDD, auf der die Daten liegen.

  8. @timm
    #Minilab: 3x HP Elitedesk G2 Mini (Core i5, 8GB RAM, 256GB SSD), Ubiquiti Flex Mini 2.5G, Rack: #DeskPi Rackmate T0. Netzwerk kommt von einer #UDMPro.

    #Nextcloud: 1x Lenovo ThinkCentre Tiny m920q (Core i5, 16GB RAM, 256GB SSD). Darauf läuft #Proxmox, Nextcloud ist eine VM. Als Storage ist eine ältere Synology via NFS angebunden. Dort liegt auch die virt. HDD, auf der die Daten liegen.

  9. @timm
    #Minilab: 3x HP Elitedesk G2 Mini (Core i5, 8GB RAM, 256GB SSD), Ubiquiti Flex Mini 2.5G, Rack: #DeskPi Rackmate T0. Netzwerk kommt von einer #UDMPro.

    #Nextcloud: 1x Lenovo ThinkCentre Tiny m920q (Core i5, 16GB RAM, 256GB SSD). Darauf läuft #Proxmox, Nextcloud ist eine VM. Als Storage ist eine ältere Synology via NFS angebunden. Dort liegt auch die virt. HDD, auf der die Daten liegen.

  10. @timm Hi, welches meinst du? Das #Minilab oder die #Nextcloud für meinen Vater? Oder was anderes? Sorry, hab gerade ein paar Dinge parallel laufen 😉

  11. @timm Hi, welches meinst du? Das #Minilab oder die #Nextcloud für meinen Vater? Oder was anderes? Sorry, hab gerade ein paar Dinge parallel laufen 😉

  12. Das #Minilab nimmt ein wenig mehr Form an. Gerade habe ich die Netzteile untergebracht. War alles nicht so einfach, aber jetzt ist alles verstaut 🙂. Der Switch ist auf das Rack gewandert und dort befestigt.
    #homelab

  13. Das #Minilab nimmt ein wenig mehr Form an. Gerade habe ich die Netzteile untergebracht. War alles nicht so einfach, aber jetzt ist alles verstaut 🙂. Der Switch ist auf das Rack gewandert und dort befestigt.
    #homelab

  14. Die erste Anprobe ist ganz ok. Ich würde gern jeden HP Mini in einen separaten #DeskPi Rackmount montieren, bin aber wahrscheinlich zu geizig. Auch bei der Stromversorgung bin ich mir noch nicht sicher. Es gibt eine 4-fach 10 Zoll Leiste von Digitus, aber ich fürchte, dass sie zu tief ist. #homelab #minilab

  15. Die erste Anprobe ist ganz ok. Ich würde gern jeden HP Mini in einen separaten #DeskPi Rackmount montieren, bin aber wahrscheinlich zu geizig. Auch bei der Stromversorgung bin ich mir noch nicht sicher. Es gibt eine 4-fach 10 Zoll Leiste von Digitus, aber ich fürchte, dass sie zu tief ist. #homelab #minilab

  16. What’s one to do when you want to play a DJ set but you don’t have a power point?
    Here’s some photos of an initial build of a solar powered audio amplifier and Pioneer DDJ-FLX10 power supply in an 8U mini rack!

    2700kelvin.house/2025/10/a-sol

    #minirack #homelab #3dprinting #minilab #audiophile #dj #solar #sydney #australia

  17. Ok so I'm seeing some curious issues with this ceph cluster and either I have a config issue, or a core misunderstanding that I really should address before I build out further

    I have 8 hdd disks across 4 nodes, and in rook they're dust assigned to a 4+2 EC pool.

    I had thought it would spread the data over all 8 drives eventually

    But in
    ceph pg dump I see two drives missing.

    * maybe it just grabs the he first 6 that it sees and leaves those two alone? Would it swap in drives as a hot spare?
    * Or maybe I had a hiccup and they didn't get assigned for some other reason?
    * Maybe I should reset it and re-create with 5+3 EC?
    * The two drives in question have basically no data usage but they're not errored out
    #Homelab #Ceph #Kubernetes #Minilab

  18. Ok so I'm seeing some curious issues with this ceph cluster and either I have a config issue, or a core misunderstanding that I really should address before I build out further

    I have 8 hdd disks across 4 nodes, and in rook they're dust assigned to a 4+2 EC pool.

    I had thought it would spread the data over all 8 drives eventually

    But in
    ceph pg dump I see two drives missing.

    * maybe it just grabs the he first 6 that it sees and leaves those two alone? Would it swap in drives as a hot spare?
    * Or maybe I had a hiccup and they didn't get assigned for some other reason?
    * Maybe I should reset it and re-create with 5+3 EC?
    * The two drives in question have basically no data usage but they're not errored out
    #Homelab #Ceph #Kubernetes #Minilab

  19. All drives have been added physically, now to figure out how the heck I'm going to build the pools and then transfer data over

    Current plan:
    * I have 8 disks, so I'm thinking 4+2 EC pool with the HDDs only, ODD failure domain because I just don't have enough hosts
    * I think I can update Ceph and tell it to add the new HDDs as blank OSDs pretty easily
    * Then I can add a new pool ? Maybe I'm a little fuzzy on terms. Goal is to run CephFS on this pool.
    * Then I'll create the base CephFS volumes. I'm thinking I'll create a new namespace and add the PVCs there first. I'll back things up via this namespace.
    * Then I can create new CephFS vols/PVCs in each namespace that also needs access
    * I should be able to do some of the basic copy operations by just more bring NFS and CephFS at the same time in a pod? Maybe. That or I expose CephFS outside of the cluster and mount it directly on the NAS itself.

    #Homelab #Ceph #Kubernetes #Minilab

  20. All drives have been added physically, now to figure out how the heck I'm going to build the pools and then transfer data over

    Current plan:
    * I have 8 disks, so I'm thinking 4+2 EC pool with the HDDs only, ODD failure domain because I just don't have enough hosts
    * I think I can update Ceph and tell it to add the new HDDs as blank OSDs pretty easily
    * Then I can add a new pool ? Maybe I'm a little fuzzy on terms. Goal is to run CephFS on this pool.
    * Then I'll create the base CephFS volumes. I'm thinking I'll create a new namespace and add the PVCs there first. I'll back things up via this namespace.
    * Then I can create new CephFS vols/PVCs in each namespace that also needs access
    * I should be able to do some of the basic copy operations by just more bring NFS and CephFS at the same time in a pod? Maybe. That or I expose CephFS outside of the cluster and mount it directly on the NAS itself.

    #Homelab #Ceph #Kubernetes #Minilab

  21. Cluster rebuild project:

    This isn't yak shaving, this is something else entirely

    The goal: move all bulk storage off of the old NAS and onto a 3.5in HDD Ceph pool in the Minilab (plan is 4 nodes 8 disks 4+2 EC pool with osd failure domain). Most of the bulk data will be in CephFS. I plan to add a samba container for access by windows for misc uses as needed.

    What needs to be accomplished to get there:

    * Data needs to transfer and performance tested from each application it will be utilizer
    * The HDD ool needs to be installed and built
    * Before that I need to be confident of backups, Velero is working but it is failing on CephFS specifically and I'm not sure why. I'm able to manually take CephFS volume snapshots? Uggggggggh.
    * Great now the Ceph mgrs are xrashing. The only errors I see are OOMKills but the nodes aren't close to our of memory any I haven't found anything else in the logs

    So now I'm troubleshooting a pop-up event before the unclear backup issue before I can even get started on migrating the data.

    With trip planning happening I probably won't have much progress until late Aug at best. The goal is to have this done and tested including backups before mid Nov.

    #Homelab #Ceph #Kubernetes #Minilab

  22. Cluster rebuild project:

    This isn't yak shaving, this is something else entirely

    The goal: move all bulk storage off of the old NAS and onto a 3.5in HDD Ceph pool in the Minilab (plan is 4 nodes 8 disks 4+2 EC pool with osd failure domain). Most of the bulk data will be in CephFS. I plan to add a samba container for access by windows for misc uses as needed.

    What needs to be accomplished to get there:

    * Data needs to transfer and performance tested from each application it will be utilizer
    * The HDD ool needs to be installed and built
    * Before that I need to be confident of backups, Velero is working but it is failing on CephFS specifically and I'm not sure why. I'm able to manually take CephFS volume snapshots? Uggggggggh.
    * Great now the Ceph mgrs are xrashing. The only errors I see are OOMKills but the nodes aren't close to our of memory any I haven't found anything else in the logs

    So now I'm troubleshooting a pop-up event before the unclear backup issue before I can even get started on migrating the data.

    With trip planning happening I probably won't have much progress until late Aug at best. The goal is to have this done and tested including backups before mid Nov.

    #Homelab #Ceph #Kubernetes #Minilab

  23. Overview of cluster specs:

    Networking:
    * Mikrotik RB5009Upr+S+in
    * Mikrotik CRS310-5s-4s+in
    * Mikrotik CRS310-8g+2s+in (rear mounted)
    * Cable modem (pending move into rack)
    * 1x raspberry pi 4 running dnsmasq for DHCP/DNS, with a second acting as a coldish spare

    Compute:
    * 1x Intel core ultra 235 system with Nvidia p4 and 32gb ram, general compute
    * 4x odroid H4s ultra with 1x NVMe boot, 2x 800gb, ssd 2x 22tb HDD (pending)

    Each node has 1x 2.5gb link to the rear CRS310 with room to LACP the odroids if I need to upgrade networking.

    Software: The cluster nodes are all running bare metal Talos. Three odroids act as control plane+storage, the fourth acts as a storage+compute, and the Intel core ultra is pure compute. There are/will be multiple Ceph storage pools for different use cases. This was the smallest Ceph that I felt ok with. Ceph people really suggest larger clusters than this so we'll see how it goes. That is also why I'm stalled until I get backups working fully.


    #Homelab #Ceph #Kubernetes #Minilab

  24. Overview of cluster specs:

    Networking:
    * Mikrotik RB5009Upr+S+in
    * Mikrotik CRS310-5s-4s+in
    * Mikrotik CRS310-8g+2s+in (rear mounted)
    * Cable modem (pending move into rack)
    * 1x raspberry pi 4 running dnsmasq for DHCP/DNS, with a second acting as a coldish spare

    Compute:
    * 1x Intel core ultra 235 system with Nvidia p4 and 32gb ram, general compute
    * 4x odroid H4s ultra with 1x NVMe boot, 2x 800gb, ssd 2x 22tb HDD (pending)

    Each node has 1x 2.5gb link to the rear CRS310 with room to LACP the odroids if I need to upgrade networking.

    Software: The cluster nodes are all running bare metal Talos. Three odroids act as control plane+storage, the fourth acts as a storage+compute, and the Intel core ultra is pure compute. There are/will be multiple Ceph storage pools for different use cases. This was the smallest Ceph that I felt ok with. Ceph people really suggest larger clusters than this so we'll see how it goes. That is also why I'm stalled until I get backups working fully.


    #Homelab #Ceph #Kubernetes #Minilab

  25. Physical test fit is good!

    (The 3.5in drives are not populated yet)
    #Homelab #Ceph #Kubernetes #Minilab

  26. Physical test fit is good!

    (The 3.5in drives are not populated yet)
    #Homelab #Ceph #Kubernetes #Minilab