Chapter 10. Make your Calamari Admin Node a Ceph Admin Node
After you create your initial monitors, you can use the Ceph CLI to check on your cluster. However, you have to specify the monitor and admin keyring each time with the path to the directory holding your configuration, but you can simplify your CLI usage by making the admin node a Ceph admin client.
You will also need to install
ceph-common on the Calamari node.
ceph-deploy admin <node-name>
ceph-deploy admin admin-node
ceph-deploy utility will copy the
ceph.client.admin.keyring files to the
etc/ceph directory. When
ceph-deploy is talking to the local admin host (
admin-node), it must be reachable by its hostname (e.g.,
hostname -s). If necessary, modify
/etc/hosts to add the name of the admin host. If you do not have an
/etc/ceph directory, you should install
You may then use the Ceph CLI.
Once you have added your new Ceph monitors, Ceph will begin synchronizing the monitors and form a quorum. You can check the quorum status by executing the following:
sudo ceph quorum_status --format json-pretty
Ensure that you have acceptable permissions for the
/etc/ceph/ceph.client.admin.keyring. You can use
sudo when executing the
ceph command, or your can change the keyring permissions to enable a specific user or group. Keyring permissions provide administrative capability to the Red Hat Ceph Storage cluster. So exercise caution if many users have access to the Ceph nodes and admin node.
sudo chmod +r /etc/ceph/ceph.client.admin.keyring
Your cluster will not achieve an
active + clean state until you add enough OSDs to facilitate object replicas. This is inclusive of CRUSH failure domains.