3 ms·

> We are attempting to build a fault-tolerant and performant CephFS cluster Ohhh boy. I hope this works, and look forward to hearing updates.

by dimino 10y ago

mritun 10y ago
from CephFS website: "Important: CephFS currently lacks a robust ‘fsck’ check and repair function. Please use caution when storing important data as the disaster recovery tools are still under development. For more information about using CephFS today, see CephFS for early adopters." I'm getting the same feeling I get when I'm watching those "Hold my beer and watch this..." videos. From my vantage point they look to have 0 experience in building and running infrastructure... and asking advice on HN. They might ask well post a Ask Slashdot thread if they want armchair advice. Genuinely, I think they've crunched some numbers and think they can run their stuff cheaper and faster in-house... but probably underestimated the human-experience angle. For just 10-20 physical servers, this is going to be either extremely expensive (if they hire right) or extremely painful (if they don't).
- lykron 10y ago
  It seems they have Ceph experience, considering they've made work on AWS.
- sytse 10y ago
  We certainly don't have any experience hosting our own hardware. We're not doing this to save money, we're doing it to increase performance https://about.gitlab.com/2016/11/10/why-choose-bare-metal/ https://about.gitlab.com/2016/11/10/why-choose-bare-metal/
  - mritun 10y ago
    Then prototype first. Rent a server or two somewhere for 3-6 months and run a shadow first. Once you're confident that you understand all the "other 80%" stuff that is involved running your own infrastructure and don't lose data, then think about doing it yourself. A service providers' biggest responsibilities to its customers are security, durability, availability and performance -- in that order. You guys are vastly underestimating the complexity involved in getting first 3 right.

> We are attempting to build a fault-tolerant and performant CephFS cluster Ohhh boy. I hope this works, and look forward to hearing updates.

by dimino 10y ago

> We are attempting to build a fault-tolerant and performant CephFS cluster Ohhh boy. I hope this works, and look forward to hearing updates.

mritun 10y ago

from CephFS website: "Important: CephFS currently lacks a robust ‘fsck’ check and repair function. Please use caution when storing important data as the disaster recovery tools are still under development. For more information about using CephFS today, see CephFS for early adopters." I'm getting the same feeling I get when I'm watching those "Hold my beer and watch this..." videos. From my vantage point they look to have 0 experience in building and running infrastructure... and asking advice on HN. They might ask well post a Ask Slashdot thread if they want armchair advice. Genuinely, I think they've crunched some numbers and think they can run their stuff cheaper and faster in-house... but probably underestimated the human-experience angle. For just 10-20 physical servers, this is going to be either extremely expensive (if they hire right) or extremely painful (if they don't).

lykron 10y ago
It seems they have Ceph experience, considering they've made work on AWS.
sytse 10y ago
We certainly don't have any experience hosting our own hardware. We're not doing this to save money, we're doing it to increase performance https://about.gitlab.com/2016/11/10/why-choose-bare-metal/ https://about.gitlab.com/2016/11/10/why-choose-bare-metal/
- mritun 10y ago
  Then prototype first. Rent a server or two somewhere for 3-6 months and run a shadow first. Once you're confident that you understand all the "other 80%" stuff that is involved running your own infrastructure and don't lose data, then think about doing it yourself. A service providers' biggest responsibilities to its customers are security, durability, availability and performance -- in that order. You guys are vastly underestimating the complexity involved in getting first 3 right.