]>
Commit | Line | Data |
---|---|---|
1911f103 TL |
1 | ======================= |
2 | Basic Ceph Client Setup | |
3 | ======================= | |
4 | Client machines need some basic configuration in order to interact with | |
5 | a cluster. This document describes how to configure a client machine | |
6 | for cluster interaction. | |
7 | ||
8 | .. note:: Most client machines only need the `ceph-common` package and | |
9 | its dependencies installed. That will supply the basic `ceph` | |
10 | and `rados` commands, as well as other commands like | |
11 | `mount.ceph` and `rbd`. | |
12 | ||
13 | Config File Setup | |
14 | ================= | |
15 | Client machines can generally get away with a smaller config file than | |
16 | a full-fledged cluster member. To generate a minimal config file, log | |
17 | into a host that is already configured as a client or running a cluster | |
f91f0fd5 TL |
18 | daemon, and then run |
19 | ||
20 | .. code-block:: bash | |
1911f103 TL |
21 | |
22 | ceph config generate-minimal-conf | |
23 | ||
24 | This will generate a minimal config file that will tell the client how to | |
25 | reach the Ceph Monitors. The contents of this file should typically be | |
26 | installed in `/etc/ceph/ceph.conf`. | |
27 | ||
28 | Keyring Setup | |
29 | ============= | |
30 | Most Ceph clusters are run with authentication enabled, and the client will | |
31 | need keys in order to communicate with cluster machines. To generate a | |
32 | keyring file with credentials for `client.fs`, log into an extant cluster | |
f91f0fd5 TL |
33 | member and run |
34 | ||
35 | .. code-block:: bash | |
1911f103 TL |
36 | |
37 | ceph auth get-or-create client.fs | |
38 | ||
39 | The resulting output should be put into a keyring file, typically | |
40 | `/etc/ceph/ceph.keyring`. |