All Products
Search
Document Center

Create resources

Last Updated: Feb 26, 2019

To deploy an application in EDAS, you must create the required resources.

To help simplify resource utilization, the following describes the basic concepts of EDAS resources.

Basic concepts

Resources Definition Scenarios
Elastic Compute Service (ECS) ECS is a computing service provided by Alibaba Cloud that has elastic processing capabilities. The applications that you publish in EDAS are deployed on ECS instances.
EDAS Agent EDAS Agent is a Daemon program provided by EDAS for communication between applications and EDAS service clusters and between applications and the EDAS console. EDAS Agent is installed on an ECS instance, so you can use and manage the ECS instance in EDAS.
Clusters In EDAS, a cluster is a collection of ECS instances used to deploy applications. To meet demanding security requirements, you must specify a namespace and a VPC network when creating a cluster.
Namespace A namespace is an isolated resource environment built in a region. To meet demanding resource security requirements, you must create a namespace.
Virtual Private Cloud (VPC) A VPC network is an isolated network environment built in Alibaba Cloud. To meet demanding network security requirements, we recommend that you create a VPC network and add ECS instances.
Server Load Balancer (SLB) SLB is a load balancing service provided by Alibaba Cloud for distributing traffic among multiple ECS instances. SLB instances are used to achieve load balancing among ECS instances.Your application is accessible on the Internet through the IP address and port of an Internet SLB instance.

By default, all of the preceding resources must be created.The exceptions to this rule are described at the beginning of the relevant sections.

Note: Chrome browser is recommended for operations in EDAS console.

Create VPCs

To create an ECS cluster and publish a common application without special network security requirements, you can skip this step and use a classic network.

  1. Log on to the VPC console to create a VPC network.For detailed instructions, see Deploy a VPC.

    Note: If you have not activated the VPC service, click Activate VPC Service.On the VPC sales page, read and agree to the VPC Activation Agreement and then click Open Now.

  2. Synchronize the VPC network to the EDAS console.

    1. Log on to the EDAS console. In the left-side navigation pane, choose Resource Management > VPC.

    2. On the VPC page, select the region where the created VPC is located, for example, East China 1. Then, click Synchronize VPC in the upper-right corner.

    3. Verify that the created VPC network has been synchronized to the EDAS console.

Create ECS instances

  1. Log on to the EDAS console.

  2. In the left-side navigation pane, choose Resource Management > ECS.

  3. Select a region and namespace (optional) for the ECS instance to be created. Then, click Create Instance in the upper-right corner.

  4. On the ECS purchase page, select ECS type and configuration and pay for it. See Create ECS instances for details.

    The application configuration specifications are as follows:

    Cluster typeConfiguration requirement Attach data diskNotes
    ECS clusterCPU≥1 vCPU
    Memory size ≥1 GB
    Supported
    • JVMs are multi-thread applications that may cause problems when they run out of memory.Therefore, avoid applying the minimum configurations to the ECS instances added to the cluster created in the production environment.
    • When all target ECS instances are added to the cluster, set the swap partition.This prevents the log process and other processes from using a lot of memory resources and thus from causing running faults in the operating system.
    Swarm ClusterCPU≥1 vCPU
    Memory size ≥1 GB
    Not supported. Plan disk space in advance.
    • JVMs are multi-thread applications that may cause problems when they run out of memory.Therefore, avoid applying the minimum configurations to the ECS instances added to the cluster created in the production environment.
    • When all target ECS instances are added to the cluster, set the swap partition.This prevents the log process and other processes from using a lot of memory resources and thus from causing running faults in the operating system.
    Container Service Kubernetes clusterCPU≥1 vCPU
    Memory size ≥ 2 GB
    Supported
    • When all target ECS instances are added to the cluster, set the swap partition.This prevents the log process and other processes from using a lot of memory resources and thus from causing running faults in the operating system.

    Note: After you create the ECS instance, it is added to the default namespace and cluster.

Create namespaces

You can skip this step if you have no special resource security requirements.In this case, you can use the default namespace of a region.

  1. Log on to the EDAS console.

  2. In the left-side navigation pane, choose Application Management > Namespace.

  3. On the Namespace page, select Region and click Create Namespace in the upper-right corner.

  4. In the Create Namespace dialog box, set Namespace Name (required), Namespace ID (required), and Namespace Type (to Normal Namespace), and enter descriptions as needed.Click Confirm.

    Note: The prefix of a namespace ID is determined by the specified region (target region) and cannot be modified. Instead, only the custom part can be modified.

    Create namespace

Create clusters

Create clusters

  1. In the left-side navigation pane, choose Resource Management > Cluster.

  2. On the Clusters page, select a region and click Create Cluster in the upper-right corner.

  3. In the Create Cluster dialog box, set the cluster parameters and click Create to save the settings.

    Configuration Description
    Cluster Name Name of a cluster, which contains a maximum of 64 characters consisting of letters, digits, underscores (_), hyphens (-), and periods (.).
    Cluster Type Select ECS for common applications and Swarm for Docker applications.Note: A Container Service Kubernetes cluster must be created in Container Service and then synchronized to the EDAS console. For more information, see Create Container Service Kubernetes clusters.
    Network Type If Cluster Type is set to ECS, Network Type can be VPC or Classic Network. If Cluster Type is set to Swarm, Network Type can only be VPC because Swarm clusters in EDAS do not support classic networks.
    VPC Select the VPC you created.
    Namespace This parameter is selected on the Clusters page and cannot be modified here.If no namespace is configured, the default namespace of the region is selected by default and displayed as the region name, for example East China 1.

Add ECS instances

You can add ECS instances to a cluster on the EDAS in either of the following ways:

  1. Directly import instances to the cluster without image conversion.

  2. Re-install the system with the EDAS official image. After re-installation, all data in the instance will be deleted and a new password for logging on to the instance must be configured.

You cannot import an instance directly to a cluster in any of the following conditions:

  • The ECS instance was created before December 1, 2017.
  • The instance of classic network type is imported into a cluster of classic network type.
  • The instance is not running, for example, the instance is in Stopped, Starting, or Stopping status.
  • If you create a Windows instance or another instance that does not support simple shell commands, it cannot be imported to EDAS and converted successfully.
  • The instance is not imported from an ECS cluster.
  1. On the Clusters page, select a region, such as East China 1, and click the name of the created cluster.

  2. On the Cluster Details page, click Add ECS Instance in the upper-right corner.

  3. On the Select Cluster and ECS page, select an instance addition method and ECS instance in the instance list, and then click Next.

    • Import ECS: You cannot modify the namespace and the imported cluster. Also, ECS instances are imported from the default namespace and cluster under this region.
    • From Existing Cluster: A namespace and a cluster are selected from the region.Then, the ECS instance is moved from the left pane to the right pane on the page.

    If no instances meet the necessary conditions, click Create ECS Instance in the upper-right corner of the page. This takes you to the ECS purchase page on the Alibaba Cloud official website, where you can purchase and create a new ECS instance.For more information, see Create ECS instances.

  4. On the Ready to Import Page, view the information of the selected instance.

    • If the ECS instance can be imported directly, click Confirm and Import.
    • If the instance needs to be converted, select I agree to convert the above instances, and fully understand that the data in the original systems will be lost after conversion.Then, enter a new password for root user logon after the conversion.Click Confirm and Import.
  5. On the Import tab page, view the import progress of the instance.

    • If the ECS instance supports direct import, you can view its import progress on the Import tab page. If the message Instance transfer succeeded is displayed, the ECS instance has been imported successfully.Click Click to return to the Cluster Details page. When the ECS instance status changes to Running, the ECS instance is imported to the cluster successfully.
    • For an ECS instance that needs to be converted before being imported, the import progress of the ECS instance displayed on the Import page is Converting now. This may take 5 minutes.If you click Click to return to the Cluster Details page before the import is completed, the health check status Converting and the conversion progress in percentage are displayed. When the import is completed, the health check status Running is displayed.

Synchronize SLB instances to EDAS

  1. Log on to the SLB console to create an SLB instance.For detailed instructions, see Create SLB instances.

  2. Synchronize the SLB instance to the EDAS console.

    1. Log on to the EDAS console. In the left-side navigation pane, choose Resource Management > SLB.

    2. On the SLB page, select the region where the created SLB instance is located, such as East China 1. Then, click Synchronize SLB in the upper-right corner.

    3. Verify that the created SLB instance has been synchronized to the EDAS console.