- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Before You Start
- Permissions Management
-
Exclusive ServiceComb Engine
- Creating a ServiceComb Engine
-
Managing ServiceComb Engines
- Viewing ServiceComb Engine Information
- Obtaining the Service Center Address of a ServiceComb Engine
- Obtaining the Configuration Center Address of a ServiceComb Engine
- Viewing the Instance Quota of a ServiceComb Engine
- Viewing the Configuration Item Quota of a ServiceComb Engine
- Configuring Backup and Restoration of a ServiceComb Engine
- Managing Public Network Access for a ServiceComb Engine
- Viewing ServiceComb Engine Operation Logs
- Upgrading a ServiceComb Engine Version
- Deleting a ServiceComb Engine
- Changing ServiceComb Engine Specifications
- Managing Security Authentication for a ServiceComb Engine
- Managing Tags
- Using ServiceComb Engines
- Registry/Configuration Center
- Key Operations Recorded by CTS
-
Best Practices
- CSE Best Practices
-
ServiceComb Engines
-
ServiceComb Engine Application Hosting
- Hosting Spring Cloud Applications Using Spring Cloud Huawei SDK
- Hosting a Java Chassis Application
-
ServiceComb Engine Application Hosting
- Registry/Configuration Centers
-
Developer Guide
- Overview
- Developing Microservice Applications
- Preparing the Environment
- Connecting Microservice Applications
- Deploying Microservice Applications
- Using ServiceComb Engine Functions
- Appendix
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Examples
-
CSE API
- API Calling
- Dynamic Configuration
-
Engine Management
- Querying the Flavor List of a Microservice Engine
- Querying the Microservice Engine List
- Creating a Microservice Engine
- Querying Microservice Engine Details
- Querying Details About a Microservice Engine Job
- Querying Details About the Microservice Engine Quota
- Deleting a Microservice Engine
- Upgrading a Microservice Engine
- Updating Microservice Engine Configurations
- Changing Microservice Engine Specifications
- Retrying an Exclusive ServiceComb Engine Job
- Updating Microservice Engine Details
- Querying the Engine Job List
- Querying an RBAC Token
-
Microservice Governance
- Querying the Governance Policy List
- Creating a Dark Launch Policy
- Querying a Dark Launch Policy
- Deleting a Dark Launch Policy
- Changing a Governance Policy
- Deleting a Governance Policy
- Querying Governance Policy Details
- Creating a Governance Policy
- Querying the Governance Policy List of a Specified Kind
- Querying Microservice Thresholds in Batches
- Querying Microservice Reporting Information
- Querying the Reported Information List
- Nacos API
-
ServiceComb API
- API Calling
- Authentication
-
Microservice
- Querying Information About a Microservice
- Deleting Definition Information About a Microservice
- Querying Information About All Microservices
- Creating Static Information for a Microservice
- Deleting Static Information About Microservices in Batches
- Modifying Extended Attributes of a Microservice
- Querying the Unique Service or Schema ID of a Microservice
- Schema
-
Microservice Instance
- Registering a Microservice Instance
- Querying a Microservice Instance Based on service_id
- Deregistering a Microservice Instance
- Querying Details About a Microservice Instance
- Modifying the Extended Information About a Microservice Instance
- Modifying Status of a Microservice Instance
- Sending Heartbeat Information
- Querying a Microservice Instance by Filter Criteria
- Querying Microservice Instances in Batches
- Dependency
- Configuration Management
- Appendixes
- Change History
- SDK Reference
-
FAQs
- Precautions When Using Huawei Cloud CSE
- Nacos Engines
-
ServiceComb Engines
- How Do I Perform Local Development and Testing?
- How Can I Handle a Certificate Loading Error?
- What If the Header Name Is Invalid?
- What Is the Performance Loss of Mesher?
- Why Is "Version validate failed" Displayed When I Attempt to Connect to the Service Center?
- Why Is "Not enough quota" Displayed When I Attempt to Connect to the Service Center?
- What Should I Do If the Service Registration Fails After IPv6 Is Enabled for the Exclusive ServiceComb Engine with Security Authentication Enabled?
- What Is Service Name Duplication Check?
- Why Do I Have to Define Service Contracts?
- Why Are Microservice Development Framework and Netty Versions Unmatched?
- What Do I Need to Know Before Upgrading an Exclusive ServiceComb Engine?
- What Must I Check Before Migrating Services from the Professional to the Exclusive Microservice Engine?
- Why Is "Duplicate cluster name" Displayed?
- Error Message "the subnet could not be found" Is Displayed When the Access Address Fails to Be Processed During Engine Creation
- Why Is Error "does not match rule: {Max: 100, Regexp: ^[a-zA-Z0-9]{1,160}$|^[a-zA-Z0-9][a-zA-Z0-9_\-.]{0,158}[a-zA-Z0-9]$}"}" Reported?
- What Should I Do If SpringCloud Applications Fail to Connect to the Configuration Center of ServiceComb Engine 2.x?
- Why Could My the Global Configuration Not Be Modified?
- Obtain Configurations Failed
- Videos
- General Reference
Copied.
Creating a Registry/Configuration Center
This section describes how to create an engine whose registry/configuration center is Nacos.
Nacos engines are supported only in CN East 2, CN-Hong Kong, AP-Singapore, ME-Riyadh, and LA-Mexico City2.
Prerequisites
- A Nacos engine runs on a VPC. Before creating a Nacos engine, ensure that VPCs and subnets are available. For details about how to create a VPC and subnet, see Creating a VPC.
- The user has the CSE FullAccess and DNS Full Access permissions.
Creating a Registry/Configuration Center
- Go to Buy Registry/Configuration Center Instance.
- 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 Nacos engine locates. You can search for and select an enterprise project in 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.
*Name
Name of a Nacos engine. The name contains 3 to 64 characters, including letters, digits, and hyphens (-), and starts with a letter but cannot end with a hyphen.
NOTICE:Nacos engine name cannot be default.
*Registry/Configuration Center Instance
Select Nacos.
NOTE:
Cluster nodes in the registry/configuration center are evenly distributed to different AZs. A failure of a single node does not affect external services. The registry/configuration center does not support AZ-level DR but provides host-level DR.
*Instances
Select the required capacity specifications.
NOTE:
To create a Nacos engine with more than 2,000 microservice instances, submit a service ticket.
Version
Only the latest version can be created.
*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 console to go to the Virtual Private Cloud page and create one. For details, see Creating a VPC.
NOTE:
- You cannot use a shared VPC to create a Nacos engine. Otherwise, the engine fails to be created.
- The VPC cannot be changed once the Nacos engine is created.
Tag
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.
- Click Buy. The page for confirming the engine information is displayed.
- Click Submit. When the status becomes Available, the engine is created.
NOTE:
- After the Nacos engine is created, its status is Available. For details about how to view the Nacos engine status, see Viewing Nacos Engine Information.
- You may fail in buying an engine for insufficient underlying resources. To prevent this, delete engines in time so that you will not be charged if your engines restore upon sufficient underlying resources.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot