Creating a Microservice Engine

Restrictions

• When a microservice engine is in use, do not disable the enterprise project. Otherwise, the engine will not be displayed in the engine list, affecting normal use.
• The specification cannot be changed once the microservice engine is created.
• The AZ of a created microservice engine cannot be changed.
• The VPC cannot be changed once the engine is created.

Prerequisites

A microservice engine runs on a VPC. Before creating a microservice engine, ensure that a VPC and subnet are available.

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

If the engine is created using an account with the minimum permission for creating engines, for example, cse:engine:create in the fine-grained permission dependencies of microservice engines, the default VPC security group cse-engine-default-sg needs to be preset by the primary account and the rules listed in Table 1 need to be added.

Creating a Microservice Engine

1. Go to the Buy Exclusive Microservice Engine page.
   

   • By default, a maximum of five exclusive microservice engines can be created for each project. To create more exclusive microservice engines, submit a service ticket to increase the quota. For details, see Creating a Service Ticket.
   • For details about projects, see Projects.

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	Select the project where the microservice engine is located. You can search for and select the required enterprise project from the drop-down list. Enterprise projects let you manage cloud resources and users by project. An enterprise project can be used after it is created and enabled. For details, see Enabling the Enterprise Project Function. By default, default is selected. After a microservice engine is created, you can remove microservice engine resources out of the current enterprise project and into a new enterprise project. For details, see Removing Resources from an Enterprise Project and Adding Resources to an Enterprise Project.
   *Specification	Select the microservice instance quota.
   *Engine Type	Microservice engine type. If the engine type is cluster, the engine is deployed in cluster mode and supports host-level DR.
   *Name	Name of a microservice engine. The name contains 3 to 24 characters, including letters, digits, and hyphens (-), and starts with a letter but cannot end with a hyphen. The name cannot be default and cannot be changed once the engine is created.
   *AZ	Availability zone. Select one or three AZs for the engine based on the number of AZs in the environment. Select one AZ to provide host-level DR. Select three AZs to provide AZ-level DR. NOTE: The AZs in one region can communicate with each other over an intranet. Multiple AZs enhance DR capabilities.
   *Network	Select a VPC and subnet to provision logically isolated, configurable, and manageable virtual networks for your engine. To use a created VPC, search for and select a VPC created under the current account from the drop-down list. To use a new VPC, click Create VPC in the drop-down list. For details, see Creating a VPC.
   Description	Click and enter the engine description.
   Authentication Mode	The exclusive microservice 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 10–30 minutes to create a ServiceComb engine.
   • After the microservice engine is created, its status is Available. For details about how to view the microservice engine status, see Viewing Microservice 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 an engine again.
     • If the retry fails, delete the microservice engine that fails to be created. For details, see Deleting an Exclusive Microservice Engine.