检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Solution Log in to the ECS console and click Elastic Cloud Server. In the ECS list, search the ECS IDs in the error information to find the ECSs where the components are deployed. Check whether each of their status is Running. If yes, go to 2 and search for the next ECS.
What Should I Do If an ECS Error Occurs When I Create and Deploy a Component on a VM? Symptom The ECS service may be unavailable when you create and deploy a component on a ServiceStage VM.
Getting Started Quick Experience Developing and Deploying a ServiceComb Java Microservice Developing and Deploying a Go Microservice Quick Config Select a Configuration Quickly Purchase an ECS Reset the ECS Password and Log In to the ECS Custom Config Configure Basic Settings Configure
ServiceStage billing does not include computing resources (Cloud Container Engine (CCE) and Elastic Cloud Server (ECS)), network resources (Elastic Load Balance (ELB) and Elastic Public Network EIP)), middleware (Cloud Service Engine (CSE), Distributed Cache Service (DCS), and Cloud
Choose Elastic Cloud Server and click the ECS whose VM agent is offline. In the Management Information area of the Basic Information tab page, view the IAM agency bound to the ECS. Log in to the Identity and Access Management (IAM) console.
Solution Log in to the ECS console and click Elastic Cloud Server. In the ECS list, find the target ECS for deploying the component and click it to open its details page.
Choose Elastic Cloud Server and click the ECS whose VM agent is offline. In the Management Information area of the Basic Information tab page, view the IAM agency bound to the ECS. Log in to the Identity and Access Management (IAM) console.
Deploying a Microservice Using a Software Package Scenarios ServiceStage allows you to quickly deploy microservices in containers (such as CCE) or VMs (such as ECS), and supports source code deployment, JAR/WAR package deployment, and Docker image package deployment.
Deploying a Microservice Using Source Code Scenarios ServiceStage allows you to quickly deploy microservices in containers (such as CCE) or VMs (such as ECS), and supports source code deployment, JAR/WAR package deployment, and Docker image package deployment.
Upgrading The VM agent has been installed on the ECS node and is being upgraded. Upgrade failed The VM agent has been installed on the ECS node and fails to be upgraded. Agent restarting The VM agent has been installed on the ECS node and is restarting.
Glossary Environment An environment is a collection of basic compute (such as CCE and ECS), network (such as ELB and EIP), and middleware (such as DCS and RDS) resources, used for component deployment and running.
Manually Synchronizing the Component Status ServiceStage periodically syncs the number and status of component instances from compute resources (CCE and ECS) that run component instances.
Each cluster must contain at least one ECS node with 8 vCPUs and 16 GB memory or two ECS nodes with 4 vCPUs and 8 GB memory. For details about how to add a node to the CCE cluster, see Creating a Node. The VPC to which the cluster belongs is the one created in 1.
If Type is set to Scale out, click Add ECS and create an ECS to run new component instances. For details, see Purchasing a Custom ECS. If Type is set to Scale in, the number of running component instances can be reduced to 1. Click OK.
Creating and Managing an Environment Scenarios An environment is a collection of basic compute (such as CCE and ECS), network (such as ELB and EIP), and middleware (such as DCS and RDS) resources, used for component deployment and running.
Table 6 schemas Parameter Type Description id String Resource ID. name String Resource name. type String Resource type. eip elb cce ecs as cse dcs rds Example Request Modify the ECS whose ID is 67835bb3-1235-4cc9-be71-becbb2b4ca0d and name is ecs-a5a9. { "resources": [
Creating an Environment Function An environment is a collection of basic compute (such as CCE and ECS), network (such as ELB and EIP), and middleware (such as DCS and RDS) resources, used for component deployment and running.
Table 4 schemas Parameter Type Description id String Resource ID. name String Resource name. type String Resource type. eip elb cce ecs dcs rds cse: ServiceComb engine nacos: registry/configuration center ms_gateway: application gateway subnet acl Example Request None Example Response
An environment is a collection of basic compute (such as CCE and ECS), network (such as ELB and EIP), and middleware (such as DCS and RDS) resources, used for component deployment and running.
Example Request Add ECS basic resource ecs-9876 and CSE optional resource Cloud Service Engine, and remove ECS resource test. { "add_base_resources": [ { "id": "ed2f3420-7031-4d93-b92b-e360cd4acf9e", "type": "ecs", "name": "ecs-9876" } ], "add_optional_resources":