I love my Synology DS1618 - it’s a bit older now, but the 10Gbps is a delight.
— GPG Proofs —
This is an OpenPGP proof that connects my OpenPGP key to this Lemmy account. For details check out https://keyoxide.org/guides/openpgp-proofs
[ Verifying my OpenPGP key: openpgp4fpr:27265882624f80fe7deb8b2bca75b6ec61a21f8f ]
I love my Synology DS1618 - it’s a bit older now, but the 10Gbps is a delight.
I want to move my 4x SFP+ from their current MicroTik switch to my new Brocade. Then I’m very strongly debating running both VM and Ceph over the same 10Gbps connections, removing the ugly USB Ethernet dongles from my three Proxmox Lenovo M920q boxes.
After that? Maybe look at finally migrating Vault off my ClusterHat to Kubernetes.
Don’t forget sweetheart tax breaks from local municipalities on real estate!
Sure you can have this huge complex company, because we know the 1500 people who work from the office will frequent the local Subway for lunch and that’s sales tax!
The only thing worse than someone saying just Google it is an op replying to their own post saying, never mind fixed it! (Without actually saying the solution).
Same here - they finally said in a recent email how many of those pictures were at risk… 2. Just two pictures. Fuck off Photobucket.
IIRC, Ralph Wilson (it’s correct name and I will not accept any others) has a huge screen that can be used for parking lot viewing in warmer months.
Probably not worth the liability for blizzard conditions though.
Yeah, but they are the ones let go when the stock tumbles.
And hey, bonus - prison labor is basically free !
Ceph is… fine. I feel like I don’t know it enough to properly maintain it. I only went with 10gbe because I was basically told on a homelab reddit that Ceph will fail in unpredictable ways unless you give it crazy speeds for it’s storage and network. And yet, it has perpetually complained about too many placement groups.
1 pools have too many placement groups
Pool tank has 128 placement groups, should have 32
Aside from that and the occasional falling over of monitors it’s been relatively quiet? I’m tempted to use use the Synology for all the storage and let the 10GbE network be carved up into VM traffic instead. Right now I’m using bonded USB 1GbE copper and it’s kind of sketchy.
To be fair - both synologies are running big spinny NAS drives - I could reduce my capacity and my power usage by going with SSDs, but shockingly, I can’t seem to figure out what to cull in the 35TB combined storage.
I am debating moving my Vault cluster from a Clusterhat to pods on my fresh kubes deployment - and if I virtualize Pihole, that would also reduce some power consumption. Admittedly, I’m going overboard on my “homelab” - it’s more of a full blown SMB at this point with Palo firewall and brocade 48p switch. I do infosec for a living though, and there’s reason to most of my madness.
Unfortunately, no - not specifically. I want to get a kilawatt monitor at one point. The best I can do is share my UPS’s reported power output - currently at around 202-216W, but that includes both my DS1618 and the DS415+ along with my Ubiquiti NVR and two of my Lenovo M920Qs.
I should probably look at what adding the 5 bay external expansion would take power wise and maybe decommission the very aged 415
Edit: this is also my annual reminder to finally hook up the USB port on my UPSs to… something. I really wanted to get some smart - “Oh shit there’s a power outage and we’re running low on reserves, intelligently and gracefully shut things off in this order”, but I never got around to it.
This is basically my homelab. Synology 1618 + 3x Lenovo M920Q systems with 1TB names. I upgraded to a 10gb fibre switch so they run Proxmox + Ceph, with the Synology offering additional fibre storage with the add on 10gb fibre card.
That’s probably a few steps up from what the OP is asking for.
Splitting out storage and computer is definitely good first step to increase optimization and increase failure resiliency.
For the nginx reverse proxy - that’s how I ran things prior to moving to microk8s. If you want I can dig out some config examples. The trick for me was to set up host based stanzas, then update my internal DNS to have A records for each docker service pointing to the same docker host.
With Kubes + external-dns + nginx ingress, I can just do a deployment/service/ingress and things automatically work now.