Managing Basic Resources

Prerequisites

The following basic resources to be managed have been created:

• ECSs, which must be in the running state and 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, see Purchasing a Custom ECS.

• AS groups, which 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, see Creating an AS Group.

• Load balancers, which must be in the same VPC as the target environment.

  Load balancers are used to access services provided by components in ELB mode or perform ELB dark launch. Create a load balancer based on the actual application scenario.

  Scenario	Reference
  Use the domain name to access an application.	Creating a Shared Load Balancer. See Creating a Dedicated Load Balancer.
  ELB dark launch	See Creating a Dedicated Load Balancer.

• EIPs.

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

• VPCs, which provide a logically isolated, configurable, and manageable virtual network environment, improving cloud resource security and simplifying network deployment.

  For details, see Creating a VPC.

• VPC subnets. A VPC subnet is a CIDR block in a VPC, and subnets in a VPC are on the Layer 3 network. You can create multiple subnets in a VPC to manage cloud resources.

  For details, see Creating a VPC.

• Network ACLs, which provide security protection for the associated subnets.

  For details, see Creating a Network ACL.

• DCS instances, which must be in the same VPC as the target environment.

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

• RDS MySQL DB instances, which must be in the same VPC as the target environment.

  RDS instances are used for persistent storage of application data. For details, see Buying an RDS for MySQL DB Instance.

• ServiceComb engines (microservice engines, see Cloud Service Engine Overview). If the microservice engines and the environment are in different VPC, correctly configure the VPC connectivity.

  Microservice engines 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, see Creating a Microservice Engine.

• Registry/configuration centers. If the Nacos engines and the environment are in different VPC, correctly configure the VPC connectivity.

  Registry/configuration centers are used to connect microservices running in the environment to the engine to implement microservice registry and discovery, and configuration management. For details, see Creating a Registry/Configuration Center.

Managing Basic Resources

1. Log in to ServiceStage.
2. Choose Environment Management. The Environment Management page is displayed.
3. Click the target environment. The Overview page is displayed.
4. Manage the required basic resources in the environment by referring to the following table.

   Resource Type	Resource Name	Operation
   Compute	Clusters	See Binding a CCE Cluster. CCE clusters can be bound to a Kubernetes environment. To manage CCE clusters in the environment, see Managing CCE Resources.
   	ECSs	Choose Compute > ECSs. Click Manage Resource. Select the ECSs to be managed. Click OK. NOTE: ECSs can be managed in a VM environment. In the same VPC, ECSs that have been managed by other environments cannot be managed again. If Agent Status of the managed ECSs indicates that the agent is missing and to install it first, install the agent. For details, see Installing a VM Agent.
   	AS Groups	Choose Compute > AS Groups. Click Manage Resource. Select the AS groups to be managed. Click OK. NOTE: AS groups can be managed in a VM environment. In the same VPC, AS groups that have been managed by other environments cannot be managed again. If Agent Status of the ECSs of the managed AS groups indicates that the agent is missing and to install it first, install the agent. For details, see Installing a VM Agent.
   Networking	Load Balancers	Choose Networking > Load Balancers. Click Manage Resource. Select the load balancers to be managed. Click OK.
   	VPC EIPs	Choose Networking > VPC EIPs. Click Manage Resource. Select the EIPs to be managed. Click OK.
   	VPCs	Choose Network > VPCs. Click Manage Resource. Select the VPCs to be managed. Click OK.
   	Subnet	Choose Network > Subnet. Click Manage Resource. Select the VPC subnets to be managed. Click OK.
   	ACL	Choose Network > ACL. Click Manage Resource. Select the ACLs to be managed. Click OK.
   Middleware	DCS Instances	Choose Middleware > DCS Instances. Click Manage Resource. Select the DCS instances to be managed. Click OK.
   	ServiceComb Engines	Choose Middleware > ServiceComb Engines. Click Manage Resource. Select the ServiceComb engines to be managed. Click OK.
   	Registry/Configuration Center	Choose Middleware > Registry/Configuration Center. Click Manage Resource. Select the registry/configuration centers to be managed. Click OK.
   	RDS Instances	Choose Middleware > RDS Instances. Click Manage Resource. Select the RDS instances to be managed. Click OK.