# Using SFS Turbo Volumes

#### Prerequisites

You have created a CCE cluster and installed the CSI plug-in (everest) in the cluster.

#### Notes and Constraints

- SFS Turbo volumes are available only in certain regions.
- Currently, SFS Turbo file systems cannot be directly created on CCE.
- Only an SFS Turbo file system in the same VPC as the cluster and in the same subnet as the node can be imported.
- Inbound ports (111, 445, 2049, 2051, and 20048) must be enabled for the security group to which the SFS Turbo file system belongs.

#### Importing an SFS Turbo Volume

CCE allows you to import existing SFS Turbo volumes.

1. Log in to the CCE console. In the navigation pane, choose Resource Management > Storage. On the SFS Turbo tab page, click Import.
2. Select one or more SFS Turbo volumes that you want to import.
3. Select the cluster and namespace to which you want to import the volumes.
4. Click Next. The volumes are displayed in the list. When PVC Status becomes Bound, the volumes are imported successfully.

#### Adding an SFS Turbo Volume

1. Create a workload or job by referring to Creating a Deployment, Creating a StatefulSet, Creating a DaemonSet, or Creating a Job. After you have added a container, choose Data Storage > Cloud Volume, and then click Add Cloud Volume.
2. Set the storage volume type to SFS Turbo.

   Table 1 Parameters for configuring an SFS Turbo volume
   Parameter | Parameter Description
   --- | ---
   Type | SFS Turbo: applicable to DevOps, containerized microservices, and enterprise office applications.
   Allocation Mode
   Manual | Select an existing SFS Turbo volume. You need to import SFS Turbo volumes in advance. For details, see Importing an SFS Turbo Volume.

   Add Container Path

   Configure the following parameters:
   1. subPath: Enter the subpath of the file storage, for example, /tmp.

      This parameter specifies a subpath inside the referenced volume instead of its root. If this parameter is not specified, the root path is used. Currently, only file storage is supported. The value must be a relative path and cannot start with a slash (/) or ../.

   2. Container Path: Enter the mount path in the container, for example, /tmp.
      The mount path must not be a system directory, such as / and /var/run. Otherwise, an exception occurs. You are advised to mount the volume to an empty directory. If the directory is not empty, ensure that there are no files affecting container startup in the directory. Otherwise, such files will be replaced, resulting in failures to start the container and create the workload.
      NOTICE:

      If the volume is mounted to a high-risk directory, you are advised to use an account with minimum permissions to start the container; otherwise, high-risk files on the host machine may be damaged.

   3. Set permissions.
      - Read-only: You can only read the data in the mounted volumes.
      - Read/Write: You can modify the data in the mounted volumes. Newly written data is not migrated if the container is migrated, which causes a data loss.

   Click Add Container Path to add multiple settings. Then, click OK.

3. Click OK.

#### Unbinding an SFS Turbo Volume

When an SFS Turbo volume is successfully imported to a cluster, the volume is bound to the cluster. The volume can also be imported to other clusters. When the volume is unbound from the cluster, other clusters can still import and use the volume.

If the SFS Turbo volume has been mounted to a workload, the volume cannot be unbound from the cluster.

1. Log in to the CCE console. In the navigation pane, choose Resource Management > Storage. In the SFS Turbo volume list, click Unbind next to the target volume.
2. In the dialog box displayed, click OK.

Parent topic: SFS Turbo Volumes