El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Elastic Cloud Server/ User Guide (Kuala Lumpur Region)/ FAQs/ ECS Management/ Hostnames/ How Can I Set Sequential ECS Names When Creating Multiple ECSs?

How Can I Set Sequential ECS Names When Creating Multiple ECSs?

Updated on 2024-04-19 GMT+08:00

Scenarios

When creating multiple ECSs at the same time, you can use either of the following methods to sequentially name the ECSs:

  • Automatic naming: The system automatically adds a hyphen followed by a four-digit incremental number to the end of each ECS name.
  • Customizable naming: You can customize a naming rule in the format "name_prefix[begin_number,bits]name_suffix". The system will automatically name the ECSs according to naming rule you specify.

This section describes how to use the two methods to name ECSs.

Automatic Naming

You can customize the name according to the following naming rules: The name must contain 1 to 64 characters that can be only letters, digits, underscores (_), and hyphens (-).

  • Example 1: If there is no existing ECS and you enter ecs-f526, the ECSs will be named ecs-f526-0001, ecs-f526-0002, ecs-f526-0003, ....
  • Example 2: If there is an ECS named ecs-f526-0010 and you enter ecs-f526, the ECSs will be named ecs-f526-0011, ecs-f526-0012, ecs-f526-0013, ....
  • Example 3: If there is an ECS named ecs-0010 and you select Allow duplicate ECS name, all the ECSs will be named ecs-0010.

Customizable Naming

You can customize a naming rule in the format "name_prefix[begin_number,bits]name_suffix". The system will automatically name the ECSs according to naming rule you specify.

Field Description for a Customizable Naming Rule

Figure 1 shows the format of a customizable naming rule.

Figure 1 Format of a customizable naming rule

Table 1 describes these parameters.

Table 1 Parameters in a customizable naming rule

Field

Mandatory

Description

Example

name_prefix

Yes

ECS name prefix

The name prefix can contain only letters, digits, underscores (_), and hyphens (-).

ecs

[begin_number,bits]

Yes

Sequence numbers that increase in ascending order to differentiate multiple ECSs.

[0,4]

name_suffix

No

ECS name suffix

The name suffix can contain only letters, digits, underscores (_), and hyphens (-).

f526

Table 2 [begin_number,bits] parameters

Field

Mandatory

Description

Example

begin_number

No

Begin number of ECS names.

The begin number ranges from 0 to 9999. The default value is 0.

0

bits

No

Number of bits for the sequential numbers in ECS names.

The value ranges from 1 to 4. The default value is 4.

4

Notes on Using Customizable Naming
  • Customized names cannot be duplicate.
  • No space is allowed in [begin_number,bits].
  • If the bits of "Begin number + Number of ECSs to be created - 1" is greater than the specified bits, the bits of "Begin number + Number of ECSs to be created - 1" will be used.

    For example, if [begin_number,bits] is set to [8,1] and the number of ECSs to be created is 2, the bits of "Begin number + Number of ECSs to be created - 1" is the same as the specified bits (1). Then, the ECSs will be named name_prefix8name_suffix and name_prefix9name_suffix.

    If [begin_number,bits] is set to [8,1] and the number of ECSs to be created is 3, the specified bits is 1, the bits of "Begin number + Number of ECSs to be created - 1" (value 10, bits 2) is different from the specified bits (1). Therefore, the bits of "Begin number + Number of ECSs to be created - 1" will be used, which is 2.

    The ECSs will be named name_prefix08name_suffix, name_prefix09name_suffix, and name_prefix10name_suffix.

  • If the value of "Begin number + Number of ECSs to be created" is greater than the maximum value 9999, the sequential numbers that exceed 9999 will consistently to be 9999.
  • If [begin_number,bits] is set to [] or [,], the begin number starts from 0, and the number of bits is 4 by default.
  • If [begin_number,bits] is set to [99] or [99,], the begin number starts from 99, and the number of bits is 4 by default.
Customizable Naming Examples
  • Example 1: If you select customizable naming and enter name_prefix[,]name_suffix,

    The ECSs will be named name_prefix0000name_suffix, name_prefix0001name_suffix, name_prefix0002name_suffix, ....

  • Example 2: If you select customizable naming and enter name_prefix[]name_suffix,

    The ECSs will be named name_prefix0000name_suffix, name_prefix0001name_suffix, name_prefix0002name_suffix, ....

  • Example 3: If you select customizable naming and enter name_prefix[9,]name_suffix,

    The ECSs will be named name_prefix0009name_suffix, name_prefix0010name_suffix, name_prefix0011name_suffix, ....

  • Example 4: If you select customizable naming and enter name_prefix[,3]name_suffix,

    The ECSs will be named name_prefix000name_suffix, name_prefix001name_suffix, name_prefix002name_suffix, ....

  • Example 5: If you select customizable naming and enter name_prefix[8]name_suffix,

    The ECSs will be named name_prefix0008name_suffix, name_prefix0009name_suffix, name_prefix0010name_suffix, ....

  • Example 6: If you select customizable naming and enter name_prefix[9999]name_suffix,

    All the ECSs will be named name_prefix9999name_suffix.

  • Example 7: If you select customizable naming and enter name_prefix[8],

    The ECSs will be named name_prefix0008, name_prefix0009, name_prefix0010, ....

Utilizamos cookies para mejorar nuestro sitio y tu experiencia. Al continuar navegando en nuestro sitio, tú aceptas nuestra política de cookies. Descubre más

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback