billwashere
- 0 Posts
- 27 Comments
Well true but I was assuming the circuits had some things drawing a little power. Flipping on a device and tripping a breaker with 12 machines on it wouldn’t be ideal :)
I have done this before in my upstairs home lab. 3 beefy ESXi machines, some nas storage, and a basic 10gbe switch eats up a lot of a single 15amp circuit. And apparently turning on a TV pushes it over the edge. Luckily the UPS saved my but while a reset the breaker and shut some stuff off.
This is only about 21 amps. Most outlets in a home are 15amps but 20amps isn’t unheard of. From one outlet doubtful but yes one house would provide that much power easily if you split them up to three or 4 rooms on different breakers.
Now it would be fun to watch his electric meter spin like a saw blade … (yes I’m old … I remember meters that had spinning discs)
Not sure if this is common knowledge but Pi-hole can also run in a docker container, it doesn’t have to be a raspberry pi. I have it running on portainer on two different machine in my house. I’m a systems architect by trade so there no kill like overkill 😅
You might be a nerd when you have to schedule maintenance at your own house.
For a DB, iscsi all day long. At work we have some of the fastest storage available on the market today (SCM drives in front of E1.L super fast SSD all connected with 100gbe mellanox switches and NICs) and it barely can keep up with the MySQL DB. NFS would absolutely work for the other use cases. But these are enterprise class systems for an entire university so yeah lots of load.
For a home system, I’m not sure it matters if the load isn’t much. I prefer iscsi because I know how it works. I use it for VMware datastores even at home. Anything that is shared storage between webservers or the like, NFS is almost required since shared iscsi storage is going to be very difficult to set up outside of something like VMware datastores since the file system is setup for multi-writers. Other filesystems like Redhat’s GFS2 or Oracle’s OCFS can do it but it’s not cheap or easy.
Tl;dr summary: my suggestion is iscsi for the DB and NFS for the other stuff.
Well it’s not “bad practice” per se but it ultimately depends on what you are trying to accomplish and what the underlying architecture is capable of supporting.
Not docker specific but we run enterprise level applications with VMWare esxi hosts accessing vm’s over an iSCSI network share and plan on trying this using NFS datastores over 100gbe with SCM and E1.L SSDs. So this should work fine but this is super fast super expensive hardware and is a lot different from homelab type architecture. Now I have done similar things at home with two esxi hosts using a Drobo for NFS datastores so I could vmotion. Was it super high performance? No. Did it work? Yes.
For a small container based environment I’d probably keep all the containers and storage for the containers local, probably on a fast SSD or NVME drive. Those are usually small. But any large media I’d NFS mount and keep that on the NAS. You can get 1TB NVME drive and pcie adapter for less than $100 on Amazon that would be way fast enough for anything in a home lab.
My 2¢… 😀
My main issue was it doesn’t play well with Macs.