Does anyone have experience running ceph in a home lab? Last time I looked into it, there were quite significant hardware requirements.
Yes. I first tried it with Rook, and that was a disaster, so I shifted to Longhorn. That has had its own share of problems, and is quite slow. Finally, I let Proxmox manage Ceph for me, and it’s been a dream. So far I haven’t migrated my K8s workloads to it, but I’ve used it for RDBMS storage (DBs in VMs), and it works flawlessly. I don’t have an incredibly great setup, either: 3x Dell R620s (Ivy Bridge-era Xeons), a…
Ceph: A Journey to 1 TiB/s
111–120 of 216 posts
Re: Ceph: A Journey to 1 TiB/s
#112Our EOS clusters have a lot more nodes, however, and use mostly HDDs. CERN also uses ceph extensively.
Re: Ceph: A Journey to 1 TiB/s
#113Does anyone have experience running ceph in a home lab? Last time I looked into it, there were quite significant hardware requirements.
My household is already 100% on Linux, so having a native network filesystem that I can just mount from any laptop is very handy.
Works great over Tailscale too, so I don't even have to be at home.
[1] I run a large install of Ceph at work, so "easy" might be a bit relative.
Re: Ceph: A Journey to 1 TiB/s
#114Re: Ceph: A Journey to 1 TiB/s
#115Earlier quoted context omitted.
I had to run a bunch of benchmarks to compare speeds of not just AWS instance types, but actual individual instances in each type, as some NVME SSDs have been more used than others in order to lube up some Aerospike response times. Crazy.
Ad-tech, or?
Re: Ceph: A Journey to 1 TiB/s
#116Earlier quoted context omitted.
There still are. As someone who has done both production and homelab deployments: unless you are specifically just looking for experience with it and just setting up a demo - don't bother. When it works, it works great - when it goes wrong it's a huge headache. Edit: As just an edit, if distributed storage is just something you are interested in there are much better options for a homelab setup: - seaweedfs has been…
I just want to hoard data. I hate having to delete stuff to make space. Things disappear from the web every day. I should hold onto them. My requirements for a storage solution are: > Single root file system > Storage device failure tolerance > Gradual expansion capability The problem with every storage solution I've ever seen is the lack of gradual expandability. I'm not a corporation, I'm just a guy. I don't have t…
Re: Ceph: A Journey to 1 TiB/s
#117Does anyone have experience running ceph in a home lab? Last time I looked into it, there were quite significant hardware requirements.
I run Ceph on some Raspberry Pi 4s. It's super reliable, and with cephadm it's very easy[1] to install and maintain. My household is already 100% on Linux, so having a native network filesystem that I can just mount from any laptop is very handy. Works great over Tailscale too, so I don't even have to be at home. [1] I run a large install of Ceph at work, so "easy" might be a bit relative.
I'm trying to do similar.
Re: Ceph: A Journey to 1 TiB/s
#118Earlier quoted context omitted.
Those numbers seem reasonable in that context. I first started using BitTorrent around that time as well, and it wasn't uncommon to see many users long-term seeding multiple hundreds of gigabytes of Linux ISOs alone. Here’s another usage scenario with data usage numbers I found a while back. > A 2004 paper published in ACM Transactions on Programming Languages and Systems shows how Hancock code can sift calling card…
I archived Hancock here over a decade ago, stumbled upon it via HN at the time if I’m not mistaken: https://github.com/mqudsi/hancock
Corinna Cortes et al wrote the paper(s) on Hancock and also the Communities of Interest paper referenced in the Wired article I linked to. She’s apparently a pretty big deal and went on to work at Google after her prestigious work at AT&T.
Hancock: A Language for Extracting Signatures from Data
https://scholar.google.com/citations?view_op=view_citation&h...
Hancock: A Language for Analyzing Transactional Data Streams
https://scholar.google.com/citations?view_op=view_citation&h...
Communities of Interest
https://scholar.google.com/citations?view_op=view_citation&h...
Re: Ceph: A Journey to 1 TiB/s
#119Earlier quoted context omitted.
I run Ceph on some Raspberry Pi 4s. It's super reliable, and with cephadm it's very easy[1] to install and maintain. My household is already 100% on Linux, so having a native network filesystem that I can just mount from any laptop is very handy. Works great over Tailscale too, so I don't even have to be at home. [1] I run a large install of Ceph at work, so "easy" might be a bit relative.
What are your speeds? Do you rub ceph FS too? I'm trying to do similar.
Latency is hilariously terrible though. It's funny to open a text file over the network in vi, paste a long blob of text and watch it sync that line by line over the network.
If by "rub" you mean scrub, then yes, although I increased the scrub intervals. There's no need to scrub everything every week.
Re: Ceph: A Journey to 1 TiB/s
#120Earlier quoted context omitted.
It’s at least 20ish years ago: I remember an old sysadmin talking about managing petabytes before 2003
Those numbers seem reasonable in that context. I first started using BitTorrent around that time as well, and it wasn't uncommon to see many users long-term seeding multiple hundreds of gigabytes of Linux ISOs alone. Here’s another usage scenario with data usage numbers I found a while back. > A 2004 paper published in ACM Transactions on Programming Languages and Systems shows how Hancock code can sift calling card…
This is pretty mind-boggling to me.