Chapter 6. Performing operations with the Shared File Systems service (manila)

Procedure

1. List the shares:

   $ openstack share list

2. View the export locations of the share:

   $ openstack share export location list <share_id>

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

3. View the parameters for the share:

   $ openstack share export location show <share_id> <export_location_id>

   • Replace <export_location_id> with the export location of the share to view the parameters.

     Note

     You use the export location to mount the share, as described in Section 6.9.3, “Mounting NFS, native CephFS, or CIFS shares”.

Procedure

1. Create a snapshot of a share:

   $ openstack share snapshot create [--name <snapshot_name>] <share>

   • Replace <share> with the name or ID of the share for which you want to create a snapshot.
   • Optional: Replace <snapshot_name> with the name of the snapshot.

2. Confirm that you created the snapshot:

   $ openstack share snapshot list --share <share>

   Replace <share> with the ID of the share from which you created the snapshot.

Procedure

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

   $ 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''

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

   Note

   In the following example, the StorageNFS subnet on the StorageNFS network assigns IP address 198.51.100.160 to nfs-port0.

   $ 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='198.51.100.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'

3. Add nfs-port0 to a Compute instance.

   $ openstack server add port instance0 nfs-port0
   $ openstack server list -f yaml
   - Flavor: m1.micro
     ID: 0b878c11-e791-434b-ab63-274ecfc957e8
     Image: manila-test
     Name: demo-instance0
     Networks: demo-network=198.51.100.4, 10.0.0.53; StorageNFS=198.51.100.160
     Status: ACTIVE

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

   Note

   You might need to adjust the networking configuration on the Compute instance, and then 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:

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

3. Activate the interface:

   $ sudo 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:

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

Procedure

1. Access the remote shell for the openstackclient pod from your workstation:

   $ oc rsh -n openstack openstackclient

2. Create a share transfer:

   $ openstack share transfer create <share_id> --name <share_transfer_name>

   • Replace <share_id> with the ID of the share you want to transfer.

   • Replace <share_transfer_name> with a name for your share transfer.

     Example output:

     +------------------------+--------------------------------------+
     | Field                  | Value                                |
     +------------------------+--------------------------------------+
     | id                     | 1c56314e-7e97-455a-bbde-83828db038d4 |
     | created_at             | 2025-09-22T13:45:41.376091           |
     | name                   | share-transfer                       |
     | resource_type          | share                                |
     | resource_id            | 4f508574-e1c8-4bf9-adc4-8a1d34ac13a6 |
     | source_project_id      | 7dd704e2ab5c42c0afe83bfad076fcb4     |
     | destination_project_id | None                                 |
     | accepted               | False                                |
     | expires_at             | 2025-09-22T13:50:41.375594           |
     | auth_key               | af429e22e0abc31d                     |
     +------------------------+--------------------------------------+

   • Store the transfer id and auth_key to share with the user in a different project so they can accept the share transfer. You must save the transfer ID when you create the transfer because you cannot obtain the auth_key from the service again later. If you do not have the auth_key to share with another user later, you must delete the transfer and start the process again.

3. View a list of share transfers in your project to verify that your share transfer is created:

   $ openstack share transfer list

   Example output:

   +--------------------------------------+----------------+---------------+--------------------------------------+
   | ID                                   | Name           | Resource Type | Resource Id                          |
   +--------------------------------------+----------------+---------------+--------------------------------------+
   | 1c56314e-7e97-455a-bbde-83828db038d4 | share-transfer | share         | 4f508574-e1c8-4bf9-adc4-8a1d34ac13a6 |
   +--------------------------------------+----------------+---------------+--------------------------------------+

4. View details of the share transfer:

   $ openstack share transfer show <share_transfer_id>

   • Replace <share_transfer_id> with the share transfer ID, for example 1c56314e-7e97-455a-bbde-83828db038d4.

     Example output:

     +------------------------+--------------------------------------+
     | Field                  | Value                                |
     +------------------------+--------------------------------------+
     | id                     | 181773b2-e359-45f4-9d7d-31ee8b722fd3 |
     | created_at             | 2025-09-22T13:45:41.376091           |
     | name                   | share-transfer                       |
     | resource_type          | share                                |
     | resource_id            | 4f508574-e1c8-4bf9-adc4-8a1d34ac13a6 |
     | source_project_id      | 7dd704e2ab5c42c0afe83bfad076fcb4     |
     | destination_project_id | None                                 |
     | accepted               | False                                |
     | expires_at             | 2025-09-22T13:50:41.375594           |
     +------------------------+--------------------------------------+

   • To delete a share transfer, you can run the following command:

     $ openstack share transfer delete <share_transfer_id>

5. Exit the openstackclient pod:

   $ exit

6. Share the transfer id and auth_key with the user who accepts the share transfer in a different project.

   • The user accepts the share transfer by using the following command. In this example, 1c56314e-7e97-455a-bbde-83828db038d4 is the share transfer ID and af429e22e0abc31d is the authorization key:

     Example:

     $ openstack share transfer accept 1c56314e-7e97-455a-bbde-83828db038d4  af429e22e0abc31d