Storage Guide

1. Add the following parameters to the environment file to create two availability zones:

   parameter_defaults:
    CinderXXXAvailabilityZone: zone1
    CinderYYYAvailabilityZone: zone2

   Replace XXX and YYY with supported back-end values, such as:

   CinderISCSIAvailabilityZone
   CinderNfsAvailabilityZone
   CinderRbdAvailabilityZone

   Note

   Search the /usr/share/openstack-tripleo-heat-templates/deployment/cinder/ directory for the heat template associated with your back end for the correct back-end value.

   The following example deploys two back ends where rbd is zone 1 and iSCSI is zone 2:

   parameter_defaults:
    CinderRbdAvailabilityZone: zone1
    CinderISCSIAvailabilityZone: zone2

2. Deploy the overcloud and include the updated environment file.

Procedure

1. In the dashboard, select Project > Compute > Volumes.

2. Click Create Volume, and edit the following fields:

   Field	Description
   Volume name	Name of the volume.
   Description	Optional, short description of the volume.
   Type	Optional volume type (see Section 2.2.2, “Group Volume Settings with Volume Types”). If you have multiple Block Storage back ends, you can use this to select a specific back end. See Section 2.3.2, “Specify back end for volume creation”.
   Size (GB)	Volume size (in gigabytes). If you want to create an encrypted volume from an unencrypted image, you must ensure that the volume size is at least 1GB larger than the image size so that the encryption data does not truncate the volume data.
   Availability Zone	Availability zones (logical server groups), along with host aggregates, are a common method for segregating resources within OpenStack. Availability zones are defined during installation. For more information about availability zones and host aggregates, see Creating and managing host aggregates.

3. Specify a Volume Source:

   Source	Description
   No source, empty volume	The volume is empty and does not contain a file system or partition table.
   Snapshot	Use an existing snapshot as a volume source. If you select this option, a new Use snapshot as a source list opens; you can then choose a snapshot from the list. If you want to create a new volume from a snapshot of an encrypted volume, you must ensure that the new volume is at least 1GB larger than the old volume. For more information about volume snapshots, see Section 2.3.10, “Create, use, or delete volume snapshots”.
   Image	Use an existing image as a volume source. If you select this option, a new Use snapshot as a source list opens; you can then choose an image from the list.
   Volume	Use an existing volume as a volume source. If you select this option, a new Use snapshot as a source list opens; you can then choose a volume from the list.

4. Click Create Volume. After the volume is created, its name appears in the Volumes table.

1. In the dashboard, select Project > Compute > Volumes.
2. Select the volume’s Edit Volume button.
3. Edit the volume name or description as required.
4. Click Edit Volume to save your changes.

1. List the volumes to retrieve the ID of the volume you want to extend:

   $ cinder list

2. To resize the volume, run the following commands to specify the correct API microversion, then pass the volume ID and the new size (a value greater than the old size) as parameters:

   $ OS_VOLUME_API_VERSION=<API microversion>
   $ cinder extend <volume ID> <size>

   Replace <API_microversion>, <volume_ID>, and <size> with appropriate values, for example:

   $ OS_VOLUME_API_VERSION=3.42
   $ cinder extend 573e024d-5235-49ce-8332-be1576d323f8 10

1. In the dashboard, select Project > Compute > Volumes.
2. In the Volumes table, select the volume to delete.
3. Click Delete Volumes.

1. In the dashboard, select Project > Compute > Volumes.
2. Select the Create Snapshot action of the target volume.
3. Provide a Snapshot Name for the snapshot and click Create a Volume Snapshot. The Volume Snapshots tab displays all snapshots.

Procedure

1. Log in to the undercloud as the stack user.

2. Source the overcloudrc file:

   [stack@undercloud ~] $ source overcloudrc

3. Detach your volume:

   $ nova volume-detach <instance_id> <vol_id>

   Replace <instance_id> and <vol_id> with the IDs of the instance and volume that you want to revert.

4. Locate the ID or name of the snapshot that you want to revert. You can only revert the latest snapshot.

   $ cinder snapshot-list

5. Revert the snapshot:

   $ cinder --os-volume-api-version=3.40 revert-to-snapshot  <snapshot_id or snapshot_name>

   Replace <snapshot_id or snapshot_name> with the ID or the name of the snapshot.

6. Optional: You can use the cinder snapshot-list command to check that the volume you are reverting is in a reverting state.

   $  cinder snapshot-list

7. Reattach the volume:

   $  nova volume-attach <instance_id> <vol_id>

   Replace <instance_id> and <vol_id> with the IDs of the instance and volume that you reverted.

1. In the dashboard, select Project > Compute > Volumes.
2. Select the target volume’s Upload to Image action.
3. Provide an Image Name for the volume and select a Disk Format from the list.
4. Click Upload.

Procedure

1. Log in to the undercloud host as the stack user.

2. Source the undercloud credentials file:

   $ source ~/stackrc

3. Create a new environment file, or modify an existing environment file. In this example, create a new file lvm2-filtering.yaml:

   $ touch ~/lvm2-filtering.yaml

4. Include the following parameter in the environment file:

   parameter_defaults:
     LVMFilterEnabled: true

   You can further customize the implementation of the LVM2 filter. For example, to enable filtering only on Compute nodes, use the following configuration:

   parameter_defaults:
     ComputeParameters:
       LVMFilterEnabled: true

   These parameters also support regular expression. To enable filtering only on Compute nodes, and ignore all devices that start with /dev/sd, use the following configuration:

   parameter_defaults:
     ComputeParameters:
       LVMFilterEnabled: true
       LVMFilterDenylist:
         - /dev/sd.*

5. Run the openstack overcloud deploy command and include the environment file that contains the LVM2 filtering configuration, as well as any other environment files that are relevant to your overcloud deployment:

   $ openstack overcloud deploy --templates \
   <environment-files> \
   -e lvm2-filtering.yaml

Procedure

1. If the cinder-backup service is available, back up the current unencrypted volume:

   $ cinder backup-create <unencrypted_volume>

   • Replace <unencrypted_volume> with the name or ID of the unencrypted volume.

2. Create a new encrypted volume:

   $ cinder create <encrypted_volume_size> --volume-type <encrypted_volume_type>

   • Replace <encrypted_volume_size> with the size of the new volume in GB. This value must be larger than the size of the unencrypted volume by 1GB to accommodate the encryption metadata.
   • Replace <encrypted_volume_type> with the encryption type that you require.

3. Restore the backup of the unencrypted volume to the new encrypted volume:

   $ cinder backup-restore <backup> --volume <encrypted_volume>

   • Replace <backup> with the name or ID of the unencrypted volume backup.
   • Replace <encrypted_volume> with the ID of the new encrypted volume.

1. Create an Image service image of the unencrypted volume:

   $ cinder upload-to-image <unencrypted_volume> <new_image>

   • Replace <unencrypted_volume> with the name or ID of the unencrypted volume.
   • Replace <new_image> with a name for the new image.

2. Create a new volume from the image that is 1GB larger than the image:

   $ cinder volume create --size <size> --volume-type luks --image <new_image> <encrypted_volume_name>

   • Replace <size> with the size of the new volume. This value must be 1GB larger than the size of the old unencrypted volume.
   • Replace <new_image> with the name of the image that you created from the unencrypted volume.
   • Replace <encrypted_volume_name> with a name for the new encrypted volume.

Procedure

1. Configure the overcloud.

   Note

   For more information, see Configuring a basic overcloud with CLI tools in the Director Installation and Usage guide.

2. Update the heat template to enable multipath:

   parameter_defaults:
     NovaLibvirtVolumeUseMultipath:  true
     NovaComputeOptVolumes:
       - /etc/multipath.conf:/etc/multipath.conf:ro
       - /etc/multipath/:/etc/multipath/:rw
     CinderVolumeOptVolumes:
       - /etc/multipath.conf:/etc/multipath.conf:ro
       - /etc/multipath/:/etc/multipath/:rw

3. Optional: If you are using Block Storage (cinder) as an Image service (glance) back end, you must also complete the following steps:

   1. Add the following GlanceApiOptVolumes configuration to the heat template:

      parameter_defaults:
        GlanceApiOptVolumes:
          - /etc/multipath.conf:/etc/multipath.conf:ro
          - /etc/multipath/:/etc/multipath/:rw

   2. Set the ControllerExtraConfig parameter in the following way:

      parameter_defaults:
        ControllerExtraConfig:
          glance::config::api_config:
            default_backend/cinder_use_multipath:
              value: true

      Note

      Ensure that both default_backend and the GlanceBackendID heat template default value match.

4. For every configured back end, set use_multipath_for_image_xfer to true:

   parameter_defaults:
     ExtraConfig:
       cinder::config::cinder_config:
         <backend>/use_multipath_for_image_xfer:
           value: true

5. Deploy the overcloud:

   $ openstack overcloud deploy

   Note

   For information about creating the overcloud using overcloud parameters, see Creating the Overcloud with the CLI Tools in the Director Installation and Usage guide.

6. Before containers are running, install multipath on all Controller and Compute nodes:

   $ sudo dnf install -y device-mapper-multipath

   Note

   Director provides a set of hooks to support custom configuration for specific node roles after the first boot completes and before the core configuration begins. For more information about custom overcloud configuration, see Pre-Configuration: Customizing Specific Overcloud Roles in the Advanced Overcloud Customization guide.

7. Configure the multipath daemon on all Controller and Compute nodes:

   $ mpathconf --enable --with_multipathd y --user_friendly_names n --find_multipaths y

   Note

   The example code creates a basic multipath configuration that works for most environments. However, check with your storage vendor for recommendations, because some vendors have optimized configurations that are specific to their hardware. For more information about multipath, see the Configuring device mapper multipath guide.

8. Run the following command on all Controller and Compute nodes to prevent partition creation:

   $ sed -i "s/^defaults {/defaults {\n\tskip_kpartx yes\n\trecheck_wwid yes/" /etc/multipath.conf

   Note

   Setting skip_kpartx to yes prevents kpartx on the Compute node from automatically creating partitions on the device, which prevents unnecessary device mapper entries. For more information about configuration attributes, see Modifying the DM-Multipath configuration file in the Configuring device mapper multipath guide.

9. Start the multipath daemon on all Controller and Compute nodes:

   $ systemctl enable --now multipathd

Procedure

1. Verify that multipath is installed on all Controller and Compute nodes:

   $ rpm -qa | grep device-mapper-multipath
   
   device-mapper-multipath-0.4.9-127.el8.x86_64
   device-mapper-multipath-libs-0.4.9-127.el8.x86_64

   If multipath is not installed, install it on all Controller and Compute nodes:

   $ sudo dnf install -y device-mapper-multipath

2. Configure the multipath daemon on all Controller and Compute nodes:

   $ mpathconf --enable --with_multipathd y --user_friendly_names n --find_multipaths y

   Note

   The example code creates a basic multipath configuration that works for most environments. However, check with your storage vendor for recommendations, because some vendors have optimized configurations specific to their hardware. For more information about multipath, see the Configuring device mapper multipath guide.

3. Run the following command on all Controller and Compute nodes to prevent partition creation:

   $ sed -i "s/^defaults {/defaults {\n\tskip_kpartx yes\n\trecheck_wwid yes/" /etc/multipath.conf

   Note

   Setting skip_kpartx to yes prevents kpartx on the Compute node from automatically creating partitions on the device, which prevents unnecessary device mapper entries. For more information about configuration attributes, see Modifying the DM-Multipath configuration file in the Configuring device mapper multipath guide.

4. Start the multipath daemon on all Controller and Compute nodes:

   $ systemctl enable --now multipathd

5. Update the heat template to enable multipath:

   parameter_defaults:
     NovaLibvirtVolumeUseMultipath:  true
     NovaComputeOptVolumes:
       - /etc/multipath.conf:/etc/multipath.conf:ro
       - /etc/multipath/:/etc/multipath/:rw
     CinderVolumeOptVolumes:
       - /etc/multipath.conf:/etc/multipath.conf:ro
       - /etc/multipath/:/etc/multipath/:rw

6. Optional: If you are using Block Storage (cinder) as an Image service (glance) back end, you must also complete the following steps:

   1. Add the following GlanceApiOptVolumes configuration to the heat template:

      parameter_defaults:
        GlanceApiOptVolumes:
          - /etc/multipath.conf:/etc/multipath.conf:ro
          - /etc/multipath/:/etc/multipath/:rw

   2. Set the ControllerExtraConfig parameter in the following way:

      parameter_defaults:
        ControllerExtraConfig:
          glance::config::api_config:
            default_backend/cinder_use_multipath:
              value: true

      Note

      Ensure that both default_backend and the GlanceBackendID heat template default value match.

7. For every configured back end, set use_multipath_for_image_xfer to true:

   parameter_defaults:
     ExtraConfig:
       cinder::config::cinder_config:
         <backend>/use_multipath_for_image_xfer:
           value: true

8. Run the following command to update the overcloud:

   $ openstack overcloud deploy

   Note

   When you run the openstack overcloud deploy command to install and configure multipath, you must pass all previous roles and environment files that you used to deploy the overcloud, such as --templates, --roles-file, -e for all environment files, and --timeout. Failure to pass all previous roles and environment files can cause problems with your overcloud deployment. For more information about using overcloud parameters, see Creating the Overcloud with the CLI Tools in the Director Installation and Usage guide.

Procedure

1. Create a VM.
2. Attach a non-encrypted volume to the VM.

3. Get the name of the Compute node that contains the instance:

   $ nova show INSTANCE | grep OS-EXT-SRV-ATTR:host

   Replace INSTANCE with the name of the VM that you booted.

4. Retrieve the virsh name of the instance:

   $ nova show INSTANCE | grep instance_name

   Replace INSTANCE with the name of the VM that you booted.

5. Get the IP address of the Compute node:

   $ . stackrc
   $ nova list | grep compute_name

   Replace compute_name with the name from the output of the nova show INSTANCE command.

6. SSH into the Compute node that runs the VM:

   $ ssh heat-admin@COMPUTE_NODE_IP

   Replace COMPUTE_NODE_IP with the IP address of the Compute node.

7. Log in to the container that runs virsh:

   $ podman exec -it nova_libvirt /bin/bash

8. Enter the following command on a Compute node instance to verify that it is using multipath in the cinder volume host location:

   virsh domblklist VIRSH_INSTANCE_NAME | grep /dev/dm

   Replace VIRSH_INSTANCE_NAME with the output of the nova show INSTANCE | grep instance_name command.

   If the instance shows a value other than /dev/dm-, the connection is non-multipath and you must refresh the connection info with the nova shelve and nova unshelve commands:

   $ nova shelve <instance>
   $ nova unshelve <instance>

   Note

   If you have more than one type of back end, you must verify the instances and volumes on all back ends, because connection info that each back end returns might vary.

1. Edit swift_params.yaml:

   cat > swift_params.yaml << EOF
   parameter_defaults:
       ExtraConfig:
         swift::proxy::copy::object_post_as_copy: False
   EOF

2. Include the parameter file when you deploy or update the overcloud:

   openstack overcloud deploy [... previous args ...] -e swift_params.yaml

Procedure

1. Install the supporting utility packages:

   # yum install xfsprogs rsync

2. Format the /dev/sdb and /dev/sdc devices as XFS:

   # mkfs.xfs /dev/sdb
   # mkfs.xfs /dev/sdc

3. Create the mount point directory structure:

   # mkdir -p /srv/node/sdb
   # mkdir -p /srv/node/sdc

4. Edit the /etc/fstab file and add the following data to it:

   /dev/sdb /srv/node/sdb xfs defaults 0 2
   /dev/sdc /srv/node/sdc xfs defaults 0 2

5. Mount the devices:

   # mount /srv/node/sdb
   # mount /srv/node/sdc

6. Create or edit the /etc/rsyncd.conf file to contain the following data:

   uid = swift
   gid = swift
   log file = /var/log/rsyncd.log
   pid file = /var/run/rsyncd.pid
   address = MANAGEMENT_INTERFACE_IP_ADDRESS
   
   [account]
   max connections = 2
   path = /srv/node/
   read only = False
   lock file = /var/lock/account.lock
   
   [container]
   max connections = 2
   path = /srv/node/
   read only = False
   lock file = /var/lock/container.lock
   
   [object]
   max connections = 2
   path = /srv/node/
   read only = False
   lock file = /var/lock/object.lock

   Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network on the storage node.

7. Start the rsyncd service and configure it to start when the system boots:

   # systemctl enable rsyncd.service
   # systemctl start rsyncd.service

Procedure

1. Install the packages:

   # yum install openstack-swift-account openstack-swift-container \
     openstack-swift-object

2. Edit the /etc/swift/account-server.conf file and complete the following actions:

   1. In the [DEFAULT] section, configure the bind IP address, bind port, user, configuration directory, and mount point directory:

      [DEFAULT]
      ...
      bind_ip = MANAGEMENT_INTERFACE_IP_ADDRESS
      bind_port = 6202
      user = swift
      swift_dir = /etc/swift
      devices = /srv/node
      mount_check = True

      Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network on the storage node.

   2. In the [pipeline:main] section, enable the healthcheck and recon modules:

      [pipeline:main]
      pipeline = healthcheck recon account-server

   3. In the [filter:recon] section, configure the recon cache directory:

      [filter:recon]
      use = egg:swift#recon
      ...
      recon_cache_path = /var/cache/swift

3. Open the default firewall port for the account service:

   # firewall-cmd --permanent --add-port=6202/tcp

4. Edit the /etc/swift/container-server.conf file and complete the following actions:

   1. In the [DEFAULT] section, configure the bind IP address, bind port, user, configuration directory, and mount point directory:

      [DEFAULT]
      ...
      bind_ip = MANAGEMENT_INTERFACE_IP_ADDRESS
      bind_port = 6201
      user = swift
      swift_dir = /etc/swift
      devices = /srv/node
      mount_check = True

      Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network on the storage node.

   2. In the [pipeline:main] section, enable the healthcheck and recon modules:

      [pipeline:main]
      pipeline = healthcheck recon container-server

   3. In the [filter:recon] section, configure the recon cache directory:

      [filter:recon]
      use = egg:swift#recon
      ...
      recon_cache_path = /var/cache/swift

5. Open the default firewall port for the container service:

   # firewall-cmd --permanent --add-port=6201/tcp

6. Edit the /etc/swift/object-server.conf file and complete the following actions:

   1. In the [DEFAULT] section, configure the bind IP address, bind port, user, configuration directory, and mount point directory:

      [DEFAULT]
      ...
      bind_ip = MANAGEMENT_INTERFACE_IP_ADDRESS
      bind_port = 6200
      user = swift
      swift_dir = /etc/swift
      devices = /srv/node
      mount_check = True

      Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network on the storage node.

   2. In the [pipeline:main] section, enable the healthcheck and recon modules:

      [pipeline:main]
      pipeline = healthcheck recon object-server

   3. In the [filter:recon] section, configure the recon_cache_path and the recon_lock_path directories:

      [filter:recon]
      use = egg:swift#recon
      ...
      recon_cache_path = /var/cache/swift
      recon_lock_path = /var/lock

7. Open the default firewall port for the object service:

   # firewall-cmd --permanent --add-port=6200/tcp

8. Ensure that the ownership of the mount point directory structure is correct:

   # chown -R swift:swift /srv/node

9. Create the recon directory and ensure proper ownership of it:

   # mkdir -p /var/cache/swift
   # chown -R root:swift /var/cache/swift
   # chmod -R 775 /var/cache/swift

1. In the dashboard, select Project > Object Store > Containers.
2. Click Create Container.

3. Specify the Container Name, and select one of the following in the Container Access field.

   Type	Description
   Private	Limits access to a user in the current project.
   Public	Permits API access to anyone with the public URL. However, in the dashboard, project users cannot see public containers and data from other projects.

4. Click Create Container.

1. In the dashboard, select Project > Object Store > Containers.
2. Click the name of the container to which you want to add the pseudo-folder.
3. Click Create Pseudo-folder.
4. Specify the name in the Pseudo-folder Name field, and click Create.

1. In the dashboard, select Project > Object Store > Containers.
2. Browse for the container in the Containers section, and ensure all objects have been deleted (see Section 3.4.6, “Deleting an object”).
3. Select Delete Container in the container’s arrow menu.
4. Click Delete Container to confirm the container’s removal.

1. In the dashboard, select Project > Object Store > Containers.
2. Click the name of the container in which the uploaded object will be placed; if a pseudo-folder already exists in the container, you can click its name.
3. Browse for your file, and click Upload Object.

4. Specify a name in the Object Name field:

   • Pseudo-folders can be specified in the name using a / character (for example, Images/myImage.jpg). If the specified folder does not already exist, it is created when the object is uploaded.
   • A name that is not unique to the location (that is, the object already exists) overwrites the object’s contents.
5. Click Upload Object.

1. In the dashboard, select Project > Object Store > Containers.
2. Click the name of the object’s container or folder (to display the object).
3. Click Upload Object.
4. Browse for the file to be copied, and select Copy in its arrow menu.

5. Specify the following:

   Field	Description
   Destination container	Target container for the new object.
   Path	Pseudo-folder in the destination container; if the folder does not already exist, it is created.
   Destination object name	New object’s name. If you use a name that is not unique to the location (that is, the object already exists), it overwrites the object’s previous contents.

6. Click Copy Object.

1. In the dashboard, select Project > Object Store > Containers.
2. Browse for the object, and select Delete Object in its arrow menu.
3. Click Delete Object to confirm the object’s removal.

Procedure

1. After you deploy the overcloud, run the following command as the cloud administrator to create a share type:

   # manila type-create default <spec_driver_handles_share_servers>

   The <spec_driver_handles_share_servers> parameter is a Boolean value:

   • For CephFS through NFS or native CephFS, the value is false.
   • For other back ends, the value can be true or false; set <spec_driver_handles_share_servers> to match the value of the Manila<backend>DriverHandlesShareServers parameter. For example, if you use a NetApp back end, the parameter is called ManilaNetappDriverHandlesShareServers.

2. Add specifications to the default share type or create additional share types to use with multiple configured back ends. For example, configure the default share type to select a CephFS back end and an additional share type that uses a NetApp driver_handles_share_servers=True back end:

   (overcloud) [stack@undercloud-0 ~]$ manila type-create default false --extra-specs share_backend_name='cephfs'
   (overcloud) [stack@undercloud-0 ~]$ manila type-create netapp true --extra-specs share_backend_name='tripleo_netapp'

Procedure

1. Discover the available share types:

   $ manila type-list

   The command output lists the name and ID of the share type.

Procedure

1. Use the example share types to create a 10 GB NFS share named share-01 on the CephFS NFS back end. This example uses CephFS with NFS:

   (user) [stack@undercloud-0 ~]$ manila create --name share-01 nfs 10

2. Optional: Create a 20 GB NFS share named share-02 on the NetApp back end:

   (user) [stack@undercloud-0 ~]$ manila create --name share-02 --share-type netapp --share-network mynet nfs 20

Procedure

1. List the shares:

   (user) [stack@undercloud-0 ~]$ manila list
   
   +--------------------------------------+----------+-----+-----------+           | ID                                   | Name     | ... | Status    ...
   +--------------------------------------+----------+-----+-----------+
   | 8c3bedd8-bc82-4100-a65d-53ec51b5fe81 | share-01 | ... | available ...
   +--------------------------------------+----------+-----+-----------+

2. View the export locations of the share:

   (user) [stack@undercloud-0 ~]$ manila share-export-location-list share-01
   
    +------------------------------------------------------------------
    | Path
    |  172.17.5.13:/volumes/_nogroup/e840b4ae-6a04-49ee-9d6e-67d4999fbc01
    +------------------------------------------------------------------

3. View the parameters for the share:

   manila share-export-location-show <id>

   Note

   This information is used to mount the share in Section 4.4.2, “Mounting the share”.

Procedure

1. Create a security group for the StorageNFS port that allows packets to egress the port, but which does not allow ingress packets from unestablished connections:

   (user) [stack@undercloud-0 ~]$ openstack security group create no-ingress -f yaml
   created_at: '2018-09-19T08:19:58Z'
   description: no-ingress
   id: 66f67c24-cd8b-45e2-b60f-9eaedc79e3c5
   name: no-ingress
   project_id: 1e021e8b322a40968484e1af538b8b63
   revision_number: 2
   rules: 'created_at=''2018-09-19T08:19:58Z'', direction=''egress'', ethertype=''IPv4'',
    id=''6c7f643f-3715-4df5-9fef-0850fb6eaaf2'', updated_at=''2018-09-19T08:19:58Z''
   
    created_at=''2018-09-19T08:19:58Z'', direction=''egress'', ethertype=''IPv6'',                                                          id=''a8ca1ac2-fbe5-40e9-ab67-3e55b7a8632a'', updated_at=''2018-09-19T08:19:58Z'''
   updated_at: '2018-09-19T08:19:58Z'

2. Create a port on the StorageNFS network with security enforced by the no-ingress security group.

   (user) [stack@undercloud-0 ~]$ openstack port create nfs-port0 --network StorageNFS --security-group no-ingress -f yaml
   
   admin_state_up: UP
   allowed_address_pairs: ''
   binding_host_id: null
   binding_profile: null
   binding_vif_details: null
   binding_vif_type: null
   binding_vnic_type: normal
   created_at: '2018-09-19T08:03:02Z'
   data_plane_status: null
   description: ''
   device_id: ''
   device_owner: ''
   dns_assignment: null
   dns_name: null
   extra_dhcp_opts: ''
   fixed_ips: ip_address='172.17.5.160', subnet_id='7bc188ae-aab3-425b-a894-863e4b664192'
   id: 7a91cbbc-8821-4d20-a24c-99c07178e5f7
   ip_address: null
   mac_address: fa:16:3e:be:41:6f
   name: nfs-port0
   network_id: cb2cbc5f-ea92-4c2d-beb8-d9b10e10efae
   option_name: null
   option_value: null
   port_security_enabled: true
   project_id: 1e021e8b322a40968484e1af538b8b63
   qos_policy_id: null
   revision_number: 6
   security_group_ids: 66f67c24-cd8b-45e2-b60f-9eaedc79e3c5
   status: DOWN
   subnet_id: null
   tags: ''
   trunk_details: null
   updated_at: '2018-09-19T08:03:03Z'

   Note

   StorageNFSSubnet assigned IP address 172.17.5.160 to nfs-port0.

3. Add nfs-port0 to a Compute instance.

   (user) [stack@undercloud-0 ~]$ openstack server add port instance0 nfs-port0
   (user) [stack@undercloud-0 ~]$ openstack server list -f yaml
   - Flavor: m1.micro
     ID: 0b878c11-e791-434b-ab63-274ecfc957e8
     Image: manila-test
     Name: demo-instance0
     Networks: demo-network=172.20.0.4, 10.0.0.53; StorageNFS=172.17.5.160
     Status: ACTIVE

   In addition to its private and floating addresses, the Compute instance is assigned a port with the IP address 172.17.5.160 on the StorageNFS network that you can use to mount NFS shares when access is granted to that address for the share in question.

   Note

   You might need to adjust the networking configuration on the Compute instance and restart the services for the Compute instance to activate an interface with this address.

Procedure

1. Log in to the instance.

2. Configure the IPv6 interface address:

   $ ip address add fd00:fd00:fd00:7000::c/64 dev eth1

3. Activate the interface:

   $ ip link set dev eth1 up

4. Ping the IPv6 address in the export location of the share to test interface connectivity:

   $ ping -6  fd00:fd00:fd00:7000::21

5. Alternatively, verify that you can reach the NFS server through Telnet:

   $ dnf install -y telnet
   $ telnet fd00:fd00:fd00:7000::21 2049

Procedure

1. Retrieve the IP address of the client compute instance where you plan to mount the share. Make sure that you pick the IP address that corresponds to the network that can reach the shares. In this example, it is the IP address of the StorageNFS network:

   (user) [stack@undercloud-0 ~]$ openstack server list -f yaml
   - Flavor: m1.micro
     ID: 0b878c11-e791-434b-ab63-274ecfc957e8
     Image: manila-test
     Name: demo-instance0
     Networks: demo-network=172.20.0.4, 10.0.0.53;
     StorageNFS=172.17.5.160
     Status: ACTIVE
   
   (user) [stack@undercloud-0 ~]$ manila access-allow share-01 ip 172.17.5.160

   Note

   Access to the share has its own ID (accessid).

   +-----------------+---------------------------------------+
   | Property        | Value                                 |
   +-----------------+---------------------------------------+
   | access_key      | None
   | share_id        | db3bedd8-bc82-4100-a65d-53ec51b5cba3
   | created_at      | 2018-09-17T21:57:42.000000
   | updated_at      | None
   | access_type     | ip
   | access_to       | 172.17.5.160
   | access_level    | rw
   | state           | queued_to_apply
   | id              | 875c6251-c17e-4c45-8516-fe0928004fff
   +-----------------+---------------------------------------+

2. Verify that the access configuration was successful:

   (user) [stack@undercloud-0 ~]$ manila access-list share-01
   
   +--------------+-------------+--------------+--------------+--------+ ...
   | id           | access_type | access_to    | access_level | state  | ...
   +--------------+-------------+--------------+--------------+--------+
   | 875c6251-... | ip          | 172.17.5.160 | rw       	   | active | ...
   +--------------+------------+--------------+--------------+---------+ ...

Procedure

1. Revoke access to a share:

   # manila access-deny <share> <accessid>

   Note

   Replace <share> with either the share name or the share ID.

   For example:

   (user) [stack@undercloud-0 ~]$ manila access-list share-01
   +--------------+-------------+--------------+--------------+--------+
   | id           | access_type | access_to    | access_level | state  | ...
   +--------------+-------------+--------------+--------------+--------+ ...
   | 875c6251-... | ip          | 172.17.5.160 | rw       	   | active | ...
   +--------------+-------------+--------------+--------------+--------+
   
   (user) [stack@undercloud-0 ~]$ manila access-deny share-01 875c6251-c17e-4c45-8516-fe0928004fff
   
   (user) [stack@undercloud-0 ~]$ manila access-list share-01
   
   +--------------+------------+--------------+--------------+--------+ ...
   | id           | access_type| access_to    | access_level | state  | ...
   +--------------+------------+--------------+--------------+--------+ ...
   +--------------+------------+--------------+--------------+--------+ ...

Procedure

1. Retrieve the export location of a share:

   (user) [stack@undercloud-0 ~]$ manila share-export-location-list share-01

   When multiple export locations exist, choose one for which the value of the preferred metadata field equals True. If no preferred locations exist, you can use any export location.

Procedure

1. Log in to the instance and run the following command:

   (user) [stack@undercloud-0 ~]$ openstack server ssh demo-instance0 --login root
   # hostname
   demo-instance0

2. Mount the share on an IPv4 network by using the export location:

   # mount -t nfs -v  172.17.5.13:/volumes/_nogroup/e840b4ae-6a04-49ee-9d6e-67d4999fbc01 /mnt

Procedure

1. To see the usage statements, run the following commands:

   # manila help quota-show
   # manila help quota-update
   # manila help quota-delete

Procedure

1. To create the share, you can use a share type that specifies some capabilities that you want the share to have. Cloud administrators can create share types. View the available share types:

   clouduser1@client:~$ manila type-list
   +--------------------------------------+-------------+------------+------------+--------------------------------------+--------------------------------------------+-------------+
   | ID                                   | Name        | visibility | is_default | required_extra_specs                 | optional_extra_specs                       | Description |
   +--------------------------------------+-------------+------------+------------+--------------------------------------+--------------------------------------------+-------------+
   | 1cf5d45a-61b3-44d1-8ec7-89a21f51a4d4 | dhss_false  | public     | YES        | driver_handles_share_servers : False | create_share_from_snapshot_support : True  | None        |
   |                                      |             |            |            |                                      | mount_snapshot_support : False             |             |
   |                                      |             |            |            |                                      | revert_to_snapshot_support : False         |             |
   |                                      |             |            |            |                                      | snapshot_support : True                    |             |
   | 277c1089-127f-426e-9b12-711845991ea1 | dhss_true   | public     | -          | driver_handles_share_servers : True  | create_share_from_snapshot_support : True  | None        |
   |                                      |             |            |            |                                      | mount_snapshot_support : False             |             |
   |                                      |             |            |            |                                      | revert_to_snapshot_support : False         |             |
   |                                      |             |            |            |                                      | snapshot_support : True                    |             |
   +--------------------------------------+-------------+------------+------------+--------------------------------------+--------------------------------------------+-------------+

   In this example, two share types are available.

2. To use a share type that specifies the driver_handles_share_servers=True capability, you must create a share network on which to export the share. Create a share network from a private project network.

   clouduser1@client:~$ openstack subnet list
   +--------------------------------------+---------------------+--------------------------------------+---------------------+
   | ID                                   | Name                | Network                              | Subnet              |
   +--------------------------------------+---------------------+--------------------------------------+---------------------+
   | 78c6ac57-bba7-4922-ab81-16cde31c2d06 | private-subnet      | 74d5cfb3-5dd0-43f7-b1b2-5b544cb16212 | 10.0.0.0/26         |
   | a344682c-718d-4825-a87a-3622b4d3a771 | ipv6-private-subnet | 74d5cfb3-5dd0-43f7-b1b2-5b544cb16212 | fd36:18fc:a8e9::/64 |
   +--------------------------------------+---------------------+--------------------------------------+---------------------+
   
   clouduser1@client:~$ manila share-network-create --name mynet --neutron-net-id 74d5cfb3-5dd0-43f7-b1b2-5b544cb16212 --neutron-subnet-id 78c6ac57-bba7-4922-ab81-16cde31c2d06
   +-------------------+--------------------------------------+
   | Property          | Value                                |
   +-------------------+--------------------------------------+
   | network_type      | None                                 |
   | name              | mynet                                |
   | segmentation_id   | None                                 |
   | created_at        | 2018-10-09T21:32:22.485399           |
   | neutron_subnet_id | 78c6ac57-bba7-4922-ab81-16cde31c2d06 |
   | updated_at        | None                                 |
   | mtu               | None                                 |
   | gateway           | None                                 |
   | neutron_net_id    | 74d5cfb3-5dd0-43f7-b1b2-5b544cb16212 |
   | ip_version        | None                                 |
   | cidr              | None                                 |
   | project_id        | cadd7139bc3148b8973df097c0911016     |
   | id                | 0b0fc320-d4b5-44a1-a1ae-800c56de550c |
   | description       | None                                 |
   +-------------------+--------------------------------------+
   
   clouduser1@client:~$ manila share-network-list
   +--------------------------------------+-------+
   | id                                   | name  |
   +--------------------------------------+-------+
   | 6c7ef9ef-3591-48b6-b18a-71a03059edd5 | mynet |
   +--------------------------------------+-------+

3. Create the share:

   clouduser1@client:~$ manila create nfs 1 --name software_share --share-network mynet --share-type dhss_true
   +---------------------------------------+--------------------------------------+
   | Property                              | Value                                |
   +---------------------------------------+--------------------------------------+
   | status                                | creating                             |
   | share_type_name                       | dhss_true                            |
   | description                           | None                                 |
   | availability_zone                     | None                                 |
   | share_network_id                      | 6c7ef9ef-3591-48b6-b18a-71a03059edd5 |
   | share_server_id                       | None                                 |
   | share_group_id                        | None                                 |
   | host                                  |                                      |
   | revert_to_snapshot_support            | False                                |
   | access_rules_status                   | active                               |
   | snapshot_id                           | None                                 |
   | create_share_from_snapshot_support    | False                                |
   | is_public                             | False                                |
   | task_state                            | None                                 |
   | snapshot_support                      | False                                |
   | id                                    | 243f3a51-0624-4bdd-950e-7ed190b53b67 |
   | size                                  | 1                                    |
   | source_share_group_snapshot_member_id | None                                 |
   | user_id                               | 61aef4895b0b41619e67ae83fba6defe     |
   | name                                  | software_share                       |
   | share_type                            | 277c1089-127f-426e-9b12-711845991ea1 |
   | has_replicas                          | False                                |
   | replication_type                      | None                                 |
   | created_at                            | 2018-10-09T21:12:21.000000           |
   | share_proto                           | NFS                                  |
   | mount_snapshot_support                | False                                |
   | project_id                            | cadd7139bc3148b8973df097c0911016     |
   | metadata                              | {}                                   |
   +---------------------------------------+--------------------------------------+

4. View the status of the share:

   clouduser1@client:~$ manila list
   +--------------------------------------+----------------+------+-------------+--------+-----------+-----------------+------+-------------------+
   | ID                                   | Name           | Size | Share Proto | Status | Is Public | Share Type Name | Host | Availability Zone |
   +--------------------------------------+----------------+------+-------------+--------+-----------+-----------------+------+-------------------+
   | 243f3a51-0624-4bdd-950e-7ed190b53b67 | software_share | 1    | NFS         | error  | False     | dhss_true       |      | None              |
   +--------------------------------------+----------------+------+-------------+--------+-----------+-----------------+------+-------------------+

   In this example, an error occurred during the share creation.

5. To view the user support message, run the message-list command. Use the --resource-id to filter to the specific share you want to find out about.

   clouduser1@client:~$ manila message-list
   +--------------------------------------+---------------+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------+-----------+----------------------------+
   | ID                                   | Resource Type | Resource ID                          | Action ID | User Message                                                                                             | Detail ID | Created At                 |
   +--------------------------------------+---------------+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------+-----------+----------------------------+
   | 7d411c3c-46d9-433f-9e21-c04ca30b209c | SHARE         | 243f3a51-0624-4bdd-950e-7ed190b53b67 | 001       | allocate host: No storage could be allocated for this share request, Capabilities filter didn't succeed. | 008       | 2018-10-09T21:12:21.000000 |
   +--------------------------------------+---------------+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------+-----------+----------------------------+

   In the User Message column, notice that the Shared File Systems service failed to create the share because of a capabilities mismatch.

6. To view more message information, run the message-show command, followed by the ID of the message from the message-list command:

   clouduser1@client:~$ manila message-show 7d411c3c-46d9-433f-9e21-c04ca30b209c
   +---------------+----------------------------------------------------------------------------------------------------------+
   | Property      | Value                                                                                                    |
   +---------------+----------------------------------------------------------------------------------------------------------+
   | request_id    | req-0a875292-6c52-458b-87d4-1f945556feac                                                                 |
   | detail_id     | 008                                                                                                      |
   | expires_at    | 2018-11-08T21:12:21.000000                                                                               |
   | resource_id   | 243f3a51-0624-4bdd-950e-7ed190b53b67                                                                     |
   | user_message  | allocate host: No storage could be allocated for this share request, Capabilities filter didn't succeed. |
   | created_at    | 2018-10-09T21:12:21.000000                                                                               |
   | message_level | ERROR                                                                                                    |
   | id            | 7d411c3c-46d9-433f-9e21-c04ca30b209c                                                                     |
   | resource_type | SHARE                                                                                                    |
   | action_id     | 001                                                                                                      |
   +---------------+----------------------------------------------------------------------------------------------------------+

7. As the cloud user, you can check capabilities through the share type so you can review the share types available. The difference between the two share types is the value of driver_handles_share_servers:

   clouduser1@client:~$ manila type-list
   +--------------------------------------+-------------+------------+------------+--------------------------------------+--------------------------------------------+-------------+
   | ID                                   | Name        | visibility | is_default | required_extra_specs                 | optional_extra_specs                       | Description |
   +--------------------------------------+-------------+------------+------------+--------------------------------------+--------------------------------------------+-------------+
   | 1cf5d45a-61b3-44d1-8ec7-89a21f51a4d4 | dhss_false  | public     | YES        | driver_handles_share_servers : False | create_share_from_snapshot_support : True  | None        |
   |                                      |             |            |            |                                      | mount_snapshot_support : False             |             |
   |                                      |             |            |            |                                      | revert_to_snapshot_support : False         |             |
   |                                      |             |            |            |                                      | snapshot_support : True                    |             |
   | 277c1089-127f-426e-9b12-711845991ea1 | dhss_true   | public     | -          | driver_handles_share_servers : True  | create_share_from_snapshot_support : True  | None        |
   |                                      |             |            |            |                                      | mount_snapshot_support : False             |             |
   |                                      |             |            |            |                                      | revert_to_snapshot_support : False         |             |
   |                                      |             |            |            |                                      | snapshot_support : True                    |             |
   +--------------------------------------+-------------+------------+------------+--------------------------------------+--------------------------------------------+-------------+

8. Create a share with the other available share type:

   clouduser1@client:~$ manila create nfs 1 --name software_share --share-network mynet --share-type dhss_false
   +---------------------------------------+--------------------------------------+
   | Property                              | Value                                |
   +---------------------------------------+--------------------------------------+
   | status                                | creating                             |
   | share_type_name                       | dhss_false                           |
   | description                           | None                                 |
   | availability_zone                     | None                                 |
   | share_network_id                      | 6c7ef9ef-3591-48b6-b18a-71a03059edd5 |
   | share_group_id                        | None                                 |
   | revert_to_snapshot_support            | False                                |
   | access_rules_status                   | active                               |
   | snapshot_id                           | None                                 |
   | create_share_from_snapshot_support    | True                                 |
   | is_public                             | False                                |
   | task_state                            | None                                 |
   | snapshot_support                      | True                                 |
   | id                                    | 2d03d480-7cba-4122-ac9d-edc59c8df698 |
   | size                                  | 1                                    |
   | source_share_group_snapshot_member_id | None                                 |
   | user_id                               | 5c7bdb6eb0504d54a619acf8375c08ce     |
   | name                                  | software_share                       |
   | share_type                            | 1cf5d45a-61b3-44d1-8ec7-89a21f51a4d4 |
   | has_replicas                          | False                                |
   | replication_type                      | None                                 |
   | created_at                            | 2018-10-09T21:24:40.000000           |
   | share_proto                           | NFS                                  |
   | mount_snapshot_support                | False                                |
   | project_id                            | cadd7139bc3148b8973df097c0911016     |
   | metadata                              | {}                                   |
   +---------------------------------------+--------------------------------------+

   In this example, the second share creation attempt fails.

9. View the user support message:

   clouduser1@client:~$ manila list
   +--------------------------------------+----------------+------+-------------+--------+-----------+-----------------+------+-------------------+
   | ID                                   | Name           | Size | Share Proto | Status | Is Public | Share Type Name | Host | Availability Zone |
   +--------------------------------------+----------------+------+-------------+--------+-----------+-----------------+------+-------------------+
   | 2d03d480-7cba-4122-ac9d-edc59c8df698 | software_share | 1    | NFS         | error  | False     | dhss_false      |      | nova              |
   | 243f3a51-0624-4bdd-950e-7ed190b53b67 | software_share | 1    | NFS         | error  | False     | dhss_true       |      | None              |
   +--------------------------------------+----------------+------+-------------+--------+-----------+-----------------+------+-------------------+
   
   clouduser1@client:~$ manila message-list
   +--------------------------------------+---------------+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------+-----------+----------------------------+
   | ID                                   | Resource Type | Resource ID                          | Action ID | User Message                                                                                             | Detail ID | Created At                 |
   +--------------------------------------+---------------+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------+-----------+----------------------------+
   | ed7e02a2-0cdb-4ff9-b64f-e4d2ec1ef069 | SHARE         | 2d03d480-7cba-4122-ac9d-edc59c8df698 | 002       | create: Driver does not expect share-network to be provided with current configuration.                  | 003       | 2018-10-09T21:24:40.000000 |
   | 7d411c3c-46d9-433f-9e21-c04ca30b209c | SHARE         | 243f3a51-0624-4bdd-950e-7ed190b53b67 | 001       | allocate host: No storage could be allocated for this share request, Capabilities filter didn't succeed. | 008       | 2018-10-09T21:12:21.000000 |
   +--------------------------------------+---------------+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------+-----------+----------------------------+

   The service does not expect a share network for the share type that you used.

10. Without consulting the administrator, you can discover that the administrator has not made available a storage back end that supports exporting shares directly on to your private neutron network. Create the share without the share-network parameter:

    clouduser1@client:~$ manila create nfs 1 --name software_share --share-type dhss_false
    +---------------------------------------+--------------------------------------+
    | Property                              | Value                                |
    +---------------------------------------+--------------------------------------+
    | status                                | creating                             |
    | share_type_name                       | dhss_false                           |
    | description                           | None                                 |
    | availability_zone                     | None                                 |
    | share_network_id                      | None                                 |
    | share_group_id                        | None                                 |
    | revert_to_snapshot_support            | False                                |
    | access_rules_status                   | active                               |
    | snapshot_id                           | None                                 |
    | create_share_from_snapshot_support    | True                                 |
    | is_public                             | False                                |
    | task_state                            | None                                 |
    | snapshot_support                      | True                                 |
    | id                                    | 4d3d7fcf-5fb7-4209-90eb-9e064659f46d |
    | size                                  | 1                                    |
    | source_share_group_snapshot_member_id | None                                 |
    | user_id                               | 5c7bdb6eb0504d54a619acf8375c08ce     |
    | name                                  | software_share                       |
    | share_type                            | 1cf5d45a-61b3-44d1-8ec7-89a21f51a4d4 |
    | has_replicas                          | False                                |
    | replication_type                      | None                                 |
    | created_at                            | 2018-10-09T21:25:40.000000           |
    | share_proto                           | NFS                                  |
    | mount_snapshot_support                | False                                |
    | project_id                            | cadd7139bc3148b8973df097c0911016     |
    | metadata                              | {}                                   |
    +---------------------------------------+--------------------------------------+

11. Ensure that the share was created successfully:

    clouduser1@client:~$ manila list
    +--------------------------------------+----------------+------+-------------+-----------+-----------+-----------------+------+-------------------+
    | ID                                   | Name           | Size | Share Proto | Status    | Is Public | Share Type Name | Host | Availability Zone |
    +--------------------------------------+----------------+------+-------------+-----------+-----------+-----------------+------+-------------------+
    | 4d3d7fcf-5fb7-4209-90eb-9e064659f46d | software_share | 1    | NFS         | available | False     | dhss_false      |      | nova              |
    | 2d03d480-7cba-4122-ac9d-edc59c8df698 | software_share | 1    | NFS         | error     | False     | dhss_false      |      | nova              |
    | 243f3a51-0624-4bdd-950e-7ed190b53b67 | software_share | 1    | NFS         | error     | False     | dhss_true       |      | None              |
    +--------------------------------------+----------------+------+-------------+-----------+-----------+-----------------+------+-------------------+

12. Delete the shares and support messages:

    clouduser1@client:~$ manila message-list
    +--------------------------------------+---------------+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------+-----------+----------------------------+
    | ID                                   | Resource Type | Resource ID                          | Action ID | User Message                                                                                             | Detail ID | Created At                 |
    +--------------------------------------+---------------+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------+-----------+----------------------------+
    | ed7e02a2-0cdb-4ff9-b64f-e4d2ec1ef069 | SHARE         | 2d03d480-7cba-4122-ac9d-edc59c8df698 | 002       | create: Driver does not expect share-network to be provided with current configuration.                  | 003       | 2018-10-09T21:24:40.000000 |
    | 7d411c3c-46d9-433f-9e21-c04ca30b209c | SHARE         | 243f3a51-0624-4bdd-950e-7ed190b53b67 | 001       | allocate host: No storage could be allocated for this share request, Capabilities filter didn't succeed. | 008       | 2018-10-09T21:12:21.000000 |
    +--------------------------------------+---------------+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------+-----------+----------------------------+
    
    clouduser1@client:~$ manila delete 2d03d480-7cba-4122-ac9d-edc59c8df698 243f3a51-0624-4bdd-950e-7ed190b53b67
    clouduser1@client:~$ manila message-delete ed7e02a2-0cdb-4ff9-b64f-e4d2ec1ef069 7d411c3c-46d9-433f-9e21-c04ca30b209c
    
    clouduser1@client:~$ manila message-list
    +----+---------------+-------------+-----------+--------------+-----------+------------+
    | ID | Resource Type | Resource ID | Action ID | User Message | Detail ID | Created At |
    +----+---------------+-------------+-----------+--------------+-----------+------------+
    +----+---------------+-------------+-----------+--------------+-----------+------------+

Procedure

1. Verify the access control list of the share to ensure that the rule that corresponds to your client is correct and has been successfully applied.

   $ manila access-list share-01

   In a successful rule, the state attribute equals active.

2. If the share type parameter is configured to driver_handles_share_servers=False, copy the hostname or IP address from the export location and ping it to confirm connectivity to the NAS server:

   # ping -c 1 172.17.5.13
   PING 172.17.5.13 (172.17.5.13) 56(84) bytes of data.
   64 bytes from 172.17.5.13: icmp_seq=1 ttl=64 time=0.048 ms--- 172.17.5.13 ping statistics ---
   1 packets transmitted, 1 received, 0% packet loss, time 0ms
   rtt min/avg/max/mdev = 7.851/7.851/7.851/0.000 ms
   If using the NFS protocol, you may verify that the NFS server is ready to respond to NFS rpcs on the proper port:
   # rpcinfo -T tcp -a 172.17.5.13.8.1 100003 4
   program 100003 version 4 ready and waiting

   Note

   The IP address is written in universal address format (uaddr), which adds two extra octets (8.1) to represent the NFS service port, 2049.