If you want to migrate an application in Enterprise Distributed Application Service (EDAS) from Alibaba Cloud public cloud to another Alibaba Cloud environment, or if you want to migrate an application in EDAS across accounts in Alibaba Cloud public cloud, you must import the configurations and program package of the application to your destination environment or account. This helps you reduce O&M costs. This topic describes how to import an application from an on-premises environment to EDAS for management.
Prerequisites
An application is exported to your on-premises environment. For more information, see Export applications.
Scenarios
You migrate an application in EDAS from Alibaba Cloud public cloud to another Alibaba Cloud environment. For example, you migrate an application to EDAS in Alibaba Finance Cloud.
You migrate an application in EDAS across accounts in Alibaba Cloud public cloud. For example, you export an application from a source account and import the application to a destination account.
Quick import
Log on to the EDAS console.
In the left-side navigation pane, choose .
In the upper part of the Applications page, click Import Application.
In the Select Common Files section of the Upload Application dialog box, upload the on-premises JSON file of the application that you want to import, and click OK.
NoteIf you migrate an application in EDAS within the same Alibaba Cloud environment, you do not need to upload the program package. For example, if you migrate an application across accounts or regions in EDAS in Alibaba Cloud public cloud, or across accounts or regions in EDAS in Alibaba Cloud Finance, you do not need to upload the program package.
If you migrate an application in EDAS across Alibaba Cloud environments, such as from Alibaba Cloud public cloud to Alibaba Cloud Finance, you must upload the program package.
In the Import Confirmation dialog box, confirm the information about the application and click Quick Import.
In the Import dialog box, configure the Application Name, Microservices Namespace, Cluster Name, Kubernetes Namespace, and Replica parameters and click OK.
The import process may take a few minutes. If you want to track the import details during the process, perform the following steps: Go to the Applications page. On the right side of the page, click Details to go to the Import/Export Records panel.
Custom import
Log on to the EDAS console.
In the left-side navigation pane, choose .
In the upper part of the Applications page, click Import Application.
NoteOnly Java applications are supported. Multi-language applications are not supported.
In the Select Common Files section of the Upload Application dialog box, upload the JSON file of the on-premises application that you want to import, and click OK.
NoteIf the cloud environment of the source application file is different from the current cloud environment, EDAS displays the Upload Offline Package section. In this section, select Upload Local Package or Offline Package URL to upload the program package.
In the Import Confirmation dialog box, click Import.
In the Configurations step of the Edit Imported Application wizard, configure the environment, basic information, deployment method, and resource parameters for the application, and click Next.
The following table describes the parameters.
Parameter
Description
Microservices Namespace
The microservices namespace in which you want to deploy the application. Select the microservices namespace that you created. If you have not created a microservices namespace or do not select a microservices namespace, this parameter is set to Default.
If you have not created a microservices namespace or you want to create a microservices namespace, click Create Microservices Namespace. For more information, see Manage a microservices namespace.
Cluster
The cluster in which you want to deploy the application. Select an imported Container Service for Kubernetes (ACK) cluster from the Cluster drop-down list.
If the selected Kubernetes cluster is not imported to EDAS, select This cluster is used for the first time in EDAS. If you select this check box, the cluster is imported to EDAS when an application is created. This consumes a certain amount of time. Then, check whether Alibaba Cloud Service Mesh is activated.
NoteYou can select a cluster that does not reside in the same microservices namespace as the application.
K8s Namespace
The Kubernetes namespace of the application. Internal system objects are allocated to different Kubernetes namespaces to form logically isolated projects, teams, or user groups. This way, different groups can be separately managed and share the resources of the entire cluster. Valid values:
default: the default Kubernetes namespace. If an object does not belong to a Kubernetes namespace, the default Kubernetes namespace is used for the object.
kube-system: the Kubernetes namespace for the objects that are created by the system.
kube-public: the Kubernetes namespace that is automatically created by the system. This Kubernetes namespace can be read by all users, including unauthenticated users.
In this example, select default.
If you want to create a custom Kubernetes namespace, click Create Kubernetes Namespace. In the dialog box that appears, enter a name for the Kubernetes namespace in the K8s Namespace field. The name can contain digits, lowercase letters, and hyphens (-), and can be 1 to 63 characters in length. It must start and end with a letter or a digit.
Application Name
The name of the application. The name must start with a letter and can contain digits, letters, and hyphens (-). The name can be up to 36 characters in length.
Application Description
The description of the application. The description can be up to 128 characters in length.
Total Pods
The number of pods on which you want to deploy the application. The maximum or minimum number of pods varies based on the cluster performance.
Single-pod Resource Quota
The CPU and memory quotas that you want to specify for a pod. If you want to specify a quota limit, enter a numeric value. The default value 0 indicates that no limit is specified. If you do not specify quotas, the quotas vary based on the cluster performance.
When you use a JAR or WAR package to deploy an application, you must configure the following parameters.
Parameter
Description
Source of Deployment Package
The source of the application deployment package. By default, Custom Program is selected. If you modify the deployment package, the modified content is used for the import. If you do not modify the deployment package, the deployment package is retrieved from the offline program package.
File Uploading Method
NoteOnly Java applications can be imported. PHP applications and multi-language applications cannot be imported.
Use a JAR package to deploy an application
Upload JAR Package: Select and upload the JAR package that you downloaded.
JAR Package Address: Enter the URL of the JAR package.
Use a WAR package to deploy an application
Upload WAR Package: Select and upload the on-premises WAR package.
WAR Package Address: Enter the URL of the WAR package.
Use a WAR or FatJar package to deploy a High-speed Service Framework (HSF) application
Version
The version number of the application. Specify a custom version number or click Use Timestamp as Version Number to generate a version number.
If you use an image to deploy an application, you must configure the following parameters.
Parameter
Description
Image Type
The type of the image that you want to use to deploy the application. The parameter value is fixed to Configure Image.
If you set the Alibaba Cloud Container Registry parameter to Current Account, perform the following operations:
Configure the Region, Container Registry, Image Repository Namespace, and Image Repository Name parameters and select an image version.
If you set the Alibaba Cloud Container Registry parameter to Other Alibaba Cloud Accounts, perform one of the following operations:
If your image is stored in a public repository, specify the Full Image Address parameter.
If your image is stored in a private repository, use the aliyun-acr-credential-helper component to pull the container image. For more information, see Use the aliyun-acr-credential-helper component to pull images without using a secret.
NoteIf you use an image in a repository of Container Registry Enterprise Edition to create an application as a Resource Access Management (RAM) user, make sure that the RAM user has obtained the required permissions from the relevant Alibaba Cloud account. For more information, see Configure policies for RAM users to access Container Registry.
(Optional) In the Advanced Settings step, configure the following settings:
After you complete the configurations, click Complete Configuration. Then, click Confirm Import.
The import process may take a few minutes. If you want to track the import details during the process, perform the following steps: Go to the Applications page. On the right side of the page, click Details to go to the Import/Export Records panel.