Chapter 2. Understanding process management for Ceph

2.1. Prerequisites
Copiar o link

Installation of the Red Hat Ceph Storage software.

2.2. Ceph process management
Copiar o link

In Red Hat Ceph Storage, all process management is done through the Systemd service. Each time you want to start, restart, and stop the Ceph daemons, you must specify the daemon type or the daemon instance.

Additional Resources

For more information about using Systemd, see the chapter Managing services with systemd in the Red Hat Enterprise Linux System Administrator’s Guide.

2.3. Starting, stopping, and restarting all Ceph daemons
Copiar o link

Start, stop, and restart all Ceph daemons as an admin from the node.

Prerequisites

A running Red Hat Ceph Storage cluster.
Having root access to the node.

Procedure

Starting all Ceph daemons:
```
systemctl start ceph.target
```
```
[root@admin ~]# systemctl start ceph.target
```
Copy to Clipboard Toggle word wrap
Stopping all Ceph daemons:
```
systemctl stop ceph.target
```
```
[root@admin ~]# systemctl stop ceph.target
```
Copy to Clipboard Toggle word wrap
Restarting all Ceph daemons:
```
systemctl restart ceph.target
```
```
[root@admin ~]# systemctl restart ceph.target
```
Copy to Clipboard Toggle word wrap

2.4. Starting, stopping, and restarting the Ceph daemons by type
Copiar o link

To start, stop, or restart all Ceph daemons of a particular type, follow these procedures on the node running the Ceph daemons.

Prerequisites

A running Red Hat Ceph Storage cluster.
Having root access to the node.

Procedure

On Ceph Monitor nodes:

Starting:

systemctl start ceph-mon.target

[root@mon ~]# systemctl start ceph-mon.target

Copy to Clipboard

Toggle word wrap

Stopping:

systemctl stop ceph-mon.target

[root@mon ~]# systemctl stop ceph-mon.target

Copy to Clipboard

Toggle word wrap

Restarting:

systemctl restart ceph-mon.target

[root@mon ~]# systemctl restart ceph-mon.target

Copy to Clipboard

Toggle word wrap

On Ceph Manager nodes:

Starting:

systemctl start ceph-mgr.target

[root@mgr ~]# systemctl start ceph-mgr.target

Copy to Clipboard

Toggle word wrap

Stopping:

systemctl stop ceph-mgr.target

[root@mgr ~]# systemctl stop ceph-mgr.target

Copy to Clipboard

Toggle word wrap

Restarting:

systemctl restart ceph-mgr.target

[root@mgr ~]# systemctl restart ceph-mgr.target

Copy to Clipboard

Toggle word wrap

On Ceph OSD nodes:

Starting:

systemctl start ceph-osd.target

[root@osd ~]# systemctl start ceph-osd.target

Copy to Clipboard

Toggle word wrap

Stopping:

systemctl stop ceph-osd.target

[root@osd ~]# systemctl stop ceph-osd.target

Copy to Clipboard

Toggle word wrap

Restarting:

systemctl restart ceph-osd.target

[root@osd ~]# systemctl restart ceph-osd.target

Copy to Clipboard

Toggle word wrap

On Ceph Object Gateway nodes:

Starting:

systemctl start ceph-radosgw.target

[root@rgw ~]# systemctl start ceph-radosgw.target

Copy to Clipboard

Toggle word wrap

Stopping:

systemctl stop ceph-radosgw.target

[root@rgw ~]# systemctl stop ceph-radosgw.target

Copy to Clipboard

Toggle word wrap

Restarting:

systemctl restart ceph-radosgw.target

[root@rgw ~]# systemctl restart ceph-radosgw.target

Copy to Clipboard

Toggle word wrap

2.5. Starting, stopping, and restarting the Ceph daemons by instance
Copiar o link

To start, stop, or restart a Ceph daemon by instance, follow these procedures on the node running the Ceph daemons.

Prerequisites

A running Red Hat Ceph Storage cluster.
Having root access to the node.

Procedure

On a Ceph Monitor node:

Starting:

systemctl start ceph-mon@MONITOR_HOST_NAME

[root@mon ~]# systemctl start ceph-mon@MONITOR_HOST_NAME

Copy to Clipboard

Toggle word wrap

Stopping:

systemctl stop ceph-mon@MONITOR_HOST_NAME

[root@mon ~]# systemctl stop ceph-mon@MONITOR_HOST_NAME

Copy to Clipboard

Toggle word wrap

Restarting:

systemctl restart ceph-mon@MONITOR_HOST_NAME

[root@mon ~]# systemctl restart ceph-mon@MONITOR_HOST_NAME

Copy to Clipboard

Toggle word wrap

Replace

MONITOR_HOST_NAME with the name of the Ceph Monitor node.

On a Ceph Manager node:

Starting:

systemctl start ceph-mgr@MANAGER_HOST_NAME

[root@mgr ~]# systemctl start ceph-mgr@MANAGER_HOST_NAME

Copy to Clipboard

Toggle word wrap

Stopping:

systemctl stop ceph-mgr@MANAGER_HOST_NAME

[root@mgr ~]# systemctl stop ceph-mgr@MANAGER_HOST_NAME

Copy to Clipboard

Toggle word wrap

Restarting:

systemctl restart ceph-mgr@MANAGER_HOST_NAME

[root@mgr ~]# systemctl restart ceph-mgr@MANAGER_HOST_NAME

Copy to Clipboard

Toggle word wrap

Replace

MANAGER_HOST_NAME with the name of the Ceph Manager node.

On a Ceph OSD node:
Starting:
```
systemctl start ceph-osd@OSD_NUMBER
```
```
[root@osd ~]# systemctl start ceph-osd@OSD_NUMBER
```
Copy to Clipboard Toggle word wrap
Stopping:
```
systemctl stop ceph-osd@OSD_NUMBER
```
```
[root@osd ~]# systemctl stop ceph-osd@OSD_NUMBER
```
Copy to Clipboard Toggle word wrap
Restarting:
```
systemctl restart ceph-osd@OSD_NUMBER
```
```
[root@osd ~]# systemctl restart ceph-osd@OSD_NUMBER
```
Copy to Clipboard Toggle word wrap
Replace
- OSD_NUMBER with the ID number of the Ceph OSD.
  For example, when looking at the ceph osd tree command output, osd.0 has an ID of 0.

On a Ceph Object Gateway node:

Starting:

systemctl start ceph-radosgw@rgw.OBJ_GATEWAY_HOST_NAME

[root@rgw ~]# systemctl start ceph-radosgw@rgw.OBJ_GATEWAY_HOST_NAME

Copy to Clipboard

Toggle word wrap

Stopping:

systemctl stop ceph-radosgw@rgw.OBJ_GATEWAY_HOST_NAME

[root@rgw ~]# systemctl stop ceph-radosgw@rgw.OBJ_GATEWAY_HOST_NAME

Copy to Clipboard

Toggle word wrap

Restarting:

systemctl restart ceph-radosgw@rgw.OBJ_GATEWAY_HOST_NAME

[root@rgw ~]# systemctl restart ceph-radosgw@rgw.OBJ_GATEWAY_HOST_NAME

Copy to Clipboard

Toggle word wrap

Replace

OBJ_GATEWAY_HOST_NAME with the name of the Ceph Object Gateway node.

2.6. Starting, stopping, and restarting Ceph daemons that run in containers
Copiar o link

Use the systemctl command start, stop, or restart Ceph daemons that run in containers.

Prerequisites

Installation of the Red Hat Ceph Storage software.
Root-level access to the node.

Procedure

To start, stop, or restart a Ceph daemon running in a container, run a systemctl command as root composed in the following format:
```
systemctl ACTION ceph-DAEMON@ID
```
```
systemctl ACTION ceph-DAEMON@ID
```
Copy to Clipboard Toggle word wrap
Replace
ACTION is the action to perform; start, stop, or restart.
DAEMON is the daemon; osd, mon, mds, or rgw.
ID is either:
The short host name where the ceph-mon, ceph-mds, or ceph-rgw daemons are running.
The ID of the ceph-osd daemon if it was deployed.
For example, to restart a ceph-osd daemon with the ID osd01:
[root@osd ~]# systemctl restart ceph-osd@osd01

Copy to Clipboard Toggle word wrap
To start a ceph-mon demon that runs on the ceph-monitor01 host:
[root@mon ~]# systemctl start ceph-mon@ceph-monitor01

Copy to Clipboard Toggle word wrap
To stop a ceph-rgw daemon that runs on the ceph-rgw01 host:
[root@rgw ~]# systemctl stop ceph-radosgw@ceph-rgw01

Copy to Clipboard Toggle word wrap
Verify that the action was completed successfully.
```
systemctl status ceph-DAEMON@ID
```
```
systemctl status ceph-DAEMON@ID
```
Copy to Clipboard Toggle word wrap
For example:
```
systemctl status ceph-mon@ceph-monitor01
```
```
[root@mon ~]# systemctl status ceph-mon@ceph-monitor01
```
Copy to Clipboard Toggle word wrap

Additional Resources

See the Understanding process management for Ceph chapter in the Red Hat Ceph Storage Administration Guide for more information.

2.7. Viewing the logs of Ceph daemons that run in containers
Copiar o link

Use the journald daemon from the container host to view the logs of a Ceph daemon from a container.

Prerequisites

Installation of the Red Hat Ceph Storage software.
Root-level access to the node.

Procedure

To view the entire Ceph log, run a journalctl command as root composed in the following format:
```
journalctl -u ceph-DAEMON@ID
```
```
journalctl -u ceph-DAEMON@ID
```
Copy to Clipboard Toggle word wrap
Replace
DAEMON is the Ceph daemon; osd, mon, or rgw.
ID is either:
The short host name where the ceph-mon, ceph-mds, or ceph-rgw daemons are running.
The ID of the ceph-osd daemon if it was deployed.
For example, to view the entire log for the ceph-osd daemon with the ID osd01:
[root@osd ~]# journalctl -u ceph-osd@osd01

Copy to Clipboard Toggle word wrap
To show only the recent journal entries, use the -f option.
```
journalctl -fu ceph-DAEMON@ID
```
```
journalctl -fu ceph-DAEMON@ID
```
Copy to Clipboard Toggle word wrap
For example, to view only recent journal entries for the ceph-mon daemon that runs on the ceph-monitor01 host:
```
journalctl -fu ceph-mon@ceph-monitor01
```
```
[root@mon ~]# journalctl -fu ceph-mon@ceph-monitor01
```
Copy to Clipboard Toggle word wrap

Note

You can also use the sosreport utility to view the journald logs. For more details about SOS reports, see the What is an sosreport and how to create one in Red Hat Enterprise Linux? solution on the Red Hat Customer Portal.

Additional Resources

The journalctl(1) manual page.

2.8. Enabling logging to a file for containerized Ceph daemons
Copiar o link

By default, containerized Ceph daemons do not log to files. You can use centralized configuration management to enable containerized Ceph daemons to log to files.

Prerequisites

Installation of the Red Hat Ceph Storage software.
Root-level access to the node where the containerized daemon runs.

Procedure

Navigate to the var/log/ceph directory:
Example
```
cd /var/log/ceph
```
```
[root@host01 ~]# cd /var/log/ceph
```
Copy to Clipboard Toggle word wrap

Note any existing log files.

Syntax

ls -l /var/log/ceph/

ls -l /var/log/ceph/

Copy to Clipboard

Toggle word wrap

Example

ls -l /var/log/ceph/

[root@host01 ceph]# ls -l /var/log/ceph/
total 396
-rw-r--r--. 1 ceph ceph 107230 Feb  5 14:42 ceph-osd.0.log
-rw-r--r--. 1 ceph ceph 107230 Feb  5 14:42 ceph-osd.3.log
-rw-r--r--. 1 root root 181641 Feb  5 14:42 ceph-volume.log

Copy to Clipboard

Toggle word wrap

In the example, logging to files for OSD.0 and OSD.3 are already enabled.

Fetch the container name of the daemon for which you want to enable logging:
Red Hat Enterprise Linux 7
```
docker ps -a
```
```
[root@host01 ceph]# docker ps -a
```
Copy to Clipboard Toggle word wrap
Red Hat Enterprise Linux 8
```
podman ps -a
```
```
[root@host01 ceph]# podman ps -a
```
Copy to Clipboard Toggle word wrap

Use centralized configuration management to enable logging to a file for a Ceph daemon.

Red Hat Enterprise Linux 7

docker exec CONTAINER_NAME ceph config set DAEMON_NAME log_to_file true

docker exec CONTAINER_NAME ceph config set DAEMON_NAME log_to_file true

Copy to Clipboard

Toggle word wrap

Red Hat Enterprise Linux 8

podman exec CONTAINER_NAME ceph config set DAEMON_NAME log_to_file true

podman exec CONTAINER_NAME ceph config set DAEMON_NAME log_to_file true

Copy to Clipboard

Toggle word wrap

The DAEMON_NAME is derived from the CONTAINER_NAME. Remove ceph- and replace the hyphen between the daemon and daemon ID with a period.

Red Hat Enterprise Linux 7

docker exec ceph-mon-host01 ceph config set mon.host01 log_to_file true

[root@host01 ceph]# docker exec ceph-mon-host01 ceph config set mon.host01 log_to_file true

Copy to Clipboard

Toggle word wrap

Red Hat Enterprise Linux 8

podman exec ceph-mon-host01 ceph config set mon.host01 log_to_file true

[root@host01 ceph]# podman exec ceph-mon-host01 ceph config set mon.host01 log_to_file true

Copy to Clipboard

Toggle word wrap

Optional: To enable logging to a file for the cluster log, use the mon_cluster_log_to_file option:

Red Hat Enterprise Linux 7

docker exec CONTAINER_NAME ceph config set DAEMON_NAME mon_cluster_log_to_file true

docker exec CONTAINER_NAME ceph config set DAEMON_NAME mon_cluster_log_to_file true

Copy to Clipboard

Toggle word wrap

Red Hat Enterprise Linux 8

podman exec CONTAINER_NAME ceph config set DAEMON_NAME mon_cluster_log_to_file true

podman exec CONTAINER_NAME ceph config set DAEMON_NAME mon_cluster_log_to_file true

Copy to Clipboard

Toggle word wrap

Red Hat Enterprise Linux 7

docker exec ceph-mon-host01 ceph config set mon.host01 mon_cluster_log_to_file true

[root@host01 ceph]# docker exec ceph-mon-host01 ceph config set mon.host01 mon_cluster_log_to_file true

Copy to Clipboard

Toggle word wrap

Red Hat Enterprise Linux 8

podman exec ceph-mon-host01 ceph config set mon.host01 mon_cluster_log_to_file true

[root@host01 ceph]# podman exec ceph-mon-host01 ceph config set mon.host01 mon_cluster_log_to_file true

Copy to Clipboard

Toggle word wrap

Validate the updated configuration:

Red Hat Enterprise Linux 7

docker exec CONTAINER_NAME ceph config show-with-defaults DAEMON_NAME | grep log_to_file

docker exec CONTAINER_NAME ceph config show-with-defaults DAEMON_NAME | grep log_to_file

Copy to Clipboard

Toggle word wrap

Red Hat Enterprise Linux 8

podman exec CONTAINER_NAME ceph config show-with-defaults DAEMON_NAME | grep log_to_file

podman exec CONTAINER_NAME ceph config show-with-defaults DAEMON_NAME | grep log_to_file

Copy to Clipboard

Toggle word wrap

Example

podman exec ceph-mon-host01 ceph config show-with-defaults mon.host01 | grep log_to_file

[root@host01 ceph]# podman exec ceph-mon-host01 ceph config show-with-defaults mon.host01 | grep log_to_file
log_to_file                                                true                                                                                                                                                                                                                                      mon      default[false]
mon_cluster_log_to_file                                    true                                                                                                                                                                                                                                      mon      default[false]

Copy to Clipboard

Toggle word wrap

Optional: Restart the Ceph daemon:

Syntax

systemctl restart ceph-DAEMON@DAEMON_ID

systemctl restart ceph-DAEMON@DAEMON_ID

Copy to Clipboard

Toggle word wrap

Example

systemctl restart ceph-mon@host01

[root@host01 ceph]# systemctl restart ceph-mon@host01

Copy to Clipboard

Toggle word wrap

Validate that the new log files exist:

Syntax

ls -l /var/log/ceph/

ls -l /var/log/ceph/

Copy to Clipboard

Toggle word wrap

Example

ls -l /var/log/ceph/

[root@host01 ceph]# ls -l /var/log/ceph/
total 408
-rw-------. 1 ceph ceph    202 Feb  5 16:06 ceph.audit.log
-rw-------. 1 ceph ceph   3182 Feb  5 16:06 ceph.log
-rw-r--r--. 1 ceph ceph   2049 Feb  5 16:06 ceph-mon.host01.log
-rw-r--r--. 1 ceph ceph 107230 Feb  5 14:42 ceph-osd.0.log
-rw-r--r--. 1 ceph ceph 107230 Feb  5 14:42 ceph-osd.3.log
-rw-r--r--. 1 root root 181641 Feb  5 14:42 ceph-volume.log

Copy to Clipboard

Toggle word wrap

Two new files were created, ceph-mon.host01.log for a Monitor daemon and ceph.log for the cluster log.

2.9. Gathering log files of Ceph daemons
Copiar o link

To gather log files of Ceph daemons, run the gather-ceph-logs.yml Ansible playbook. Currently, Red Hat Ceph Storage supports gathering logs for non-containerized deployments only.

Prerequisites

A running Red Hat Ceph Storage cluster deployed.
Admin-level access to the Ansible node.

Procedure

Navigate to the /usr/share/ceph-ansible directory:
```
cd /usr/share/ceph-ansible
```
```
[ansible@admin ~]# cd /usr/share/ceph-ansible
```
Copy to Clipboard Toggle word wrap

Run the playbook:

ansible-playbook infrastructure-playbooks/gather-ceph-logs.yml -i hosts

[ansible@admin ~]# ansible-playbook infrastructure-playbooks/gather-ceph-logs.yml -i hosts

Copy to Clipboard

Toggle word wrap

Wait for the logs to be collected on the Ansible administration node.

Additional Resources

See the Viewing log files of Ceph daemons that run in containers section in the Red Hat Ceph Storage Administration Guide for more details.

2.10. Powering down and rebooting Red Hat Ceph Storage cluster
Copiar o link

Follow the below procedure for powering down and rebooting the Ceph cluster.

Prerequisites

A running Red Hat Ceph Storage cluster.
Having root access.

Procedure

Powering down the Red Hat Ceph Storage cluster

Stop the clients from using the RBD images and RADOS Gateway on this cluster and any other clients.
The cluster must be in healthy state (Health_OK and all PGs active+clean) before proceeding. Run ceph status on a node with the client keyrings, for example, the Ceph Monitor or OpenStack controller nodes, to ensure the cluster is healthy.

If you use the Ceph File System (CephFS), the CephFS cluster must be brought down. Taking a CephFS cluster down is done by reducing the number of ranks to 1, setting the cluster_down flag, and then failing the last rank.

Example:

ceph fs set FS_NAME max_mds 1
ceph mds deactivate FS_NAME:1 # rank 2 of 2
ceph status # wait for rank 1 to finish stopping
ceph fs set FS_NAME cluster_down true
ceph mds fail FS_NAME:0

[root@osd ~]# ceph fs set FS_NAME max_mds 1
[root@osd ~]# ceph mds deactivate FS_NAME:1 # rank 2 of 2
[root@osd ~]# ceph status # wait for rank 1 to finish stopping
[root@osd ~]# ceph fs set FS_NAME cluster_down true
[root@osd ~]# ceph mds fail FS_NAME:0

Copy to Clipboard

Toggle word wrap

Setting the cluster_down flag prevents standbys from taking over the failed rank.

Set the noout, norecover, norebalance, nobackfill, nodown and pause flags. Run the following on a node with the client keyrings. For example, the Ceph Monitor or OpenStack controller node:

ceph osd set noout
ceph osd set norecover
ceph osd set norebalance
ceph osd set nobackfill
ceph osd set nodown
ceph osd set pause

[root@mon ~]# ceph osd set noout
[root@mon ~]# ceph osd set norecover
[root@mon ~]# ceph osd set norebalance
[root@mon ~]# ceph osd set nobackfill
[root@mon ~]# ceph osd set nodown
[root@mon ~]# ceph osd set pause

Copy to Clipboard

Toggle word wrap

Shut down the OSD nodes one by one:
```
systemctl stop ceph-osd.target
```
```
[root@osd ~]# systemctl stop ceph-osd.target
```
Copy to Clipboard Toggle word wrap
Shut down the monitor nodes one by one:
```
systemctl stop ceph-mon.target
```
```
[root@mon ~]# systemctl stop ceph-mon.target
```
Copy to Clipboard Toggle word wrap

Rebooting the Red Hat Ceph Storage cluster

Power on the administration node.
Power on the monitor nodes:
```
systemctl start ceph-mon.target
```
```
[root@mon ~]# systemctl start ceph-mon.target
```
Copy to Clipboard Toggle word wrap
Power on the OSD nodes:
```
systemctl start ceph-osd.target
```
```
[root@osd ~]# systemctl start ceph-osd.target
```
Copy to Clipboard Toggle word wrap
Wait for all the nodes to come up. Verify all the services are up and the connectivity is fine between the nodes.

Unset the noout, norecover, norebalance, nobackfill, nodown and pause flags. Run the following on a node with the client keyrings. For example, the Ceph Monitor or OpenStack controller node:

ceph osd unset noout
ceph osd unset norecover
ceph osd unset norebalance
ceph osd unset nobackfill
ceph osd unset nodown
ceph osd unset pause

[root@mon ~]# ceph osd unset noout
[root@mon ~]# ceph osd unset norecover
[root@mon ~]# ceph osd unset norebalance
[root@mon ~]# ceph osd unset nobackfill
[root@mon ~]# ceph osd unset nodown
[root@mon ~]# ceph osd unset pause

Copy to Clipboard

Toggle word wrap

If you use the Ceph File System (CephFS), the CephFS cluster must be brought back up by setting the cluster_down flag to false:
```
ceph fs set FS_NAME cluster_down false
```
```
[root@admin~]# ceph fs set FS_NAME cluster_down false
```
Copy to Clipboard Toggle word wrap
Verify the cluster is in healthy state (Health_OK and all PGs active+clean). Run ceph status on a node with the client keyrings. For example, the Ceph Monitor or OpenStack controller nodes, to ensure the cluster is healthy.

2.11. Additional Resources
Copiar o link

For more information on installing Ceph see the Red Hat Ceph Storage Installation Guide

Este conteúdo não está disponível no idioma selecionado.

2.1. Prerequisites
Copiar o link

2.2. Ceph process management
Copiar o link

2.3. Starting, stopping, and restarting all Ceph daemons
Copiar o link

2.4. Starting, stopping, and restarting the Ceph daemons by type
Copiar o link

2.5. Starting, stopping, and restarting the Ceph daemons by instance
Copiar o link

2.6. Starting, stopping, and restarting Ceph daemons that run in containers
Copiar o link

2.7. Viewing the logs of Ceph daemons that run in containers
Copiar o link

2.8. Enabling logging to a file for containerized Ceph daemons
Copiar o link

2.9. Gathering log files of Ceph daemons
Copiar o link

2.10. Powering down and rebooting Red Hat Ceph Storage cluster
Copiar o link

2.11. Additional Resources
Copiar o link

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Tornando o open source mais inclusivo

Sobre a Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

Este conteúdo não está disponível no idioma selecionado.

Chapter 2. Understanding process management for Ceph

2.1. PrerequisitesCopiar o linkLink copiado para a área de transferência!

2.2. Ceph process managementCopiar o linkLink copiado para a área de transferência!

2.3. Starting, stopping, and restarting all Ceph daemonsCopiar o linkLink copiado para a área de transferência!

2.4. Starting, stopping, and restarting the Ceph daemons by typeCopiar o linkLink copiado para a área de transferência!

2.5. Starting, stopping, and restarting the Ceph daemons by instanceCopiar o linkLink copiado para a área de transferência!

2.6. Starting, stopping, and restarting Ceph daemons that run in containersCopiar o linkLink copiado para a área de transferência!

2.7. Viewing the logs of Ceph daemons that run in containersCopiar o linkLink copiado para a área de transferência!

2.8. Enabling logging to a file for containerized Ceph daemonsCopiar o linkLink copiado para a área de transferência!

2.9. Gathering log files of Ceph daemonsCopiar o linkLink copiado para a área de transferência!

2.10. Powering down and rebooting Red Hat Ceph Storage clusterCopiar o linkLink copiado para a área de transferência!

2.11. Additional ResourcesCopiar o linkLink copiado para a área de transferência!

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Tornando o open source mais inclusivo

Sobre a Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

2.1. Prerequisites
Copiar o link

2.2. Ceph process management
Copiar o link

2.3. Starting, stopping, and restarting all Ceph daemons
Copiar o link

2.4. Starting, stopping, and restarting the Ceph daemons by type
Copiar o link

2.5. Starting, stopping, and restarting the Ceph daemons by instance
Copiar o link

2.6. Starting, stopping, and restarting Ceph daemons that run in containers
Copiar o link

2.7. Viewing the logs of Ceph daemons that run in containers
Copiar o link

2.8. Enabling logging to a file for containerized Ceph daemons
Copiar o link

2.9. Gathering log files of Ceph daemons
Copiar o link

2.10. Powering down and rebooting Red Hat Ceph Storage cluster
Copiar o link

2.11. Additional Resources
Copiar o link