Creating a ServiceComb Engine

Prerequisites

• A ServiceComb engine runs on a VPC. Before creating a ServiceComb engine, ensure that VPCs and subnets are available.

  You have created a VPC. For details, see Creating a VPC.

• The login account has the permission to create a ServiceComb engine. For details about how to authorize and bind account permissions, see Creating a User and Granting Permissions.

Procedure

1. Go to the Buy Exclusive ServiceComb Engine page.
2. Set parameters according to the following table. Parameters marked with an asterisk (*) are mandatory.

   Parameter	Description
   * Billing Mode	Billing mode. Currently, pay-per-use is supported.
   *Enterprise Project	Project where the microservice engine locates. You can search for and select an enterprise project in the drop-down list.
   *Instances	Specifications of the microservice engine.
   *Engine Type	Microservice engine type. If the engine type is cluster, the engine is deployed in cluster mode and supports host-level DR.
   *Name	Enter a ServiceComb engine name, for example, cse-lhy-nodelete.
   *AZ	Select an available zone (AZ).
   *Network	Select the created VPC and subnet. You can search for and select a VPC and subnet from the drop-down list.
   Description	Click and enter the engine description, for example, create a microservice engine.
   Tags	Tags are used to identify cloud resources. When you have multiple cloud resources of the same type, you can use tags to classify them based on usage, owner, or environment. Click Add Tag. In the Add Tag dialog box, enter a tag key and value. For details about tag naming rules, see Managing Tags. In the Add Tag dialog box, you can click Add Tag to add multiple tags at a time, or click next to a tag to delete the tag.
   *Security Authentication	The exclusive ServiceComb engine with security authentication enabled provides the system management function using the role-based access control (RBAC) through the microservice engine console. Select Enable security authentication: Determine whether to enable Authenticate Programming Interface. After it is enabled, you need to add the corresponding account and password to the microservice configuration file. Otherwise, the service cannot be registered with the engine. After it is disabled, you can register the service with the engine without configuring the account and password in the microservice configuration file, which improves the efficiency. You are advised to disable this function when accessing the service in a VPC. Enter and confirm the password of user root. Keep the password secure. Select Disable security authentication: Disable security authentication. You can enable it after the instance is created.

3. Click Buy. The page for confirming the engine information is displayed.
4. Click Submit and wait until the engine is created.
   

   • It takes about 31 minutes to create an engine.
   • After the microservice engine is created, its status is Available. For details about how to view the microservice engine status, see Viewing ServiceComb Engine Information.
   • If the microservice engine fails to be created, view the failure cause on the Operation page and rectify the fault. Then, you can perform the following operations:
     • In the Microservice Engine Information area, click Retry to create a microservice engine again.
     • If the retry fails, delete the microservice engine that fails to be created. For details, see Deleting an Exclusive ServiceComb Engine.