2 ================================
3 DeepSea orchestrator integration
4 ================================
6 DeepSea (https://github.com/SUSE/DeepSea) is a collection of `Salt
7 <https://github.com/saltstack/salt>`_ state files, runners and modules for
8 deploying and managing Ceph.
10 The ``deepsea`` module provides integration between Ceph's orchestrator
11 framework (used by modules such as ``dashboard`` to control cluster services)
14 Orchestrator modules only provide services to other modules, which in turn
15 provide user interfaces. To try out the deepsea module, you might like
16 to use the :ref:`Orchestrator CLI <orchestrator-cli-module>` module.
21 - A salt-master node with DeepSea 0.9.9 or later installed, and the salt-api
23 - Ideally, several salt-minion nodes against which at least DeepSea's stages 0
24 through 2 have been run (this is the minimum required for the orchestrator's
25 inventory and status functions to return interesting information).
30 Four configuration keys must be set in order for the module to talk to
36 - salt_api_eauth (default is "sharedsecret")
38 These all need to match the salt-api configuration on the salt master (see
39 eauth.conf, salt-api.conf and sharedsecret.conf in /etc/salt/master.d/ on the
45 Configuration keys can be set on any machine with the proper cephx credentials,
46 these are usually Monitors where the *client.admin* key is present.
50 ceph deepsea config-set <key> <value>
56 ceph deepsea config-set salt_api_url http://admin.example.com:8000/
57 ceph deepsea config-set salt_api_username admin
58 ceph deepsea config-set salt_api_password 12345
60 The current configuration of the module can also be shown:
64 ceph deepsea config-show
69 Should you want to debug the deepsea module, increase the logging level for
70 ceph-mgr and check the logs.
77 With the log level set to 20, the module will print out all the data received
78 from the salt event bus. All log messages will be prefixed with *mgr[deepsea]*