All-in-one host vs multi-host nas/homelab/domotics reddit / selfhosted ---------------------------------------------------------------------- chuckame · 2023-12-10 18:27 Hey there, I'm currently running since years the following : - home assistant+reverse proxy+ad guard (dns/dhcp) on an odroid xu4 + ssd connected (the usb-to-sata is failing multiple times per year, that's annoying) - unraid+nextcloud on a j4105-itx - seedbox in off-home dedicated server (arr suite, plex, jackett, transmission) - in the near future, mikrotik rb760igs for dhcp server+modem replacement I'm tired about the SSD management (failing 1 reboot over 2, even changing the drive or the usb adapter). My current idea would be to stop the mess, and have just 1 homelab with everything on it, with a more powerful cpu while trying to keep it power efficient. But I'm afraid about gathering everything in case of failure. In the reverse, splitting forces me to keep backups to the nas, maintain multi deployments/upgrades (haven't checked yet to ansible playbooks), and something is fully using the cpu (parity check by example), it slows all the other services! Also, unraid ui is really bad for vm & containers management, so if having all-in-one host, then management will be "funny". Any though / feedback about how to split or unify all those services? Thanks for reading, I hope this thread will help and facilitate the final home infrastructure regarding all the feedbacks! ---------------------------------------------------------------------- thekrautboy · 2023-12-10 18:48 Perfect question for /r/Homelab and maybe /r/HomeServer ---------------------------------------------------------------------- NekoLuka · 2023-12-10 18:51 I'm still building out my homelab, but it consists of a dedicated router/firewall, an hp miniserver and (soon) a 4 bay nas. I'm planning to only backup the nas, since I want to mount all the storage for my miniserver on the nas, and all the containers and router configuration are stored in a git repo. ---------------------------------------------------------------------- ericesev · 2023-12-10 19:35 My goal is to keep our home self powered (solar & battery), so I'm in the camp of as few devices as possible. Then it's a matter of reliability and how to recover from a device failure. To be honest though, I've never actually had a device fail yet (fingers crossed). Here is how I plan for it: * I use ZFS mirroring for the drives, so it can survive a single drive failure. * Some of my Docker containers are configured with RAM/CPU limits so a single service can't interfere with others. The Docker containers are also configured to restart on failure * I have alerting for things like high CPU usage, services not running, and processes crashing. * Each docker service is in its own network to prevent unintended access among the services. Services that receive data from the internet also have AppArmor policies to prevent unintended behavior. * I have both local & remote backups. * All the configuration is stored in a private git repo. I use Ansible for most of it. * I purchase duplicates of all the hardware so there is always an offline spare ready to go. ---------------------------------------------------------------------- chuckame · 2023-12-10 20:08 Done for /r/homelab ! ---------------------------------------------------------------------- chuckame · 2023-12-10 20:14 Thanks for the feedback, what is your cpu? How do you "connect" your hdds to the nuc since it's limited to 1 or 2 data ports? ---------------------------------------------------------------------- chuckame · 2023-12-10 20:16 So you are going to do nfs for the remote volumes? Why not having a local storage and then backup every days? ---------------------------------------------------------------------- ericesev · 2023-12-10 20:45 I'm using this NUC11ATKPE with the N6005 processor, 32G RAM and 2x 4T NVMe drives: [https://www.intel.com/content/www/us/en/products/sku/217668/intel- nuc-11-essential-kit-nuc11atkpe/specifications.html](https://www.intel .com/content/www/us/en/products/sku/217668/intel-nuc-11-essential-kit- nuc11atkpe/specifications.html) One NVMe is internal, the other one is in this [external](https://amazon.com/gp/product/B09Z5ZNJNP) enclosure. There is about a 20% speed loss for the external one, but it's still much faster than I actually need. All the VLANs are trunked into a single ethernet port. I only have 75/7 mbps internet service so the single port is never congested enough to slow things down. ---------------------------------------------------------------------- NekoLuka · 2023-12-10 21:45 I use Immich for saving my pictures from my phone to my server, but I also wanna be able to view those pictures again on my pc by using the nextcloud client. And as said in my other comment, it just creates one spot that needs to be backed up, since I don't care about my VM's and containers because they can be recreated in a few commands. ---------------------------------------------------------------------- p4ck3ts · 2023-12-11 07:52 proxmox ---------------------------------------------------------------------- lentzi90 · 2023-12-11 15:50 My philosophy is to have multiple identical devices (Kubernetes nodes) so that the failure of one affects me as little as possible. I use raspberry pis for this. No cluster board, no PoE or similar that would become single points of failure. Of course there is still the router but that is basic and common enough so I can find a replacement the same day if it breaks. I still have unique devices. For example one of the pis act as a NAS and has a case to match this. If this pi breaks I can swap in another in the same case though. ---------------------------------------------------------------------- chuckame · 2023-12-11 16:50 How do you manage your reverse proxy (networking between nodes)? How do you manage big storage if any (the nas raspi connected to the hdds)? ---------------------------------------------------------------------- lentzi90 · 2023-12-11 18:38 All nodes are connected to the same LAN in my case. You can do it with VPN also if you want to spread them around. Internally, there is a cluster network that ensures routing between containers. Reverse proxy in Kubernetes lingo is Ingress and is handled by an ingress controller. I have exposed it through a sort of virtual IP using Metallb. Traffic is forwarded to this VIP from the router and Metallb can move it between the nodes if needed. For storage I use the NAS pi, which has two big HDDs in raid 1 connected. They are exposed through NFS to the other nodes. Some of the other nodes also have smaller and faster SSDs for other needs. ---------------------------------------------------------------------- kmisterk · 2023-12-12 16:16 Hey, chuckame! Thanks for your submission to selfhosted. Your post has been removed due to a violation of **Rule #5a:** ## It's Not Wednesday Posts that do not directly relate to a self-hosted tool, but relate to the process of self-hosting (Including dashboard posts, support tools, hosting options, local CLI tools, etc.) are only allowed to be posted on a Wednesday. If you believe this to be incorrect, please [message the mods](https:/ /www.reddit.com/message/compose/?to=/r/selfhosted&subject=Removed For Wednesday Only Content&message=[Removed Post](https://www.reddit.com/r/selfhosted/comments/18f9uwh/-/\)) so that we can revisit or clarify the removal reason.