Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 3. Verifying successful CephFS via NFS deployment

Deploying CephFS via NFS as a back end of OpenStack Shared File System service (manila) adds new elements to the overcloud environment.

The new overcloud elements are:

  • StorageNFS network
  • Ceph MDS service on the controllers
  • NFS-Ganesha service on the controllers

See the Shared File System service chapter in the Storage Guide for additional information about using the Shared File System service with CephFS via NFS.

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

Prerequisites

The network_data_ganesha.yaml file used to deploy CephFS via NFS as a Shared File Services system back end creates the StorageNFS VLAN: 

- name: StorageNFS
  enabled: true
  vip: true
  name_lower: storage_nfs
  vlan: 310
  ip_subnet: '172.16.4.0/24'
  allocation_pools: [{'start': '172.16.4.4', 'end': '172.16.4.250'}]
  ipv6_subnet: 'fd00:fd00:fd00:7000::/64'
  IPv6_allocation_pools: [{'start': 'fd00:fd00:fd00:7000::10', 'end': 'fd00:fd00:fd00:7000:ffff:ffff:ffff:fffe'}]
Copy to Clipboard Toggle word wrap

Complete the following steps to verify the existence of the isolated StorageNFS network.

Procedure

  1. Log in to one of the controllers in the overcloud.

  2. Run the following command to check the connected networks and verify the existence of the VLAN as set in network_data_ganesha.yaml: 

    $ ip a
15: vlan310: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 32:80:cf:0e:11:ca brd ff:ff:ff:ff:ff:ff
    inet 172.16.4.4/24 brd 172.16.4.255 scope global vlan310
       valid_lft forever preferred_lft forever
    inet 172.16.4.7/32 brd 172.16.4.255 scope global vlan310
       valid_lft forever preferred_lft forever
    inet6 fe80::3080:cfff:fe0e:11ca/64 scope link
       valid_lft forever preferred_lft forever
    Copy to Clipboard Toggle word wrap

3.2. Verifying Ceph MDS service
Copy link

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

Procedure

  1. Run the following command on all controllers to check the status of the MDS docker container: 

    $ systemctl status ceph-mds@<CONTROLLER-HOST>
    Copy to Clipboard Toggle word wrap

    Example: 

    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 (docker-current)
   CGroup: /system.slice/system-ceph\x2dmds.slice/ceph-mds@controller-0.service
           └─65066 /usr/bin/docker-current run --rm --net=host --memory=4g --cpu-quota=100000 -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/...
    Copy to Clipboard Toggle word wrap

3.3. Verifying Ceph cluster status
Copy link

Complete the following steps to verify Ceph cluster status.

Procedure

  1. Log in to the active controller.

  2. Run the following command: 

    $ sudo ceph -s

cluster:
    id: 3369e280-7578-11e8-8ef3-801844eeec7c
    health: HEALTH_OK

  services:
    mon: 3 daemons, quorum overcloud-controller-1,overcloud-controller-2,overcloud-controller-0
    mgr: overcloud-controller-1(active), standbys: overcloud-controller-2, overcloud-controller-0
    mds: cephfs-1/1/1 up  {0=overcloud-controller-0=up:active}, 2 up:standby
    osd: 6 osds: 6 up, 6 in
    Copy to Clipboard Toggle word wrap
    Note

    Notice there is one active MDS and two MDSs on standby.

  3. To check the status of the Ceph file system in more detail, run the following command where <cephfs> is the name of the Ceph file system: 

    $ sudo ceph fs ls

name: cephfs, metadata pool: manila_metadata, data pools: [manila_data]
    Copy to Clipboard Toggle word wrap

Complete the following step to verify the status of NFS-Ganesha and manila-share service.

Procedure

  1. Run the following command from one of the controllers to confirm that ceph-nfs and openstack-manila-share started: 

    $ pcs status

ceph-nfs       (systemd:ceph-nfs@pacemaker):   Started overcloud-controller-1

Docker container: openstack-manila-share [192.168.24.1:8787/rhosp13/openstack-manila-share:pcmklatest]
   openstack-manila-share-docker-0      (ocf::heartbeat:docker):        Started overcloud-controller-1
    Copy to Clipboard Toggle word wrap

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

Procedure

  1. Log in to the undercloud.

  2. Run the following command: 

    $ source /home/stack/overcloudrc
    Copy to Clipboard Toggle word wrap

  3. Run 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 |
    Copy to Clipboard Toggle word wrap
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat