Managing Resources

Prerequisites

The following resources to be managed are required.

• The ECSs to be managed have been created and are in the running state. The ECSs must be in the same VPC as the target environment and cannot be managed by other environments.

  ECSs are used to deploy and run components on VMs. For details about how to create ECSs, see Purchasing ECSs.

• The AS groups to be managed have been created. The AS groups must be in the same VPC as the target environment and cannot be managed by other environments. In addition, the AS groups contain ECSs.

  AS groups are used to deploy and run components on VMs. For details about how to create AS groups, see Creating an AS Group.

  AS groups cannot be managed in LA-Sao Paulo1 and LA-Mexico City2.

• The ELBs to be managed have been created. The ELBs must be in the same VPC as the target environment.

  ELBs are used to access services provided by components in ELB mode. For details about how to create ELBs, see Creating a Shared Load Balancer.

• The EIPs to be managed have been created.

  EIPs are used to access services provided by a component through public network. For details about how to create EIPs, see Assigning an EIP.

• The DCSs to be managed have been created. The DCSs must be in the same VPC as the target environment.

  DCSs are used to read environment variables to obtain distributed cache information during application running. For details about how to create DCSs, see Buying a DCS Redis Instance.

• The RDS MySQL DB instances to be managed have been created. The RDSs must be in the same VPC as the target environment.

  RDSs are used for persistent storage of application data. For details about how to create RDSs, see Step 1: Buy a DB Instance.

• The CSEs to be managed have been created. If the CSEs and the environment are in different VPC, correctly configure the VPC connectivity.

  CSEs are used to connect microservices running in the environment to the engine to implement microservice registry and discovery, service governance, and configuration management. For details about how to create CSEs, see Creating a Microservice Engine.

Procedure

1. Log in to ServiceStage.
2. On the Environment Management page, click the target environment.
3. In the left pane of the Resource Settings page, manage resources in the environment by referring to the following table.

   Resource Type	Resource Name	Operation
   Compute	Cloud Container Engine	See Binding a CCE Cluster. For details about how to manage CCE clusters in the Kubernetes environment, see CCE Resource Management.
   	Elastic Cloud Server	Choose Compute > Elastic Cloud Server. Click Manage Resource. Select the ECS to be managed. Click OK. NOTE: In the same VPC, ECSs that have been managed by other environments cannot be managed again. In a VM environment, if Agent Status of the managed ECSs is Install Agent, install the agent by referring to Installing a VM Agent.
   	Auto Scaling	Choose Compute > Auto Scaling. Click Manage Resource. Select the AS resource to be managed. Click OK. NOTE: In the same VPC, AS groups that have been managed by other environments cannot be managed again.
   Networking	Elastic Load Balance	Choose Networking > Elastic Load Balance. Click Manage Resource. Select the load balancer to be managed. Click OK.
   	Elastic IP	Choose Network > Elastic IP. Click Manage Resource. Select the EIP to be managed. Click OK.
   Middleware	Distributed Cache Service	Choose Middleware > Distributed Cache Service. Click Manage Resource. Select the DCS instance to be managed. Click OK.
   	Cloud Service Engine	Choose Middleware > Cloud Service Engine. Click Manage Resource. Select the microservice to be managed. Click OK.
   	Relational Database Service	Choose Middleware > Relational Database Service. Click Manage Resource. Select the RDS instance to be managed. Click OK.