2018-07-31 15:18:33 +00:00
|
|
|
|
|
|
|
|
=============================
|
|
|
|
|
Rook orchestrator integration
|
|
|
|
|
=============================
|
|
|
|
|
|
|
|
|
|
Rook (https://rook.io/) is an orchestration tool that can run Ceph inside
|
|
|
|
|
a Kubernetes cluster.
|
|
|
|
|
|
|
|
|
|
The ``rook`` module provides integration between Ceph's orchestrator framework
|
|
|
|
|
(used by modules such as ``dashboard`` to control cluster services) and
|
|
|
|
|
Rook.
|
|
|
|
|
|
|
|
|
|
Orchestrator modules only provide services to other modules, which in turn
|
|
|
|
|
provide user interfaces. To try out the rook module, you might like
|
|
|
|
|
to use the :ref:`Orchestrator CLI <orchestrator-cli-module>` module.
|
|
|
|
|
|
|
|
|
|
Requirements
|
|
|
|
|
------------
|
|
|
|
|
|
|
|
|
|
- Running ceph-mon and ceph-mgr services that were set up with Rook in
|
|
|
|
|
Kubernetes.
|
2019-01-29 14:51:16 +00:00
|
|
|
- Rook 0.9 or newer.
|
2018-07-31 15:18:33 +00:00
|
|
|
|
|
|
|
|
Configuration
|
|
|
|
|
-------------
|
|
|
|
|
|
|
|
|
|
Because a Rook cluster's ceph-mgr daemon is running as a Kubernetes pod,
|
|
|
|
|
the ``rook`` module can connect to the Kubernetes API without any explicit
|
|
|
|
|
configuration.
|
|
|
|
|
|
2019-01-29 14:51:16 +00:00
|
|
|
Development
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
If you are a developer, please see :ref:`kubernetes-dev` for instructions
|
|
|
|
|
on setting up a development environment to work with this.
|
2018-07-31 15:18:33 +00:00
|
|
|
|
|
|
|
|
|
