Creating a Microservice Engine

Prerequisites

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

  For details about how to create a VPC and subnet, see Creating a VPC.

  For details about how to add a security group rule, see Adding a Security Group Rule.

  Table 1 cse-engine-default-sg rules

  Direction	Priority	Policy	Protocol and Port	Type	Source Address
  Inbound	1	Allow	ICMP: all	IPv6	::/0
  	1	Allow	TCP: 30100–30130	IPv6	::/0
  	1	Allow	All	IPv6	cse-engine-default-sg
  	1	Allow	TCP: 30100–30130	IPv4	0.0.0.0/0
  	1	Allow	ICMP: all	IPv4	0.0.0.0/0
  Outbound	100	Allow	All	IPv4	0.0.0.0/0
  	100	Allow	All	IPv6	::/0

Procedure

1. Log in to ServiceStage and choose Cloud Service Engine > Engines.
2. Click Create Microservice Engine.
3. 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	Enterprise project where the microservice engine locates. Enterprise projects let you manage cloud resources and users by project. It is available after you create an enterprise project. NOTE: The enterprise project cannot be changed once the microservice engine is created.
   *Specification	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	Name of the microservice engine. The name cannot be changed once the microservice 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 AZ of a created microservice engine cannot be changed. The AZs in one region can communicate with each other over an intranet. Multiple AZs enhance DR capabilities.
   *Network	You can select a created VPC and its subnets to provision logically isolated, configurable, and manageable virtual networks for your engine.
   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 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.

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

   • It takes about 31 minutes to create a microservice 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 a microservice engine again.
     • If the retry fails, delete the microservice engine that fails to be created. For details, see Deleting a Microservice Engine.