Failing Better - When Not To Ceph and Lessons Learned - Lars Marowsky-Brée, SUSE

แชร์
ฝัง
  • เผยแพร่เมื่อ 16 ธ.ค. 2024

ความคิดเห็น • 6

  •  5 ปีที่แล้ว +20

    Sorry for the two typos! I cannot for the life of me explain the "plural apostrophe" on the title slide, and my colleague's name is properly spelled "João" instead. If you've got any feedback, please reach out to me by email so I can continue improving the talk!
    I'm also happy to answer any questions or follow-ups.

    • @kelownatechkid
      @kelownatechkid 4 ปีที่แล้ว +6

      Was a great presentation, much appreciated.

  • @ytdlgandalf
    @ytdlgandalf 4 ปีที่แล้ว +7

    The availability aspect of ceph is unbeatable. I'd hate to go back to drdb. That's why I run rook/ceph in my 4 node k8s cluster. The future is now

    • @Badgero12345
      @Badgero12345 3 ปีที่แล้ว +1

      TOTALLY agree! Nothing out there I have looked at is even close to as decent as CEPH. I have tried quite a few, the best part is rook-ceph works very well in the cloud on bare metal!

  • @yourjjrjjrjj
    @yourjjrjjrjj 6 หลายเดือนก่อน

    Is 3 node ceph cluster(with let's say 5 OSDs per node) ok for production? Or is it significantly better to have 5 nodes with 3 OSD per node? I only care about the performance.

    • @TheDarkWayne
      @TheDarkWayne 4 หลายเดือนก่อน

      It is better to go wide (more nodes less osds) deep (less nodes more osds) but it may not be worth it because of the overhead the additional nodes bring.