Chapter 3. Verifying successful CephFS through NFS deployment When you deploy CephFS through NFS as a back end of the Shared File Systems service (manila), you add the following new elements to the overcloud environment: StorageNFS network Ceph MDS service on the controllers NFS-Ganesha service on the controllers For more information about using the Shared File Systems service with CephFS through NFS, see Shared File Systems service in the Storage Guide . As the cloud administrator, you must verify the stability of the CephFS through NFS environment before you make it available to service users. 3.1. Verifying creation of isolated StorageNFS network The network_data_ganesha.yaml file used to deploy CephFS through NFS as a Shared File Systems service back end creates the StorageNFS VLAN. Complete the following steps to verify the existence of the isolated StorageNFS network. Prerequisites Complete the steps in Chapter 2, CephFS through NFS installation Procedure Log in to one of the controllers in the overcloud. Enter the following command to check the connected networks and verify the existence of the VLAN as set in network_data_ganesha.yaml : 3.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: 3.3. Verifying Ceph cluster status Complete the following steps to verify Ceph cluster status. Procedure Log in to the active Controller node. Enter the following command: Result Notice there is one active MDS and two MDSs on standby. To check the status of the Ceph file system in more detail, enter the following command and replace <cephfs> with the name of the Ceph file system: 3.4. Verifying NFS-Ganesha and manila-share service status Complete the following step to verify the status of NFS-Ganesha and manila-share service. Procedure Enter the following command from one of the Controller nodes to confirm that ceph-nfs and openstack-manila-share started: 3.5. Verifying manila-api services acknowledges scheduler and share services Complete the following steps to confirm the manila-api service acknowledges the scheduler and share services. Procedure Log in to the undercloud. Enter the following command: Enter the following command to confirm manila-scheduler and manila-share are enabled:

Commands:
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
systemctl status ceph-mds@<CONTROLLER-HOST>
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)
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
sudo ceph fs ls name: cephfs, metadata pool: manila_metadata, data pools: [manila_data]
pcs status ceph-nfs (systemd:ceph-nfs@pacemaker): Started overcloud-controller-1 container: openstack-manila-share [192.168.24.1:8787/rhosp-rhel8/openstack-manila-share:pcmklatest] openstack-manila-share-podman-0 (ocf::heartbeat:podman): Started overcloud-controller-1
source /home/stack/overcloudrc
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 |