Enterprise Distributed Application Service:Configure local storage

Configure local storage when you create an application

1. Log on to the EDAS console. In the left-side navigation pane, choose Application Management > Applications. The Applications page appears. In the top navigation bar, select a region. In the upper part of the page, select a namespace. In the upper-left corner, click Create Application.

2. In the Basic Information step, specify Cluster Type and Application Runtime Environment and click Next. The following table describes the parameters.

   Parameter	Description
   Cluster Type	The type of the cluster in which you want to deploy the application. Select Kubernetes Clusters.
   Application Runtime Environment	The application runtime environment. Select an application runtime environment based on the type of the hosted application. Java Custom: Select this option if you want to use a custom image to deploy the application in a Kubernetes cluster. Java: Select this option if you want to use a universal JAR package to deploy the application as a Dubbo or a Spring Boot application. You can set the Java Environment parameter after you select this option. Tomcat: Select this option if you want to use a universal WAR package to deploy the application as a Dubbo or a Spring application. You can set the Java Environment and Container Version parameters after you select this option. EDAS-Container (HSF): Select this option if you want to use a WAR or FatJar package to deploy the application as a High-speed Service Framework (HSF) application. You can set the Java Environment, Pandora Version, and Ali-Tomcat Version parameters after you select this option. PHP: Select this option if the application is a PHP application that runs on Apache HTTP Server. Node.js, C++, Go, and Other Languages: Select this option if you want to use a custom image to deploy the application in a Kubernetes cluster. The configuration process for multi-language applications is not described in this topic.

3. In the Configurations step, configure the environment information, basic information, and deployment method for the application, set the related resource parameters, and then click Next.

4. In the Advanced Settings step, click Local Storage and configure local storage as needed.

   Local storage supports Local File of Host and emptyDir.

   • Local File of Host

     File Type	Value	Description
     Default	Empty string	Indicates that the file is directly mounted without a file type check.
     (Create) File Directory	DirectoryOrCreate	The file directory. If no file directory exists, a directory is created.
     File Directory	Directory	The file directory. If no file directory exists, container startup fails.
     (Create) File	FileOrCreate	The file. If no file exists, a file is created.
     File	File	The file. If no file exists, container startup fails.
     Socket	Socket	The standard UNIX Socket file. If no file exists, container startup fails.
     CharDevice	CharDevice	The character device file. If no file exists, container startup fails.
     BlockDevice	BlockDevice	The block storage device file. If no file exists, container startup fails.

   • emptyDir

     Volumes of the emptyDir type are used for data sharing among temporary spaces or different containers.

     Parameter	Description
     Mount Mode	The mount mode. Valid values: Read/Write and Read-only.
     Mount Path	The mount path of emptyDir volumes.
     subPathExpr	The field that is used to build the directory name of subPath volumes.

5. Click Create Application.

6. On the Creation Completed page, check the information in the Basic Information, Configurations, and Advanced Settings sections. Then, click Create Application.

   In the upper part of the Application Overview page, click View Details. On the Change List page, view the application change process. Wait several minutes until the application is deployed. After the application change process is complete, view the status of the instance in the Basic Information section of the Application Overview page. If the status shows that a pod is running, the application is deployed.

Configure local storage when you update an application

You can configure local storage when you create an application, or configure or update local storage when you deploy an application.

1. Log on to the EDAS console.

2. In the left-side navigation pane, click Application Management > Applications. In the top navigation bar, select a region. In the upper part of the page, select a namespace. Select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list. Then, find the application that you want to deploy and click the application name.

3. On the Overview or Basic information page, choose Deploy > Deploy in the upper-right corner.

4. On the Select Deployment Mode page, select a deployment mode and click Start Deployment in the upper-right corner of the specified deployment mode section.

5. Set the environment and deployment package for an application, click Local Storage, complete the configuration as needed, and then click OK.

   Local storage supports Local File of Host and emptyDir.

   Important

   The application is restarted after you click OK. We recommend that you perform this operation during off-peak hours.

   • Local File of Host

     File Type	Value	Description
     Default	Empty string	Indicates that the file is directly mounted without a file type check.
     (Create) File Directory	DirectoryOrCreate	The file directory. If no file directory exists, a directory is created.
     File Directory	Directory	The file directory. If no file directory exists, container startup fails.
     (Create) File	FileOrCreate	The file. If no file exists, a file is created.
     File	File	The file. If no file exists, container startup fails.
     Socket	Socket	The standard UNIX Socket file. If no file exists, container startup fails.
     CharDevice	CharDevice	The character device file. If no file exists, container startup fails.
     BlockDevice	BlockDevice	The block storage device file. If no file exists, container startup fails.

   • emptyDir

     Volumes of the emptyDir type are used for data sharing among temporary spaces or different containers.

     Parameter	Description
     Mount Mode	The mount mode. Valid values: Read/Write and Read-only.
     Mount Path	The mount path of emptyDir volumes.
     subPathExpr	The field that is used to build the directory name of subPath volumes.

Verify the result

• Method 1

  In the left-side navigation pane of the application details page, click Change Records to view the change details of the application. If the value in the Change Status column is Success, the application is deployed and the configuration takes effect.

• Method 2

  On the Application Overview page, click Running Pods (Click View) next to Running Status. In the Pod section of the App Configurations panel, check the Status column of the pod. If a green dot appears, the application is in the running state. This means that the application is deployed as expected and the configuration takes effect.