Chapter 4. Verify native CephFS back end deployment

Deploying native CephFS as a back end of the Shared File Systems service (manila) adds the following new elements to the overcloud environment:

  • Storage provider network
  • Ceph MDS service on the Controller nodes

For more information about using the Shared File Systems service with native CephFS, see Configuring the Shared File Systems service (manila) in the Storage Guide.

The cloud administrator must verify the stability of the native CephFS environment before making it available to service users.

Prerequisites

4.1. Verifying creation of isolated storage network

The network_data.yaml file used to deploy native CephFS as a Shared File Systems service back end creates the storage VLAN. Use this procedure to confirm you successfully created the storage VLAN.

Procedure

  1. Log in to one of the Controller nodes in the overcloud.

  2. Check the connected networks and verify the existence of the VLAN as set in the network_data.yaml file: 

    $ ip a
8: vlan30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 52:9c:82:7a:d4:75 brd ff:ff:ff:ff:ff:ff
    inet 172.17.3.144/24 brd 172.17.3.255 scope global vlan30
       valid_lft forever preferred_lft forever
    inet6 fe80::509c:82ff:fe7a:d475/64 scope link
       valid_lft forever preferred_lft forever

4.2. Verifying Ceph MDS service

Use the systemctl status command to verify the Ceph MDS service status.

Procedure

  • Enter the following command on all Controller nodes to check the status of the MDS container: 

    $ systemctl status ceph-mds<@CONTROLLER-HOST>

    Example: 

$ systemctl status ceph-mds@controller-0.service

ceph-mds@controller-0.service - Ceph MDS
   Loaded: loaded (/etc/systemd/system/ceph-mds@.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-09-18 20:11:53 UTC; 6 days ago
 Main PID: 65066 (conmon)
   Tasks: 16 (limit: 204320)
   Memory: 38.2M
   CGroup: /system.slice/system-ceph\x2dmds.slice/ceph-mds@controller-0.service
         └─60921 /usr/bin/podman run --rm --net=host --memory=32000m --cpus=4 -v
/var/lib/ceph:/var/lib/ceph:z -v /etc/ceph:/etc/ceph:z -v
/var/run/ceph:/var/run/ceph:z -v /etc/localtime:/etc/localtime:ro>

4.3. Verifying Ceph cluster status

Verify the Ceph cluster status to confirm that the cluster is active.

Procedure

  1. Log in to any Controller node.

  2. From the Ceph monitor daemon, enter the following command: 

    $ sudo podman exec ceph-mon-controller-0 ceph -s
  cluster:
    id:     670dc288-cd36-4772-a4fc-47287f8e2ebf
    health: HEALTH_OK

  services:
    mon: 3 daemons, quorum controller-1,controller-2,controller-0 (age 14h)
    mgr: controller-1(active, since 8w), standbys: controller-0, controller-2
    mds: cephfs:1 {0=controller-2=up:active} 2 up:standby
    osd: 15 osds: 15 up (since 8w), 15 in (since 8w)

  task status:
    scrub status:
        mds.controller-2: idle

  data:
    pools: 6 pools, 192 pgs
    objects: 309 objects, 1.6 GiB
    usage: 21 GiB used, 144 GiB / 165 GiB avail
    pgs: 192 active+clean
    Note

    There is one active MDS and two MDSs on standby.

  3. To see a detailed status of the Ceph File System, enter the following command: 

    $ sudo ceph fs ls

name: cephfs metadata pool: manila_metadata, data pools: [manila_data]
    Note

    In this example output, cephfs is the name of Ceph File System that director creates to host CephFS shares that users create through the Shared File Systems service.

4.4. Verifying manila-share service status

Verify the status of the manila-share service.

Procedure

  1. From one of the Controller nodes, confirm that openstack-manila-share started: 

    $ sudo pcs status resources | grep manila

* Container bundle: openstack-manila-share [cluster.common.tag/rhosp16-openstack-manila-share:pcmklatest]:
* openstack-manila-share-podman-0	(ocf::heartbeat:podman):	Started controller-0

4.5. Verifying manila-api services acknowledges scheduler and share services

Complete the following steps to confirm that the manila-api service acknowledges the scheduler and share services.

Procedure

  1. Log in to the undercloud.

  2. Enter the following command: 

    $ source /home/stack/overcloudrc

  3. Enter the following command to confirm manila-scheduler and manila-share are enabled: 

    $ manila service-list

| Id | Binary          | Host             | Zone | Status | State | Updated_at |

| 2 | manila-scheduler | hostgroup        | nova | enabled | up | 2018-08-08T04:15:03.000000 |
| 5 | manila-share | hostgroup@cephfs | nova | enabled | up | 2018-08-08T04:15:03.000000 |