- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
-
Developer Guide
- Overview
- Using Native kubectl (Recommended)
- Namespace and Network
- Pod
- Label
- Deployment
- EIPPool
- EIP
- Pod Resource Monitoring Metric
- Collecting Pod Logs
- Managing Network Access Through Service and Ingress
- Using PersistentVolumeClaim to Apply for Persistent Storage
- ConfigMap and Secret
- Creating a Workload Using Job and Cron Job
- YAML Syntax
-
API Reference
- Before You Start
- Calling APIs
- Getting Started
- Proprietary APIs
-
Kubernetes APIs
- ConfigMap
- Pod
- StorageClass
- Service
-
Deployment
- Querying All Deployments
- Deleting All Deployments in a Namespace
- Querying Deployments in a Namespace
- Creating a Deployment
- Deleting a Deployment
- Querying a Deployment
- Updating a Deployment
- Replacing a Deployment
- Querying the Scaling Operation of a Specified Deployment
- Updating the Scaling Operation of a Specified Deployment
- Replacing the Scaling Operation of a Specified Deployment
- Querying the Status of a Deployment
- Ingress
- OpenAPIv2
- VolcanoJob
- Namespace
- ClusterRole
- Secret
- Endpoint
- ResourceQuota
- CronJob
-
API groups
- Querying API Versions
- Querying All APIs of v1
- Querying an APIGroupList
- Querying APIGroup (/apis/apps)
- Querying APIs of apps/v1
- Querying an APIGroup (/apis/batch)
- Querying an APIGroup (/apis/batch.volcano.sh)
- Querying All APIs of batch.volcano.sh/v1alpha1
- Querying All APIs of batch/v1
- Querying All APIs of batch/v1beta1
- Querying an APIGroup (/apis/crd.yangtse.cni)
- Querying All APIs of crd.yangtse.cni/v1
- Querying an APIGroup (/apis/extensions)
- Querying All APIs of extensions/v1beta1
- Querying an APIGroup (/apis/metrics.k8s.io)
- Querying All APIs of metrics.k8s.io/v1beta1
- Querying an APIGroup (/apis/networking.cci.io)
- Querying All APIs of networking.cci.io/v1beta1
- Querying an APIGroup (/apis/rbac.authorization.k8s.io)
- Querying All APIs of rbac.authorization.k8s.io/v1
- Event
- PersistentVolumeClaim
- RoleBinding
- StatefulSet
- Job
- ReplicaSet
- Data Structure
- Permissions Policies and Supported Actions
- Appendix
- Out-of-Date APIs
- Change History
-
FAQs
- Product Consulting
-
Basic Concept FAQs
- What Is CCI?
- What Are the Differences Between Cloud Container Instance and Cloud Container Engine?
- What Is an Environment Variable?
- What Is a Service?
- What Is Mcore?
- What Are the Relationships Between Images, Containers, and Workloads?
- What Are Kata Containers?
- Can kubectl Be Used to Manage Container Instances?
- What Are Core-Hours in CCI Resource Packages?
- Workload Abnormalities
-
Container Workload FAQs
- Why Service Performance Does Not Meet the Expectation?
- How Do I Set the Quantity of Instances (Pods)?
- How Do I Check My Resource Quotas?
- How Do I Set Probes for a Workload?
- How Do I Configure an Auto Scaling Policy?
- What Do I Do If the Workload Created from the sample Image Fails to Run?
- How Do I View Pods After I Call the API to Delete a Deployment?
- Why an Error Is Reported When a GPU-Related Operation Is Performed on the Container Entered by Using exec?
- Can I Start a Container in Privileged Mode When Running the systemctl Command in a Container in a CCI Cluster?
- Why Does the Intel oneAPI Toolkit Fail to Run VASP Tasks Occasionally?
- Why Are Pods Evicted?
- Why Is the Workload Web-Terminal Not Displayed on the Console?
- Why Are Fees Continuously Deducted After I Delete a Workload?
-
Image Repository FAQs
- Can I Export Public Images?
- How Do I Create a Container Image?
- How Do I Upload Images?
- Does CCI Provide Base Container Images for Download?
- Does CCI Administrator Have the Permission to Upload Image Packages?
- What Permissions Are Required for Uploading Image Packages for CCI?
- What Do I Do If Authentication Is Required During Image Push?
-
Network Management FAQs
- How Do I View the VPC CIDR Block?
- Does CCI Support Load Balancing?
- How Do I Configure the DNS Service on CCI?
- Does CCI Support InfiniBand (IB) Networks?
- How Do I Access a Container from a Public Network?
- How Do I Access a Public Network from a Container?
- What Do I Do If Access to a Workload from a Public Network Fails?
- What Do I Do If Error 504 Is Reported When I Access a Workload?
- What Do I Do If the Connection Timed Out?
- Storage Management FAQs
- Log Collection
- Account
- SDK Reference
- Videos
- General Reference
Copied.
SFS Turbo Volumes
You can mount SFS Turbo file systems to containers. SFS Turbo volumes are fast, on-demand, and scalable. They are suitable for DevOps, containerized microservices, and enterprise office applications.
Constraints
- SFS Turbo file systems to be mounted are billed on a pay-per-use basis. For pricing details, see SFS Turbo Billing.
- If an SFS Turbo file system is in use, the VPC where the file system is deployed cannot be modified. If the VPC is modified, the containers in CCI will not be able to access the file system.
- If an SFS Turbo file system is deleted, containers in CCI will become unavailable.
Importing SFS Turbo File Systems
CCI allows you to import existing SFS Turbo file systems.
- Log in to the CCI console. In the navigation pane on the left, choose Storage > SFS Turbo. On the page displayed, select a namespace and click Import.
- Select one or more SFS Turbo file systems that you want to import, and click Import.
If no SFS Turbo volumes are available, click create an SFS Turbo file system to create one.
After you create the SFS Turbo file system, go back to the Import SFS Turbo File System page on the CCI console. Then, select the created SFS Turbo file system and click Import.
Figure 1 Importing SFS Turbo file systems - Specify the mount option for the SFS Turbo volume to ensure real-time data access. If you mount an SFS Turbo volume to more than one pod, there will be a delay in pod metadata access due to local caching in pods.
You can set mount options for specific SFS Turbo volumes. Currently, only the noac mount option is supported. You can use this option to disable local file and directory caching, and allow pods to access data from the SFS Turbo volume in real time.
NOTE:
The mount option is valid only for SFS Turbo volumes created in the current namespace.
Figure 2 Setting the mount option for an SFS Turbo volume
Using SFS Turbo Volumes
After you select a container image when you create a Deployment or create a job, expand Advanced Settings > Storage, click the SFS Turbo Volumes tab, and click Add SFS Turbo Volume.

- When an SFS Turbo file system is being created, an independent VM will be created, which will take a long time. Therefore, you are advised to select existing SFS Turbo volumes.
- subPath is a sub-directory in the root path of the SFS Turbo file system. If such a sub-directory does not exist, it is automatically created in the SFS Turbo file system. Note that subPath must be a relative path.
Unbinding SFS Turbo Volumes
If you no longer require an imported SFS Turbo volume, you can unbind it from the SFS Turbo file system. After you unbind an SFS Turbo file system, you can no longer use it for your workloads.
If you have mounted an SFS Turbo volume to a workload, you cannot unbind it from the SFS Turbo file system.
- Log in to the CCI console. In the navigation pane on the left, choose Storage > SFS Turbo. In the SFS Turbo volume list, click Unbind next to the target volume.
- Read the message that is displayed and click Yes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot