Managing Basic Resources

After an environment is created, you can manage required basic resources and combine them into an environment for deploying and running components.

Prerequisites

You have created an environment. For details, see Creating an Environment.

You have created basic resources based on the environment type and site requirements by referring to the following table.

Resource Type	Resource Name	Description	Restrictions	Creation Method	Billing
Compute	Clusters	Used to deploy components in container mode. Components are deployed using container images and scheduled by Kubernetes.	Clusters can be bound to a Kubernetes or VM + Kubernetes environment.	See Binding a Cluster.	See CCE Billing.
	ECSs	Used to deploy and run components based on a VM.	ECSs can be managed in a VM or VM + Kubernetes environment. The ECS must be in the same VPC as the environment and cannot be managed by other environments.	See Purchasing an ECS in Custom Config Mode.	See ECS Billing.
	Custom servers	You can manage custom servers on ServiceStage for deploying and running components based on a VM.	Custom servers can be managed in a VM or VM + Kubernetes environment. You have obtained the name, unique ID, and IP address of the custom server, and the custom server cannot be managed by other environments.	-	-
	AS Groups	Used to deploy and run components based on a VM.	AS groups can be managed in a VM or VM + Kubernetes environment. The AS group must be in the same VPC as the environment and cannot be managed by other environments.	See Creating an AS Group.	See AS Pricing Details.
Networking	Load Balancers	Used to access services provided by a component through the domain name using the load balancer bound with an EIP, or to upgrade the container-deployed components through ELB dark launch.	-	Use the domain name to access an application. See Creating a Shared Load Balancer. Create an application load balancer by referring to Creating a Dedicated Load Balancer. ELB dark launch Create an application load balancer by referring to Creating a Dedicated Load Balancer.	See ELB Billing.
	VPC EIPs	Used to access services provided by a component.	-	See Assigning an EIP.	See EIP Billing.
	VPCs	Provides a logically isolated, configurable, and manageable virtual network environment, improving cloud resource security and simplifying network deployment.	-	See Creating a VPC with a Subnet.	See VPC Billing.
	Subnet	A subnet is a CIDR block in a VPC, and is on the Layer 3 network. You can create multiple subnets in a VPC to manage cloud resources.	-	See Creating a Subnet for an Existing VPC.	See VPC Billing.
	ACL	Provides security protection for associated subnets.	-	See Creating a Network ACL.	See VPC Billing.
Middleware	DCS Instances	Used to read environment variables to obtain distributed cache information during application running.	-	See Buying a DCS Redis Instance.	See DCS Billing.
	ServiceComb Engines	Microservice engine (see Cloud Service Engine Overview), which is used to connect microservices running in the environment to the engine to implement microservice registry and discovery, service governance, and configuration management.	In an HA environment of the Kubernetes type, each AZ can manage only one ServiceComb engine.	See Creating a Microservice Engine.	If you have purchased a ServiceStage resource package, you can create a ServiceComb engine of the corresponding version for free. For details, see Buying a ServiceStage Resource Package. If you use ServiceStage in pay-per-use billing mode or create additional ServiceComb engines, see ServiceComb Engine Billing.
	Registry/Configuration Center	Connects microservices running in the environment to implement microservice registry and discovery, and configuration management.	-	See Creating a Registry/Configuration Center.	See .-
	RDS Instances	Used for persistent storage of application data.	-	See Buying an RDS for MySQL DB Instance.	See RDS Billing.
	Application Gateways	Connects microservices running in the environment to implement full-link rate limiting and API management.	In an HA environment of the Kubernetes type, each AZ can manage only one application gateway.	See .-	-
	GaussDB	Used for persistent storage of application data.	-	See Buying a GaussDB Instance.	See GaussDB Billing.
	RocketMQ	Used for application production message storage and consumption subscription.	-	See Buying a RocketMQ Instance.	See RocketMQ Billing.
	CSS	Uses the multi-condition search, statistics, and report capabilities of structured and unstructured text provided by the Elasticsearch cluster of Cloud Search Service (CSS) to analyze component logs in all scenarios.	-	See Creating an Elasticsearch Cluster.	See CSS Billing.

Managing Basic Resources

Log in to ServiceStage.
Choose Environment Management. The Environment Management page is displayed.
Click the target environment. The Overview page is displayed.

Manage the required basic resources in the environment by referring to the following table.

Resource Type	Resource Name	Operation
Compute	Clusters	See Binding a Cluster. Clusters (CCE and custom Kubernetes clusters) can be bound to a Kubernetes or VM + Kubernetes environment. To manage clusters in the environment, see Managing Cluster Resources.
	ECSs	Choose Compute > ECSs. Click Manage Resource. Select the ECSs to be managed. Click OK. ECSs can be managed in a VM or VM + Kubernetes environment. 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.
	Custom servers	Choose Compute > Custom servers. Set Server Name, ID, and IP of the target custom server. Click Add Server to add more custom servers to the environment. Click Remove to remove a custom server from the list. Click OK. Custom servers can be managed in a VM or VM + Kubernetes environment. For custom servers that are initially managed and do not have a VM agent installed (see Installing a VM Agent), you need to customize the Server Name and ID. Where, Server Name contains 1 to 128 characters. Use letters, digits, underscores (_), hyphens (-), and dots (.). ID contains 1 to 64 characters. Use letters, digits, underscores (_), and hyphens (-). Keep the custom ID properly for future operations such as re-management. To manage a custom server with a VM agent installed (see Installing a VM Agent), set ID to the value you have defined during the first management. Server Name can be customized. Server Name contains 1 to 128 characters. Use letters, digits, underscores (_), hyphens (-), and dots (.). The custom server to be managed must be able to access the environment where ServiceStage is deployed through network and cannot be managed by other environments.
	AS Groups	Choose Compute > AS Groups. Click Manage Resource. Select the AS groups to be managed. Click OK. AS groups can be managed in a VM or VM + Kubernetes environment. 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 Next. (Optional) Set Redis Login Password. If the selected DCS instances are configured with the password access mode, you need to set the login password. You can also skip this operation and configure the parameters by referring to Follow-up Operations after the DCS instances are successfully managed. Click OK. After the DCS instances are successfully managed in the environment, ServiceStage writes the built-in and custom environment variables in the environment by referring to Table 1 for use.
	ServiceComb Engines	Choose Middleware > ServiceComb Engines. Click Manage Resource. Select the ServiceComb engines to be managed. Click OK. After the ServiceComb engines are successfully managed in the environment, ServiceStage writes the built-in environment variables in the environment by referring to Table 1 for use.
	Registry/Configuration Center	Choose Middleware > Registry/Configuration Center. Click Manage Resource. Select the registry/configuration centers to be managed. Click OK. After the registry/configuration centers are successfully managed in the environment, ServiceStage writes the built-in environment variables in the environment by referring to Table 1 for use.
	RDS Instances	Choose Middleware > RDS Instances. Click Manage Resource. Select the RDS instances to be managed. Click Next. (Optional) Set Database Name, Database User Name, and Database Login Password. You can also skip this operation and configure the parameters by referring to Follow-up Operations after the RDS instances are successfully managed. Click OK. After the RDS instances are successfully managed in the environment, ServiceStage writes the built-in and custom environment variables in the environment by referring to Table 1 for use.
	Application Gateways	Choose Middleware > Application Gateways. Click Manage Resource. Before managing the application gateways in the HA environment of the Kubernetes type, select the AZ where these application gateways are located. Select the application gateways to be managed. Click OK.
	GaussDB	Choose Middleware > GaussDB. Click Manage Resource. Select the GaussDB instances to be managed. Click Next. (Optional) Set Database Name, Database User Name, and Database Login Password. You can also skip this operation and configure the parameters by referring to Follow-up Operations after the GaussDB instances are successfully managed. Click OK. After the GaussDB instances are successfully managed in the environment, ServiceStage writes the built-in and custom environment variables in the environment by referring to Table 1 for use.
	RocketMQ	Choose Middleware > RocketMQ. Click Manage Resource. Select the RocketMQ instances to be managed. Click Next. (Optional) Set Username and Password. You can also skip this operation and configure the parameters by referring to Follow-up Operations after the RocketMQ instances are successfully managed. Click OK. After the RocketMQ instances are successfully managed in the environment, ServiceStage writes the built-in and custom environment variables in the environment by referring to Table 1 for use.
	CSS	Choose Middleware > CSS. Click Manage Resource. Select the Elasticsearch cluster to be managed. Click Next. (Optional) Set Username and Password. You can also skip this operation and configure the parameters by referring to Follow-up Operations after the Elasticsearch clusters are successfully managed. Click OK. After the Elasticsearch clusters are successfully managed in the environment, ServiceStage writes the built-in and custom environment variables in the environment by referring to Table 1 for use.

Click OK.

After the basic resources are managed, click Overview and select the basic resources (for example, VPC) managed in 4. You can see that Status is Available and Resource Mode is Manage.

Follow-up Operations

You can perform maintenance operations on DCS, RDS, GaussDB, RocketMQ, and CSS instances managed in the environment by referring to the following table.

Resource Type	Maintenance Operation	Description
DCS	Setting the connection password	A password has been set for the managed DCS instances. You need to enter the password. On the Overview page, choose Distributed Cache Service. Click Set Password in the Operation column of the target DCS instance. Click Edit in the Operation column. (Optional) Modify Name. The default value is DISTRIBUTED_CACHE_PASSWORD. You can change the value as required. Enter 1 to 64 characters. Start with a letter, underscore (_), or hyphen (-). Only use letters, digits, underscores (_), hyphens (-), and periods (.). Enter the value of Variable/Variable Reference, that is, the password for accessing the DCS instance. Click Confirm in the Operation column.
DCS	Setting environment variables of an environment	To add an environment variable, see Adding an Environment Variable. To edit an environment variable, see Editing an Environment Variable. To delete an environment variable, see Deleting an Environment Variable.
RDS	Setting the account and password	Set the name, username, and password of the database that can be accessed by the managed RDS instance. On the Overview page, choose Relational Database Service. Click Set Account and Password in the Operation column of the target RDS instance. Set the name of the cloud database to be accessed. Click Edit in the Operation column of the default variable name RELATIONAL_DATABASE_DB_NAME. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column. Set the username for accessing the database in Relational Database Service. Click Edit in the Operation column of the default variable name RELATIONAL_DATABASE_DB_USER. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column. Set the password of the username for accessing the database in Relational Database Service. Click Edit in the Operation column of the default variable name RELATIONAL_DATABASE_PASSWORD. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column.
RDS	Setting environment variables of an environment	To add an environment variable, see Adding an Environment Variable. To edit an environment variable, see Editing an Environment Variable. To delete an environment variable, see Deleting an Environment Variable.
RocketMQ	Setting the account and password	Set the username and password for accessing the managed RocketMQ instance. On the Overview page, choose RocketMQ. Click Set Account and Password in the Operation column of the target RocketMQ instance. Set the username for accessing the database in Relational Database Service. Click Edit in the Operation column of the default variable name DISTRIBUTED_MESSAGE_ROCKETMQ_USER. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column. Set the password of the access user. Click Edit in the Operation column of the default variable name DISTRIBUTED_MESSAGE_ROCKETMQ_PASSWORD. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column.
RocketMQ	Setting environment variables of an environment	To add an environment variable, see Adding an Environment Variable. To edit an environment variable, see Editing an Environment Variable. To delete an environment variable, see Deleting an Environment Variable.
GaussDB	Setting the account and password	Set the name, username, and password of the database that can be accessed by the managed GaussDB instance. On the Overview page, choose GaussDB. Click Set Account and Password in the Operation column of the target RocketMQ instance. Set the name of the cloud database to be accessed. Click Edit in the Operation column of the default variable name PAAS_GAUSSDB_DB_NAME. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column. Set the username for accessing the database in Relational Database Service. Click Edit in the Operation column of the default variable name PAAS_GAUSSDB_DB_USER. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column. Set the password of the username for accessing the database in Relational Database Service. Click Edit in the Operation column of the default variable name PAAS_GAUSSDB_PASSWORD. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column.
GaussDB	Setting environment variables of an environment	To add an environment variable, see Adding an Environment Variable. To edit an environment variable, see Editing an Environment Variable. To delete an environment variable, see Deleting an Environment Variable.
CSS	Setting the account and password	Set the username and password for accessing the managed CSS Elasticsearch cluster. On the Overview page, choose CSS. Click Set Account and Password in the Operation column of the target Elasticsearch cluster. Set the access user name. Click Edit in the Operation column of the default variable name PAAS_ELASTIC_SEARCH_USER. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column. Set the password of the username for accessing the database in Relational Database Service. Click Edit in the Operation column of the default variable name PAAS_ELASTIC_SEARCH_PASSWORD. Modify Name. Enter Variable/Variable Reference. Click Confirm in the Operation column.
CSS	Setting environment variables of an environment	To add an environment variable, see Adding an Environment Variable. To edit an environment variable, see Editing an Environment Variable. To delete an environment variable, see Deleting an Environment Variable.