Procedure

1. Enter the following URL in a web browser:

   Syntax

   https://HOST_NAME:PORT

   Replace:

   • HOST_NAME with the fully qualified domain name (FQDN) of the active manager host.

   • PORT with port 8443

     Example

     https://host01:8443

     You can also get the URL of the dashboard by running the following command in the Cephadm shell:

     Example

     [ceph: root@host01 /]# ceph mgr services

     This command will show you all endpoints that are currently configured. Look for the dashboard key to obtain the URL for accessing the dashboard.

2. On the login page, enter the username admin and the default password provided during bootstrapping.
3. You have to change the password the first time you log in to the Red Hat Ceph Storage dashboard.

4. After logging in, the dashboard default landing page is displayed, which provides a high-level overview of status, performance, and capacity metrics of the Red Hat Ceph Storage cluster.

   Figure 2.1. Ceph dashboard landing page

   

5. Click the following icon on the dashboard landing page to collapse or display the options in the vertical menu:

   Figure 2.2. Vertical menu on the Ceph dashboard

   

Procedure

1. As a root user, create a login.txt file and provide the custom message for the users:

   Example

   ****CUSTOM LOGIN MESSAGE****

2. Mount the login.txt file under a directory in the container:

   Example

   [root@host01 ~]# cephadm shell --mount login.txt:/var/lib/ceph/login.txt

   Note

   Every time you exit the shell, you have to mount the file in the container before deploying the daemon.

3. Optional: Check if the dashboard Ceph Manager module is enabled:

   Example

   [ceph: root@host01 /]# ceph mgr module ls

4. Set the login banner text:

   Syntax

   ceph dashboard set-login-banner -i FILE_PATH

   Example

   [ceph: root@host01 /]# ceph dashboard set-login-banner -i /var/lib/ceph/login.txt
   
   login banner file added

5. Get the login banner text:

   Example

   [ceph: root@host01 /]# ceph dashboard get-login-banner
   
   ****CUSTOM LOGIN MESSAGE****

6. Optional: You can remove the login banner using the unset command:

   Example

   [ceph: root@host01 /]# ceph dashboard unset-login-banner
   
   Login banner removed

Procedure

1. Configure a MOTD for the dashboard:

   Syntax

   ceph dashboard motd set SEVERITY EXPIRES MESSAGE

   Example

   [ceph: root@host01 /]# ceph dashboard motd set danger 2d "Custom login message"
   
   Message of the day has been set.

   Replace

   • SEVERITY can be info, warning, or danger.
   • EXPIRES can be for seconds (s), minutes (m), hours (h), days (d), weeks (w), or never expires (0).
   • MESSAGE can be any custom message that users can view as soon as they log in to the dashboard.

2. Optional: Set the MOTD that does not expire:

   Example

   [ceph: root@host01 /]# ceph dashboard motd set danger 0 "Custom login message"
   
   Message of the day has been set.

3. Get the configured MOTD :

   Example

   [ceph: root@host01 /]# ceph dashboard motd get
   
   Message="Custom login message", severity="danger", expires="2022-09-08T07:38:52.963882Z"

4. Optional: Clear the configure MOTD using the clear command:

   Example

   [ceph: root@host01 /]# ceph dashboard motd clear
   
   Message of the day has been cleared.

Procedure

1. Copy the admin key from the bootstrapped host to other hosts:

   Syntax

   ssh-copy-id -f -i /etc/ceph/ceph.pub root@HOST_NAME

   Example

   [ceph: root@host01 /]# ssh-copy-id -f -i /etc/ceph/ceph.pub root@host02
   [ceph: root@host01 /]# ssh-copy-id -f -i /etc/ceph/ceph.pub root@host03

2. Log in to the dashboard with the default credentials provided during bootstrap.
3. Change the password and log in to the dashboard with the new password .

4. On the landing page, click Expand Cluster.

   Figure 2.3. Expand cluster

   

5. Add hosts:

   1. In the Add Hosts window, click +Add.

   2. Provide the hostname. This is same as the hostname that was provided while copying the key from the bootstrapped host.

      Note

      You can use the tool tip in the Add Hosts dialog box for more details.

   3. Optional: Provide the respective IP address of the host.
   4. Optional: Select the labels for the hosts on which the services are going to be created.
   5. Click Add Host.
   6. Follow the above steps for all the hosts in the storage cluster.
6. In the Add Hosts window, click Next.

7. Create OSDs:

   1. In the Create OSDs window, for Primary devices, Click +Add.
   2. In the Primary Devices window, filter for the device and select the device.
   3. Click Add.
   4. Optional: In the Create OSDs window, if you have any shared devices such as WAL or DB devices, then add the devices.
   5. Optional: Click on the check-box Encryption to encrypt the features.
   6. In the Create OSDs window, click Next.

8. Create services:

   1. In the Create Services window, click +Create.

   2. In the Create Service dialog box,

      1. Select the type of the service from the drop-down.
      2. Provide the service ID, a unique name of the service.
      3. Provide the placement by hosts or label.
      4. Select the hosts.
      5. Provide the number of daemons or services that need to be deployed.
   3. Click Create Service.
9. In the Create Service window, Click Next.

10. Review the Cluster Resources, Hosts by Services, Host Details. If you want to edit any parameter, click Back and follow the above steps.

    Figure 2.4. Review cluster

    
11. Click Expand Cluster.
12. You get a notification that the cluster expansion was successful.
13. The cluster health changes to HEALTH_OK status on the dashboard.

Verification

1. Log in to the cephadm shell:

   Example

   [root@host01 ~]# cephadm shell

2. Run the ceph -s command.

   Example

   [ceph: root@host01 /]# ceph -s

   The health of the cluster is HEALTH_OK.

1. Status
2. Capacity
3. Performance

Procedure

1. Log in to the dashboard:

   https://HOST_NAME:8443

2. Click the Dashboard Settings icon and then click User management.

   Figure 2.8. User management

   
3. To change the password of admin, click it’s row.
4. From the Edit drop-down menu, select Edit.

5. In the Edit User window, enter the new password, and change the other parameters, and then Click Edit User.

   Figure 2.9. Edit user management

   

   You will be logged out and redirected to the log-in screen. A notification appears confirming the password change.

Procedure

1. Log into the Cephadm shell:

   Example

   [root@host01 ~]# cephadm shell

2. Create the dashboard_password.yml file:

   Example

   [ceph: root@host01 /]# touch dashboard_password.yml

3. Edit the file and add the new dashboard password:

   Example

   [ceph: root@host01 /]# vi dashboard_password.yml

4. Reset the dashboard password:

   Syntax

   ceph dashboard ac-user-set-password DASHBOARD_USERNAME -i PASSWORD_FILE

   Example

   [ceph: root@host01 /]# ceph dashboard ac-user-set-password admin -i dashboard_password.yml
   {"username": "admin", "password": "$2b$12$i5RmvN1PolR61Fay0mPgt.GDpcga1QpYsaHUbJfoqaHd1rfFFx7XS", "roles": ["administrator"], "name": null, "email": null, "lastUpdate": , "enabled": true, "pwdExpirationDate": null, "pwdUpdateRequired": false}

Procedure

1. As a root user, create a grafana.yml file and provide the following details:

   Syntax

   service_type: grafana
   spec:
     initial_admin_password: PASSWORD

   Example

   service_type: grafana
   spec:
     initial_admin_password: mypassword

2. Mount the grafana.yml file under a directory in the container:

   Example

   [root@host01 ~]# cephadm shell --mount grafana.yml:/var/lib/ceph/grafana.yml

   Note

   Every time you exit the shell, you have to mount the file in the container before deploying the daemon.

3. Optional: Check if the dashboard Ceph Manager module is enabled:

   Example

   [ceph: root@host01 /]# ceph mgr module ls

4. Optional: Enable the dashboard Ceph Manager module:

   Example

   [ceph: root@host01 /]# ceph mgr module enable dashboard

5. Apply the specification using the orch command:

   Syntax

   ceph orch apply -i FILE_NAME.yml

   Example

   [ceph: root@host01 /]# ceph orch apply -i /var/lib/ceph/grafana.yml

6. Redeploy grafana service:

   Example

   [ceph: root@host01 /]# ceph orch redeploy grafana

   This creates an admin user called admin with the given password and the user can log in to the Grafana URL with these credentials.

Procedure

1. Log into the Cephadm shell:

   Example

   [root@host01 ~]# cephadm shell

2. Check the Ceph Manager services:

   Example

   [ceph: root@host01 /]# ceph mgr services
   
   {
       "prometheus": "http://10.8.0.101:9283/"
   }

   You can see that the Dashboard URL is not configured.

3. Enable the dashboard module:

   Example

   [ceph: root@host01 /]# ceph mgr module enable dashboard

4. Create the self-signed certificate for the dashboard access:

   Example

   [ceph: root@host01 /]# ceph dashboard create-self-signed-cert

   Note

   You can disable the certificate verification to avoid certification errors.

5. Check the Ceph Manager services:

   Example

   [ceph: root@host01 /]# ceph mgr services
   
   {
       "dashboard": "https://10.8.0.101:8443/",
       "prometheus": "http://10.8.0.101:9283/"
   }

6. Create the admin user and password to access the Red Hat Ceph Storage dashboard:

   Syntax

   echo -n "PASSWORD" > PASSWORD_FILE
   ceph dashboard ac-user-create admin -i PASSWORD_FILE administrator

   Example

   [ceph: root@host01 /]# echo -n "p@ssw0rd" > password.txt
   [ceph: root@host01 /]# ceph dashboard ac-user-create admin -i password.txt administrator

7. Enable the monitoring stack. See the Enabling monitoring stack section in the Red Hat Ceph Storage Dashboard Guide for details.

Procedure

1. Download the Red Hat Single Sign-On 7.4.0 Server on the system where Red Hat Ceph Storage is installed.

2. Unzip the folder:

   [root@host01 ~]# unzip rhsso-7.4.0.zip

3. Navigate to the standalone/configuration directory and open the standalone.xml for editing:

   [root@host01 ~]# cd standalone/configuration
   [root@host01 configuration]# vi standalone.xml

4. Replace all instances of localhost and two instances of 127.0.0.1 with the IP address of the machine where Red Hat SSO is installed.

5. Optional: For Red Hat Enterprise Linux 8, users might get Certificate Authority (CA) issues. Import the custom certificates from CA and move them into the keystore with the exact java version.

   Example

   [root@host01 ~]# keytool -import -noprompt -trustcacerts -alias ca -file ../ca.cer -keystore /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.272.b10-3.el8_3.x86_64/lib/security/cacert

6. To start the server from the bin directory of rh-sso-7.4 folder, run the standalone boot script:

   [root@host01 bin]# ./standalone.sh

7. Create the admin account in https: IP_ADDRESS :8080/auth with a username and password:

   Note

   You have to create an admin account only the first time that you log into the console

8. Log into the admin console with the credentials created.

Procedure

1. To create a realm, click the Master drop-down menu. In this realm, you can provide access to users and applications.

2. In the Add Realm window, enter a case-sensitive realm name and set the parameter Enabled to ON and click Create:

   

3. In the Realm Settings tab, set the following parameters and click Save:

   1. Enabled - ON
   2. User-Managed Access - ON

   3. Make a note of the link address of SAML 2.0 Identity Provider Metadata to paste in Client Settings.

      

4. In the Clients tab, click Create:

   

5. In the Add Client window, set the following parameters and click Save:

   1. Client ID - BASE_URL:8443/auth/saml2/metadata

      Example

      https://example.ceph.redhat.com:8443/auth/saml2/metadata

   2. Client Protocol - saml

6. In the Client window, under Settings tab, set the following parameters:

   Table 2.2. Client Settings tab

   Name of the parameter	Syntax	Example
   Client ID	BASE_URL:8443/auth/saml2/metadata	https://example.ceph.redhat.com:8443/auth/saml2/metadata
   Enabled	ON	ON
   Client Protocol	saml	saml
   Include AuthnStatement	ON	ON
   Sign Documents	ON	ON
   Signature Algorithm	RSA_SHA1	RSA_SHA1
   SAML Signature Key Name	KEY_ID	KEY_ID
   Valid Redirect URLs	BASE_URL:8443/*	https://example.ceph.redhat.com:8443/*
   Base URL	BASE_URL:8443	https://example.ceph.redhat.com:8443/
   Master SAML Processing URL	https://localhost:8080/auth/realms/REALM_NAME/protocol/saml/descriptor	https://localhost:8080/auth/realms/Ceph_LDAP/protocol/saml/descriptor

   Note

   Paste the link of SAML 2.0 Identity Provider Metadata from Realm Settings tab.

   Under Fine Grain SAML Endpoint Configuration, set the following parameters and click Save:

   Table 2.3. Fine Grain SAML configuration

   Name of the parameter	Syntax	Example
   Assertion Consumer Service POST Binding URL	BASE_URL:8443/#/dashboard	https://example.ceph.redhat.com:8443/#/dashboard
   Assertion Consumer Service Redirect Binding URL	BASE_URL:8443/#/dashboard	https://example.ceph.redhat.com:8443/#/dashboard
   Logout Service Redirect Binding URL	BASE_URL:8443/	https://example.ceph.redhat.com:8443/

7. In the Clients window, Mappers tab, set the following parameters and click Save:

   Table 2.4. Client Mappers tab

   Name of the parameter	Value
   Protocol	saml
   Name	username
   Mapper Property	User Property
   Property	username
   SAML Attribute name	username

8. In the Clients Scope tab, select role_list:

   1. In Mappers tab, select role list, set the Single Role Attribute to ON.

9. Select User_Federation tab:

   1. In User Federation window, select ldap from the drop-down menu:

   2. In User_Federation window, Settings tab, set the following parameters and click Save:

      Table 2.5. User Federation Settings tab

      Name of the parameter	Value
      Console Display Name	rh-ldap
      Import Users	ON
      Edit_Mode	READ_ONLY
      Username LDAP attribute	username
      RDN LDAP attribute	username
      UUID LDAP attribute	nsuniqueid
      User Object Classes	inetOrgPerson
      organizationalPerson	rhatPerson
      Connection URL	Example: ldap://ldap.corp.redhat.com Click Test Connection. You will get a notification that the LDAP connection is successful.
      Users DN	ou=users, dc=example, dc=com
      Bind Type	simple

      Click Test authentication. You will get a notification that the LDAP authentication is successful.

   3. In Mappers tab, select first name row and edit the following parameter and Click Save:

      • LDAP Attribute - givenName

   4. In User_Federation tab, Settings tab, Click Synchronize all users:

      

      You will get a notification that the sync of users is finished successfully.

10. In the Users tab, search for the user added to the dashboard and click the Search icon:

    

11. To view the user , click the specific row. You should see the federation link as the name provided for the User Federation.

    
    Important

    Do not add users manually as the users will not be synchronized by LDAP. If added manually, delete the user by clicking Delete.

Procedure

1. To configure SSO on Ceph Dashboard, run the following command:

   Syntax

   podman exec CEPH_MGR_HOST ceph dashboard sso setup saml2 CEPH_DASHBOARD_BASE_URL IDP_METADATA IDP_USERNAME_ATTRIBUTE IDP_ENTITY_ID SP_X_509_CERT SP_PRIVATE_KEY

   Example

   [root@host01 ~]# podman exec host01 ceph dashboard sso setup saml2 https://dashboard_hostname.ceph.redhat.com:8443 idp-metadata.xml username https://10.70.59.125:8080/auth/realms/realm_name /home/certificate.txt /home/private-key.txt

   Replace

   • CEPH_MGR_HOST with Ceph mgr host. For example, host01
   • CEPH_DASHBOARD_BASE_URL with the base URL where Ceph Dashboard is accessible.
   • IDP_METADATA with the URL to remote or local path or content of the IdP metadata XML. The supported URL types are http, https, and file.
   • Optional: IDP_USERNAME_ATTRIBUTE with the attribute used to get the username from the authentication response. Defaults to uid.
   • Optional: IDP_ENTITY_ID with the IdP entity ID when more than one entity ID exists on the IdP metadata.
   • Optional: SP_X_509_CERT with the file path of the certificate used by Ceph Dashboard for signing and encryption.
   • Optional: SP_PRIVATE_KEY with the file path of the private key used by Ceph Dashboard for signing and encryption.

2. Verify the current SAML 2.0 configuration:

   Syntax

   podman exec CEPH_MGR_HOST ceph dashboard sso show saml2

   Example

   [root@host01 ~]#  podman exec host01 ceph dashboard sso show saml2

3. To enable SSO, run the following command:

   Syntax

   podman exec CEPH_MGR_HOST ceph dashboard sso enable saml2
   SSO is "enabled" with "SAML2" protocol.

   Example

   [root@host01 ~]#  podman exec host01 ceph dashboard sso enable saml2

4. Open your dashboard URL.

   Example

   https://dashboard_hostname.ceph.redhat.com:8443

5. On the SSO page, enter the login credentials. SSO redirects to the dashboard web interface.

Procedure

1. Check if SSO is enabled:

   Syntax

   podman exec CEPH_MGR_HOST ceph dashboard sso status

   Example

   [root@host01 ~]# podman exec host01 ceph dashboard sso status
   
   SSO is "enabled" with "SAML2" protocol.

2. Disable SSO:

   Syntax

   podman exec CEPH_MGR_HOST ceph dashboard sso disable
   
   SSO is "disabled".

   Example

   [root@host01 ~]#  podman exec host01 ceph dashboard sso disable

Procedure

1. Log in to the Dashboard.

2. Click the Dashboard Settings icon and then click User management.

   
3. On Roles tab, click Create:

4. In the Create Role window, set the Name, Description, and select the Permissions for this role, and then click the Create Role button:

   

   In this example, if you give the ganesha-manager and rgw-manager roles, then the user assigned with these roles can manage all NFS-Ganesha gateway and Ceph object gateway operations.

5. You get a notification that the role was created successfully.
6. Click on the Expand/Collapse icon of the row to view the details and permissions given to the roles.

Procedure

1. Log in to the Dashboard.

2. Click the Dashboard Settings icon and then click User management.

   
3. On Roles tab, click the role you want to edit.

4. In the Edit Role window, edit the parameters, and then click Edit Role.

   
5. You get a notification that the role was updated successfully.

Procedure

1. Log in to the Dashboard.

2. Click the Dashboard Settings icon and then click User management.

   
3. On Roles tab, click the role you want to clone.
4. Select Clone from the Edit drop-down menu.

5. In the Clone Role dialog box, enter the details for the role, and then click Clone Role.

   
6. Once you clone the role, you can customize the permissions as per the requirements.

Procedure

1. Log in to the Dashboard.

2. Click the Dashboard Settings icon and then click User management.

   
3. On Roles tab, click the role you want to delete.
4. Select Delete from the Edit drop-down menu.

5. In the Delete Role dialog box, Click the Yes, I am sure box and then click Delete Role.

   

Procedure

1. Log in to the Dashboard.

2. Click the Dashboard Settings icon and then click User management.

   
3. On Users tab, click Create.

4. In the Create User window, set the Username and other parameters including the roles, and then click Create User.

   
5. You get a notification that the user was created successfully.

Procedure

1. Log in to the Dashboard.

2. Click the Dashboard Settings icon and then click User management.

   
3. To edit the user, click the row.
4. On Users tab, select Edit from the Edit drop-down menu.

5. In the Edit User window, edit parameters like password and roles, and then click Edit User.

   
   Note

   If you want to disable any user’s access to the Ceph dashboard, you can uncheck Enabled option in the Edit User window.

6. You get a notification that the user was created successfully.

Procedure

1. Log in to the Dashboard.

2. Click the Dashboard Settings icon and then click User management.

   
3. On Users tab, click the user you want to delete.
4. select Delete from the Edit drop-down menu.

5. In the Delete User dialog box, Click the Yes, I am sure box and then Click Delete User to save the settings.

   

1. Log in to the dashboard.
2. From the Cluster drop-down menu, select Services.
3. View the details of the service with the daemon to perform the action on by clicking the Expand/Collapse icon on its row.

4. In Details, select the drop down next to the desired daemon to perform Start, Stop, Restart, or Redeploy.

   Figure 5.1. Managing daemons

   

1. Log in to the dashboard.
2. From the Cluster drop-down menu, select Hosts.
3. From the Hosts List, select the host with the daemon to perform the action on.
4. In the Daemon tab of the host, click the daemon.

5. Use the drop down at the top to perform Start, Stop, Restart, or Redeploy.

   Figure 5.2. Managing daemons

   

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Hosts.
3. To view the details of a specific host, click the Expand/Collapse icon on it’s row.

4. You can view the details such as Devices, Inventory, Daemons, Performance Details, and Device Health by clicking the respective tabs.

   Figure 6.1. Monitoring hosts of the Ceph cluster

   

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Configuration.
3. Optional: You can search for the configuration using the Search box:

4. Optional: You can filter for a specific configuration using following filters:

   • Level - Basic, advanced or dev
   • Service - Any, mon, mgr, osd, mds, common, mds_client, rgw, and similar filters.
   • Source - Any, mon, and similar filters
   • Modified - yes or no

5. To view the details of the configuration, click the Expand/Collapse icon on it’s row.

   Figure 6.2. Configuration options

   

6. To edit a configuration, click its row and click Edit.

   1. In the edit dialog window, edit the required parameters and Click Update.
7. You get a notification that the configuration was updated successfully.

Viewing the manager modules

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Manager Modules.

3. To view the details of a specific manager module, click the Expand/Collapse icon on it’s row.

   Figure 6.3. Manager modules

   

Enabling a manager module

1. Select the row.
2. From the Edit drop-down menu, select Enable.

Disabling a manager module

1. Select the row.
2. From the Edit drop-down menu, select Disable.

Editing a manager module

1. Select the row:

   Note

   Not all modules have configurable parameters. If a module is not configurable, the Edit button is disabled.

2. Edit the required parameters and click Update.
3. You get a notification that the module was updated successfully.

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Monitors.

3. The Monitors overview page displays information about the overall monitor status as well as tables of in Quorum and Not in quorum Monitor hosts.

   
4. To see the number of open sessions, hover the cursor over the blue dotted trail.

5. To see performance counters for any monitor, click its hostname.

   • View the performance counter of the monitor:

     

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Services.

3. To view the details of a specific service, click the Expand/Collapse icon on it’s row.

   Figure 6.4. Monitoring services of the Ceph cluster

   

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select OSDs.

3. To view the details of a specific OSD, click the Expand/Collapse icon on it’s row.

   Figure 6.5. Monitoring OSDs of the Ceph cluster

   

   You can view additional details such as Devices, Attributes (OSD map), Metadata, Device Health, Performance counter, and Performance Details by clicking on the respective tabs.

Procedure

1. Log in to the Grafana URL and select the RGW_Overview panel:

   Syntax

   https://DASHBOARD_URL:3000

   Example

   https://dashboard_url:3000

2. Verify the HAProxy metrics on the Grafana URL.

3. Launch the Ceph dashboard and log in with your credentials.

   Example

   https://dashboard_url:8443

4. From the Cluster drop-down menu, select Object Gateway.
5. Select Daemons.
6. Select the Overall Performance tab.

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select CRUSH Map.

3. To view the details of the specific OSD, click it’s row.

   Figure 6.7. CRUSH Map detail view

   

Procedure

1. Log in to the Dashboard.

2. From the Cluster drop-down menu, select Logs.

   Figure 6.8. Cluster logs

   
   1. To filter by priority, click the Priority drop-down menu and select either Debug, Info, Warning, Error, or All.
   2. To filter by keyword, enter text into the Keyword field.
   3. To filter by date, click the Date field and either use the date picker to select a date from the menu, or enter a date in the form of YYYY-MM-DD.
   4. To filter by time, enter a range in the Time range fields using the HH:MM - HH:MM format. Hours must be entered using numbers 0 to 23.
   5. To combine filters, set two or more filters.
3. Click the Download icon or Copy to Clipboard icon to download the logs.

Procedure

1. Log in to the Dashboard.
2. On the navigation bar, select Pools.
3. View the pools list which gives the details of Data protection and the application for which the pool is enabled. Hover the mouse over Usage, Read bytes, and Write bytes for the required details.

4. To view more information about a pool, click the Expand/Collapse icon on it’s row.

   Figure 6.9. Monitoring pools

   

Procedure

1. Log in to the dashboard.
2. On the navigation bar, click Filesystems.

3. To view more information about the file system, click the Expand/Collapse icon on it’s row.

   Figure 6.10. Monitoring Ceph File Systems

   

Procedure

1. Log in to the dashboard.
2. On the navigation bar, click Object Gateway.

3. To view more information about the Ceph object gateway daemon, click the Expand/Collapse icon on it’s row.

   Figure 6.11. Monitoring Ceph object gateway daemons

   

   If you have configured multiple Ceph Object Gateway daemons, click on Sync Performance tab and view the multi-site performance counters.

Procedure

1. Log in to the dashboard.
2. On the navigation bar, click Block.

3. To view more information about the images, click the Expand/Collapse icon on it’s row.

   Figure 6.12. Monitoring Block device images

   

Procedure

1. Log into the cephadm shell:

   Example

   [root@host01 ~]# cephadm shell

2. Set the APIs for the monitoring stack:

   • Specify the host and port of the Alertmanager server:

     Syntax

     ceph dashboard set-alertmanager-api-host 'ALERTMANAGER_API_HOST:PORT'

     Example

     [ceph: root@host01 /]# ceph dashboard set-alertmanager-api-host 'http://10.0.0.101:9093'
     Option ALERTMANAGER_API_HOST updated

   • To see the configured alerts, configure the URL to the Prometheus API. Using this API, the Ceph Dashboard UI verifies that a new silence matches a corresponding alert.

     Syntax

     ceph dashboard set-prometheus-api-host 'PROMETHEUS_API_HOST:PORT'

     Example

     [ceph: root@host01 /]# ceph dashboard set-prometheus-api-host 'http://10.0.0.101:9095'
     Option PROMETHEUS_API_HOST updated

     After setting up the hosts, refresh your browser’s dashboard window.

   • Specify the host and port of the Grafana server:

     Syntax

     ceph dashboard set-grafana-api-url 'GRAFANA_API_URL:PORT'

     Example

     [ceph: root@host01 /]# ceph dashboard set-grafana-api-url 'http://10.0.0.101:3000'
     Option GRAFANA_API_URL updated

3. Get the Prometheus, Alertmanager, and Grafana API host details:

   Example

   [ceph: root@host01 /]# ceph dashboard get-alertmanager-api-host
   http://10.0.0.101:9093
   [ceph: root@host01 /]# ceph dashboard get-prometheus-api-host
   http://10.0.0.101:9095
   [ceph: root@host01 /]# ceph dashboard get-grafana-api-url
   http://10.0.0.101:3000

4. Optional: If you are using a self-signed certificate in your Prometheus, Alertmanager, or Grafana setup, disable the certificate verification in the dashboard This avoids refused connections caused by certificates signed by an unknown Certificate Authority (CA) or that do not match the hostname.

   • For Prometheus:

     Example

     [ceph: root@host01 /]# ceph dashboard set-prometheus-api-ssl-verify False

   • For Alertmanager:

     Example

     [ceph: root@host01 /]# ceph dashboard set-alertmanager-api-ssl-verify False

   • For Grafana:

     Example

     [ceph: root@host01 /]# ceph dashboard set-grafana-api-ssl-verify False

5. Get the details of the self-signed certificate verification setting for Prometheus, Alertmanager, and Grafana:

   Example

   [ceph: root@host01 /]# ceph dashboard get-prometheus-api-ssl-verify
   [ceph: root@host01 /]# ceph dashboard get-alertmanager-api-ssl-verify
   [ceph: root@host01 /]# ceph dashboard get-grafana-api-ssl-verify

6. Optional: If the dashboard does not reflect the changes, you have to disable and then enable the dashboard:

   Example

   [ceph: root@host01 /]# ceph mgr module disable dashboard
   [ceph: root@host01 /]# ceph mgr module enable dashboard

Procedure

1. Log into the cephadm shell:

   Example

   [root@host01 ~]# cephadm shell

2. Configure the custom certificate for Grafana:

   Example

   [ceph: root@host01 /]# ceph config-key set mgr/cephadm/grafana_key -i $PWD/key.pem
   [ceph: root@host01 /]# ceph config-key set mgr/cephadm/grafana_crt -i $PWD/certificate.pem

3. If Grafana is already deployed, then run reconfig to update the configuration:

   Example

   [ceph: root@host01 /]# ceph orch reconfig grafana

4. Every time a new certificate is added, follow the below steps:

   1. Make a new directory

      Example

      [root@host01 ~]# mkdir /root/internalca
      [root@host01 ~]# cd /root/internalca

   2. Generate the key:

      Example

      [root@host01 internalca]# openssl ecparam -genkey -name secp384r1 -out $(date +%F).key

   3. View the key:

      Example

      [root@host01 internalca]# openssl ec -text -in $(date +%F).key | less

   4. Make a request:

      Example

      [root@host01 internalca]# umask 077; openssl req -config openssl-san.cnf -new -sha256 -key $(date +%F).key -out $(date +%F).csr

   5. Review the request prior to sending it for signature:

      Example

      [root@host01 internalca]# openssl req -text -in $(date +%F).csr | less

   6. As the CA sign:

      Example

      [root@host01 internalca]# openssl ca -extensions v3_req -in $(date +%F).csr -out $(date +%F).crt -extfile openssl-san.cnf

   7. Check the signed certificate:

      Example

      [root@host01 internalca]# openssl x509 -text -in $(date +%F).crt -noout | less

Procedure

1. Log into the cephadm shell:

   Example

   [root@host01 ~]# cephadm shell

2. Configure the Alertmanager to use the webhook for notification:

   Syntax

   service_type: alertmanager
   spec:
     user_data:
       default_webhook_urls:
       - "_URLS_"

   The default_webhook_urls is a list of additional URLs that are added to the default receivers' webhook_configs configuration.

   Example

   service_type: alertmanager
   spec:
     user_data:
       webhook_configs:
       - url: 'http:127.0.0.10:8080'

3. Update Alertmanager configuration:

   Example

   [ceph: root@host01 /]#  ceph orch reconfig alertmanager

Procedure

1. Log in to the Dashboard.

2. Customize the alerts module on the dashboard to get an email alert for the storage cluster:

   1. On the navigation menu, click Cluster.
   2. Select Manager modules.
   3. Select alerts module.
   4. In the Edit drop-down menu, select Edit.

   5. In the Edit Manager module window, update the required parameters and click Update.

      Figure 7.2. Edit Manager module for alerts

      
3. On the navigation menu, click Cluster.
4. Select Monitoring from the drop-down menu.

5. To view details of the alert, click the Expand/Collapse icon on it’s row.

   Figure 7.3. Viewing alerts

   
6. To view the source of an alert, click on its row, and then click Source.

Procedure

1. Log in to the Dashboard.
2. On the navigation menu, click Cluster.
3. Select Monitoring from the drop-down menu.
4. To create silence for an alert, select it’s row.
5. Click +Create Silence.

6. In the Create Silence window, Add the details for the Duration and click Create Silence.

   Figure 7.4. Create Silence

   
7. You get a notification that the silence was created successfully.

Procedure

1. Log in to the Dashboard.
2. On the navigation menu, click Cluster.
3. Select Monitoring from the drop-down menu.
4. Click the Silences tab.
5. To recreate an expired silence, click it’s row.
6. Click the Recreate button.

7. In the Recreate Silence window, add the details and click Recreate Silence.

   Figure 7.5. Recreate silence

   
8. You get a notification that the silence was recreated successfully.

Procedure

1. Log in to the Dashboard.
2. On the navigation menu, click Cluster.
3. Select Monitoring from the drop-down menu.
4. Click the Silences tab.
5. To edit the silence, click it’s row.
6. In the Edit drop-down menu, select Edit.

7. In the Edit Silence window, update the details and click Edit Silence.

   Figure 7.6. Edit silence

   
8. You get a notification that the silence was updated successfully.

Procedure

1. Log in to the Dashboard.
2. On the navigation menu, click Cluster.
3. Select Monitoring from the drop-down menu.
4. Click the Silences tab.
5. To expire a silence, click it’s row.
6. In the Edit drop-down menu, select Expire.

7. In the Expire Silence dialog box, select Yes, I am sure, and then click Expire Silence.

   Figure 7.7. Expire Silence

   
8. You get a notification that the silence was expired successfully.

Procedure

1. Log into the Cephadm shell:

   Example

   [root@host01 ~]# cephadm shell

2. Create the RADOS pool, namespace, and enable rgw:

   Syntax

   ceph osd pool create POOL_NAME _
   ceph osd pool application enable POOL_NAME freeform/rgw/rbd/cephfs/nfs

   Example

   [ceph: root@host01 /]# ceph osd pool create nfs-ganesha
   [ceph: root@host01 /]# ceph osd pool application enable nfs-ganesha rgw

3. Deploy NFS-Ganesha gateway using placement specification in the command line interface:

   Syntax

   ceph orch apply nfs SERVICE_ID --placement="NUMBER_OF_DAEMONS HOST_NAME_1 HOST_NAME_2 HOST_NAME_3"

   Example

   [ceph: root@host01 /]# ceph orch apply nfs foo --placement="2 host01 host02"

   This deploys an NFS-Ganesha cluster nfsganesha with one daemon on host01 and host02.

4. Update ganesha-clusters-rados-pool-namespace parameter with the namespace and the service_ID:

   Syntax

   ceph dashboard set-ganesha-clusters-rados-pool-namespace POOL_NAME/SERVICE_ID

   Example

   [ceph: root@host01 /]# ceph dashboard set-ganesha-clusters-rados-pool-namespace nfs-ganesha/foo

5. On the dashboard landing page, click NFS.
6. Select Create.

7. In the Create NFS export window, set the following parameters and click Create NFS export:

   1. Cluster - Name of the cluster.
   2. Daemons - You can select all daemons.
   3. Storage Backend - You can select Object Gateway.
   4. Object Gateway User - Select the user created. In this example, it is test_user.
   5. Path - Any directory.
   6. NFS Protocol - NFSv4 is selected by default.
   7. Pseudo - root path
   8. Access Type - The supported access types are RO, RW, and NONE.
   9. Squash
   10. Transport Protocol

   11. Clients

       

8. Verify the NFS daemon is configured:

   Example

   [ceph: root@host01 /]# ceph -s

9. As a root user, check if the NFS-service is active and running:

   Example

   [root@host01 ~]# systemctl list-units | grep nfs

10. Mount the NFS export and perform a few I/O operations.
11. Once the NFS service is up and running, in the NFS-RGW container, comment out the dir_chunk=0 parameter in etc/ganesha/ganesha.conf file. Restart the NFS-Ganesha service. This allows proper listing at the NFS mount.

Procedure

1. Log in to the cephadm shell:

   Example

   [root@host01 ~]# cephadm shell

2. Create the CephFS storage in the backend:

   Syntax

   ceph fs volume create CEPH_FILE_SYSTEM

   Example

   [ceph: root@host01 /]# ceph fs volume create cephfs

3. Enable the Ceph Manager NFS module:

   Example

   [ceph: root@host01 /]# ceph mgr module enable nfs

4. Create an NFS Ganesha cluster:

   Syntax

   ceph nfs cluster create NFS_CLUSTER_NAME "HOST_NAME_PLACEMENT_LIST"

   Example

   [ceph: root@host01 /]# ceph nfs cluster create nfs-cephfs host02
   NFS Cluster Created Successfully

5. Get the dashboard URL:

   Example

   [ceph: root@host01 /]# ceph mgr services
   {
       "dashboard": "https://10.00.00.11:8443/",
       "prometheus": "http://10.00.00.11:9283/"
   }

6. Log in to the Ceph dashboard with your credentials.
7. On the dashboard landing page, click NFS.
8. Click Create.

9. In the Create NFS export window, set the following parameters and click Create NFS export:

   1. Cluster - Name of the cluster.
   2. Daemons - You can select all daemons.
   3. Storage Backend - You can select CephFS.
   4. CephFS User ID - Select the service where the NFS cluster is created.
   5. CephFS Name - Provide a user name.
   6. CephFs Path - Any directory.
   7. NFS Protocol - NFSv4 is selected by default.
   8. Pseudo - root path
   9. Access Type - The supported access types are RO, RW, and NONE.
   10. Squash - Select the squash type.
   11. Transport Protocol - Select either the UDP or TCP protocol.

   12. Clients

       Figure 8.1. CephFS NFS export window

       

10. As a root user on the client host, create a directory and mount the NFS export:

    Syntax

    mkdir -p /mnt/nfs/
    mount -t nfs -o port=2049 HOSTNAME:EXPORT_NAME _MOUNT_DIRECTORY_

    Example

    [root@ client ~]# mkdir -p /mnt/nfs/
    [root@ client ~]# mount -t nfs -o port=2049 host02:/export1 /mnt/nfs/

Procedure

1. On the dashboard, click NFS.
2. Click the row that needs to be edited.
3. From the Edit drop-down menu, click Edit.

4. In the Edit NFS export window, edit the required parameters and click Edit NFS export.

   

Procedure

1. On the dashboard, click NFS.
2. Click the row that needs to be delete.
3. From the Edit drop-down menu, click Delete.

4. In the Delete NFS export dialog box, check Yes, I am sure and click Delete NFS export.

   

Procedure

1. On the dashboard, click Cluster.
2. From the Cluster drop-down menu, click Services.
3. Click + Create.
4. In the Create Service window, select ingress service.

5. Select the required backend service, edit the required parameters, and click Create Service to upgrade.

   Figure 8.2. Create Service window

   

Procedure

1. Log in to the dashboard.
2. On the navigation menu, click Pools.
3. Click Create.

4. In the Create Pool window, set the following parameters:

   Figure 9.1. Creating pools

   
   1. Set the name of the pool and select the pool type.
   2. Select either replicated or Erasure Coded (EC) pool type.
   3. Set the Placement Group (PG) number.
   4. Optional: If using a replicated pool type, set the replicated size.
   5. Optional: If using an EC pool type configure the following additional settings.
   6. Optional: To see the settings for the currently selected EC profile, click the question mark.
   7. Optional: Add a new EC profile by clicking the plus symbol.
   8. Optional: Click the pencil symbol to select an application for the pool.
   9. Optional: Set the CRUSH rule, if applicable.
   10. Optional: If compression is required, select passive, aggressive, or force.
   11. Optional: Set the Quotas.
   12. Optional: Set the Quality of Service configuration.
5. Click Create Pool.
6. You get a notification that the pool was created successfully.

Procedure

1. Log in to the dashboard.
2. On the navigation menu, click Pools.
3. To edit the pool, click its row.
4. Select Edit In the Edit drop-down.

5. In the Edit Pool window, edit the required parameters and click Edit Pool:

   Figure 9.2. Editing pools

   
6. You get a notification that the pool was created successfully.

Procedure

1. Log in to the dashboard.
2. On the navigation bar, in Cluster drop-down menu, click Configuration.
3. In the Level drop-down menu, select Advanced:
4. Search for mon_allow_pool_delete, click Edit

5. Set all the values to true:

   Figure 9.3. Configuration to delete pools

   
6. On the navigation bar, click Pools:
7. To delete the pool, click on its row:
8. From Edit drop-down menu, select Delete.

9. In the Delete Pool window, Click the Yes, I am sure box and then Click Delete Pool to save the settings:

   Figure 9.4. Delete pools

   

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Hosts.
3. Select a host from the list.

4. From the Edit drop-down menu, click Enter Maintenance.

   Figure 10.1. Entering maintenance mode

   
   Note

   When a host enters maintenance, all daemons are stopped. You can check the status of the daemons under the Daemons tab of a host.

Verification

1. You get a notification that the host is successfully moved to maintenance and a maintenance label appears in the Status column.

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Hosts.

3. From the Hosts List, select the host in maintenance.

   Note

   You can identify the host in maintenance by checking for the maintenance label in the Status column.

4. From the Edit drop-down menu, click Exit Maintenance.

   Figure 10.2. Exiting maintenance mode

   

   After exiting the maintenance mode, you need to create the required services on the host by default-crash and the node-exporter gets deployed.

Verification

1. You get a notification that the host has been successfully moved out of maintenance and the maintenance label is removed from the Status column.

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Hosts.
3. From the Hosts List, select the host you want to remove.

4. From the Edit drop-down menu, click Start Drain.

   Figure 10.3. Selecting Start Drain option

   

   This option drains all the daemons from the host.

   Note

   The _no_schedule label is automatically applied to the host, which blocks the deployment of daemons on this host.

   1. Optional: to stop the draining of daemons from the host, click Stop Drain option from the Edit drop-down menu.

5. Check if all the daemons are removed from the host.

   1. Click the Expand/Collapse icon on it’s row

   2. Select Daemons. No daemons should be listed.

      Figure 10.4. Checking the status of host daemons

      
      Important

      A host can be safely removed from the cluster after all the daemons are removed from it.

6. Remove the host.

   1. From the Edit drop-down menu, click Remove.

      Figure 10.5. Removing the host

      

   2. In the Remove Host dialog box, check Yes, I am sure. and click Remove Host.

      

Verification

1. You get a notification after the successful removal of the host from the Hosts List.

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select OSDs.

Creating an OSD

1. To create the OSD, click Create.

   Figure 11.1. Add device for OSDs

   
   Note

   Ensure you have an available host and a few available devices. You can check for available devices in Physical Disks under the Cluster drop-down menu.

   1. In the Create OSDs window, from Deployment Options, select one of the below options:

      • Cost/Capacity-optimized: The cluster gets deployed with all available HDDs.
      • Throughput-optimized: Slower devices are used to store data and faster devices are used to store journals/WALs.
      • IOPS-optmized: All the available NVMEs are used to deploy OSDs.

   2. From the Advanced Mode, you can add primary, WAL and DB devices by clicking +Add.

      • Primary devices: Primary storage devices contain all OSD data.
      • WAL devices: Write-Ahead-Log devices are used for BlueStore’s internal journal and are used only if the WAL device is faster than the primary device. For example, NVMEs or SSDs.
      • DB devices: DB devices are used to store BlueStore’s internal metadata and are used only if the DB device is faster than the primary device. For example, NVMEs or SSDs).
   3. If you want to encrypt your data for security purposes, under Features, select encryption.
   4. Click the Preview button and in the OSD Creation Preview dialog box, Click Create.
   5. In the OSD Creation Preview dialog box, Click Create.
2. You get a notification that the OSD was created successfully.
3. The OSD status changes from in and down to in and up.

Editing an OSD

1. To edit an OSD, select the row.

   1. From Edit drop-down menu, select Edit.
   2. Edit the device class.

   3. Click Edit OSD.

      Figure 11.2. Edit an OSD

      
   4. You get a notification that the OSD was updated successfully.

Marking the Flags of OSDs

1. To mark the flag of the OSD, select the row.

   1. From Edit drop-down menu, select Flags.
   2. Mark the Flags with No Up, No Down, No In, or No Out.

   3. Click Update.

      Figure 11.3. Marking Flags of an OSD

      
   4. You get a notification that the flags of the OSD was updated successfully.

Scrubbing the OSDs

1. To scrub the OSD, select the row.

   1. From Edit drop-down menu, select Scrub.

   2. In the OSDs Scrub dialog box, click Update.

      Figure 11.4. Scrubbing an OSD

      
   3. You get a notification that the scrubbing of the OSD was initiated successfully.

Deep-scrubbing the OSDs

1. To deep-scrub the OSD, select the row.

   1. From Edit drop-down menu, select Deep scrub.

   2. In the OSDs Deep Scrub dialog box, click Update.

      Figure 11.5. Deep-scrubbing an OSD

      
   3. You get a notification that the deep scrubbing of the OSD was initiated successfully.

Reweighting the OSDs

1. To reweight the OSD, select the row.

   1. From Edit drop-down menu, select Reweight.
   2. In the Reweight OSD dialog box, enter a value between zero and one.

   3. Click Reweight.

      Figure 11.6. Reweighting an OSD

      

Marking OSDs Out

1. To mark the OSD out, select the row.

   1. From Edit drop-down menu, select Mark Out.

   2. In the Mark OSD out dialog box, click Mark Out.

      Figure 11.7. Marking OSDs out

      
   3. The status of the OSD will change to out.

Marking OSDs In

1. To mark the OSD in, select the OSD row that is in out status.

   1. From Edit drop-down menu, select Mark In.

   2. In the Mark OSD in dialog box, click Mark In.

      Figure 11.8. Marking OSDs in

      
   3. The status of the OSD will change to in.

Marking OSDs Down

1. To mark the OSD down, select the row.

   1. From Edit drop-down menu, select Mark Down.

   2. In the Mark OSD down dialog box, click Mark Down.

      Figure 11.9. Marking OSDs down

      
   3. The status of the OSD will change to down.

Marking OSDs Lost

1. To mark the OSD lost, select the OSD in out and down status.

   1. From Edit drop-down menu, select Mark Lost.

   2. In the Mark OSD Lost dialog box, check Yes, I am sure option, and click Mark Lost.

      Figure 11.10. Marking OSDs Lost

      

Purging OSDs

1. To purge the OSD, select the OSD in down status.

   1. From Edit drop-down menu, select Purge.

   2. In the Purge OSDs dialog box, check Yes, I am sure option, and click Purge OSD.

      Figure 11.11. Purging OSDs

      
   3. All the flags are reset and the OSD is back in in and up status.

Destroying OSDs

1. To destroy the OSD, select the OSD in down status.

   1. From Edit drop-down menu, select Destroy.

   2. In the Destroy OSDs dialog box, check Yes, I am sure option, and click Destroy OSD.

      Figure 11.12. Destroying OSDs

      
   3. The status of the OSD changes to destroyed.

Deleting OSDs

1. To delete the OSD, select the OSD in down status.

   1. From Edit drop-down menu, select Delete.

   2. In the Destroy OSDs dialog box, check Yes, I am sure option, and click Delete OSD.

      Note

      You can preserve the OSD_ID when you have to to replace the failed OSD.

      Figure 11.13. Deleting OSDs

      

Procedure

1. On the dashboard, you can identify the failed OSDs in the following ways:

   • Dashboard AlertManager pop-up notifications.
   • Dashboard landing page showing HEALTH_WARN status.
   • Dashboard landing page showing failed OSDs.

   • Dashboard OSD page showing failed OSDs.

     

     In this example, you can see that one of the OSDs is down on the landing page of the dashboard.

     Apart from this, on the physical drive, you can view the LED lights blinking if one of the OSDs is down.

2. Click OSDs.

3. Select the out and down OSD:

   1. From the Edit drop-down menu, select Flags and select No Up and click Update.
   2. From the Edit drop-down menu, select Delete.
   3. In the Delete OSD dialog box, select the Preserve OSD ID(s) for replacement and Yes, I am sure check boxes.
   4. Click Delete OSD.
   5. Wait till the status of the OSD changes to out and destroyed status.

4. Optional: If you want to change the No Up Flag for the entire cluster, in the Cluster-wide configuration drop-down menu, select Flags.

   1. In Cluster-wide OSDs Flags dialog box, select No Up and click Update.

5. Optional: If the OSDs are down due to a hard disk failure, replace the physical drive:

   • If the drive is hot-swappable, replace the failed drive with a new one.
   • If the drive is not hot-swappable and the host contains multiple OSDs, you might have to shut down the whole host and replace the physical drive. Consider preventing the cluster from backfilling. See the Stopping and Starting Rebalancing chapter in the Red Hat Ceph Storage Troubleshooting Guide for details.
   • When the drive appears under the /dev/ directory, make a note of the drive path.
   • If you want to add the OSD manually, find the OSD drive and format the disk.

   • If the new disk has data, zap the disk:

     Syntax

     ceph orch device zap HOST_NAME PATH --force

     Example

     ceph orch device zap ceph-adm2 /dev/sdc --force

6. From the Create drop-down menu, select Create.

7. In the Create OSDs window, click +Add for Primary devices.

   1. In the Primary devices dialog box, from the Hostname drop-down list, select any one filter. From Any drop-down list, select the respective option.

      Note

      You have to select the Hostname first and then at least one filter to add the devices.

      For example, from Hostname list, select Type and from Any list select hdd. Select Vendor and from Any list, select ATA

      
   2. Click Add.
   3. In the Create OSDs window, click the Preview button.
   4. In the OSD Creation Preview dialog box, Click Create.
   5. You will get a notification that the OSD is created. The OSD will be in out and down status.

8. Select the newly created OSD that has out and down status.

   1. In the Edit drop-down menu, select Mark-in.
   2. In the Mark OSD in window, select Mark in.
   3. In the Edit drop-down menu, select Flags.
   4. Uncheck No Up and click Update.

9. Optional: If you have changed the No Up Flag before for cluster-wide configuration, in the Cluster-wide configuration menu, select Flags.

   1. In Cluster-wide OSDs Flags dialog box, uncheck No Up and click Update.

Verification

1. Verify that the OSD that was destroyed is created on the device and the OSD ID is preserved.

   

Procedure

1. Log into the Cephadm shell:

   Example

   [root@host01 ~]# cephadm shell

2. Set up the credentials manually:

   Example

   [ceph: root@host01 /]# ceph dashboard set-rgw-credentials

   This creates a Ceph Object Gateway user with UID dashboard for each realm in the system.

3. Optional: If you have configured a custom admin resource in your Ceph Object Gateway admin API, you have to also set the the admin resource:

   Syntax

   ceph dashboard set-rgw-api-admin-resource RGW_API_ADMIN_RESOURCE

   Example

   [ceph: root@host01 /]# ceph dashboard set-rgw-api-admin-resource admin
   Option RGW_API_ADMIN_RESOURCE updated

4. Optional: If you are using HTTPS with a self-signed certificate, disable certificate verification in the dashboard to avoid refused connections.

   Refused connections can happen when the certificate is signed by an unknown Certificate Authority, or if the host name used does not match the host name in the certificate.

   Syntax

   ceph dashboard set-rgw-api-ssl-verify false

   Example

   [ceph: root@host01 /]# ceph dashboard set-rgw-api-ssl-verify False
   Option RGW_API_SSL_VERIFY updated

5. Optional: If the Object Gateway takes too long to process requests and the dashboard runs into timeouts, you can set the timeout value:

   Syntax

   ceph dashboard set-rest-requests-timeout _TIME_IN_SECONDS_

   The default value of 45 seconds.

   Example

   [ceph: root@host01 /]# ceph dashboard set-rest-requests-timeout 240

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Services.
3. Click +Create.
4. In the Create Service window, select rgw service.

5. Select SSL and upload the Certificate in .pem format.

   Figure 12.1. Creating Ceph Object Gateway service

   
6. Click Create Service.
7. Check the Ceph Object Gateway service is up and running.

Procedure

1. Log in to the Dashboard.
2. From the Cluster drop-down menu, select Services.
3. Click +Create.
4. In the Create Service window, select ingress service.

5. Select backend service and edit the required parameters.

   Figure 12.2. Creating ingress service

   
6. Click Create Service.
7. You get a notification that the ingress service was created successfully.

Procedure

1. On the Dashboard landing page of the secondary site, in the vertical menu bar, click Object Gateway drop-down list.
2. Select Buckets.

3. You can see those object gateway buckets on the secondary landing page that were created for the object gateway users on the primary site.

   Figure 12.10. Multisite object gateway monitoring