- 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.
EVS Volumes
To meet data persistency requirements, CCI allows you to mount EVS volumes to containers. By using EVS disks, you can mount the file directory of a storage system to a container so that data in the volume is permanently preserved. Even if the container is deleted, only the volume is unmounted. Data in the volume is still stored in the storage system.
EVS supports three specifications: common I/O (previous-generation product), high I/O, and ultra-high I/O.
- Common I/O (previous-generation product): The backend storage is provided by the SATA storage medium. It is perfect for high-capacity application scenarios with low read/write rate requirements and less transaction processing, such as scenarios involving development, testing, and enterprise office applications.
- High I/O: The backend storage is provided by the SAS storage medium. It is perfect for application scenarios with relatively high performance, high read/write rate requirements, and real-time data storage requirements, such as scenarios involving file system creation and distributed file sharing.
- Ultra-high I/O: The backend storage is provided by the SSD storage medium. It is perfect for application scenarios with high performance, high read/write rate requirements, and data-intensive requirements, such as scenarios involving NoSQL, relational database, and data warehouses (such as Oracle RAC and SAP HANA).
Constraints
- EVS disks to be mounted are billed on a pay-per-use basis. For pricing details, see EVS Billing.
- You cannot import the following EVS disks if they not in the current AZ, they are unavailable or frozen, or they are system disks, CCE-associated disks, non-SCSI disks, dedicated disks, or HANA server dedicated disks (high I/O performance optimization/ultra-high I/O latency optimization).
- You can use an EVS volume only as a new disk. The content in the EVS volume that has not been mounted to CCI is invisible to the container.
- If you delete an imported EVS disk from the EVS console, it cannot be detected by CCI. Therefore, delete the EVS disk after you confirm that it is not being used by any workload.
- You can mount an EVS volume to only one pod. Otherwise, data may be lost.
- EVS disk expansion is imperceptible to CCI. You need to unbind the EVS disk on the EVS page of the CCI console before the expansion, and import it again after the expansion is complete.
Adding EVS Disks
- Log in to the CCI console. In the navigation pane on the left, choose Storage > EVS.
- Click Import. On the Import EVS Disk page, select one or more EVS disks that you want to import and click Import.
NOTE:
You can import an EVS disk into one namespace only. After you import an EVS disk into a namespace, it will not be available for import in other namespaces. If you want to import an EVS disk that has its file system (ext4) formatted, ensure that no partition has been created for the disk. Otherwise, data may be lost.
After you import the EVS disk, you can see the corresponding volume.
- Click Buy EVS Volume. On the displayed page, set the parameters, click Next, confirm the specifications, and click Submit.
- PVC Name: Enter the PVC name.
- Namespace: Select the namespace that the PVC belongs to.
- AZ: Specify the availability zone to which the disk belongs.
- Type: Specify the disk type, which can be common I/O (previous-generation product), high I/O, or ultra-high I/O.
- Capacity: The value range is 10 to 32768, in GiB.
Using EVS Volumes
After selecting a container in Creating a Deployment, expand Advanced Settings > Storage, click the EVS Volumes tab, and click Add EVS Volume.
You can mount EVS volumes only to workloads that contain one container.
After you create a workload, you can view the relationship between the EVS disk and the workload by choosing Storage > EVS.
Creating EVS Volumes Using kubectl
For details, see Using PersistentVolumeClaim to Apply for Persistent Storage.
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