Re: Is Ceph with rook ready for production?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Szabo, Istvan (Agoda)" <Istvan.Szabo@xxxxxxxxx> writes:

> How about the design? Everything is the same but the services are
> containerized and you have an orchestration service on the top?

Not really. Yes, everything is in containers, but you don't have a
"cephadm" alike tool, because that's not how k8s is designed. Instead
you manage rook via idempotent configurations. You declare a cluster or
a pool, rook takes care of it.

For run time tunings/settings, you have a ceph-toolbox, which
essentially is a container providing access to the ceph cli + correct
configuration.

In a nutshell:

- k8s -> takes care of the deployment, restarting, etc.
- rook -> takes care of proper upgrades and deployments in regards to
  ceph; i.e. in which order to upgrade mons/mgrs/osds and co.
- ceph-toolbox -> gives you the usual ceph cli, inside a container

HTH,

Nico

--
Sustainable and modern Infrastructures by ungleich.ch
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux