Help Center> Cloud Container Instance (CCI)> User Guide> Storage Management> EVS Volumes
View PDF

EVS Volumes

To meet data persistency requirements, CCI allows you to mount EVS disks to containers. By using EVS disks, you can mount the remote 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, high I/O, and ultra-high I/O.

  • Common I/O: The back-end 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 back-end 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 back-end 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

  • You cannot import the following EVS disks: disks that are not located in the current AZ, unavailable disk, system disk, CCE-associated disk, non-SCSI disk, non-shared disk, dedicated disk, frozen disk, and HANA server dedicated disk (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.

Adding EVS Disks

  1. Log in to the CCI console. In the navigation pane, choose Storage > EVS.

    • If you have purchased EVS disks on the EVS console, go to 2.
    • If you have not purchased any EVS volume, go to 3.

  2. Click Import. On the Import EVS Disk page, select one or more EVS disks that you want to import and click Import.

    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.

    Figure 1 Import result

  3. Click Buy EVS Volume. On the Buy EVS Volume page, set parameters, click Next, confirm the specifications, and click Submit.

    • PVC Name: Enter the PVC name.
    • Namespace: Select the namespace to which the PVC belongs.
    • Type: Specify the disk type, which can be common I/O, high I/O, or ultra-high I/O.
    • Capacity: Specify the disk capacity, which ranges from 10 to 1,000 GB.
    • AZ: Specify the availability zone to which the disk belongs.
    • Encryption: KMS Encryption is deselected by default. If you select KMS Encryption, set the following parameters:

      Currently, the encryption function is not available in region CN East-Shanghai1.

      • Agency Name: Agencies can be used to assign permissions to trusted accounts or cloud services for a specific period of time. If no agency is created, click Create Agency. The agency name EVSAccessKMS indicates that EVS is granted the permission to access KMS and can obtain KMS keys to encrypt and decrypt EVS disks.
      • Key Name: A secret is a type of resource that holds user-defined, sensitive data, such as authentication and key information. Secrets can be loaded into containerized applications. For details on how to create a secret, see Creating a CMK.
      • Key ID: generated by default.

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.

Figure 2 Configuring EVS volume parameters

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.

Figure 3 Managing EVS volumes

Creating EVS Volumes Using kubectl

For details, see Using Persistent Storage.

Parent topic: Storage Management