Node Flavor Description
Different regions support different node flavors, and node flavors may be changed or sold out. You are advised to log in to the CCE console and check whether the required node flavors are supported on the page for creating nodes.
You are not advised to use 2 vCPUs and 4 GiB of memory or a smaller flavor for a node in a CCE clusters because system components occupy certain resources. If the flavor is too small, pods with large specifications may fail to be scheduled to that node, and the remaining resources cannot be effectively used. As a result, the overall resource utilization is low. You are advised to obtain the node flavors on the console. For details about node flavors, see A Summary List of x86 ECS Specifications.
You need to enter the specific flavor name, for example, c6.xlarge.2.
The tables below list the flavors supported by CCE. (The flavors of some ECS models vary by region. The actual flavors displayed on the console are used.)
- CCE standard cluster
- ECS (VM)
Node Type
Node Specification Type
Flavor Name
x86 node
General computing-plus
ac9s, ac9, c9, ac8, ac7, c7, c7e, c7n, c7t, c7h, c6s, ac6, c6, c6nl, c6x, c3, and c3ne
General computing
s7, s7n, as7, s6, s6nl, s3, and s2
General computing-basic
t6
Memory-optimized
am9, m9, am8, m7s, m7, m7n, m6, m6s, m6nl, m3, m2, am7, and m3ne
Large-memory
e7, e6, and e3
Disk-intensive
d7, d6, d6nl, d2, and d3
Ultra-high I/O
i9, d9i, d7i, ai7, i7, i7n, i3, ir7, ir7n, and ir3
High-performance computing
h3 and hc2
GPU-accelerated
pi2 and pi1
p2s, p2v, p2vs, and p1
g6, g5, and g6v
AI-accelerated
ai2, ai1s, and ai1
FlexusX
x2, x2e, x1, and x1e
Kunpeng (Arm) node
Kunpeng general computing-plus
kc1, kc1n, and kc2
Kunpeng memory-optimized
km1, km1s, and km2
Kunpeng ultra-high I/O
ki2 and ki1
AI-accelerated
kai1s and kai1
- ECS (physical server): c6 and c7 are supported.
Node Type
Flavor Name
General computing-plus
c6.22xlarge.2.physical
c6.22xlarge.2.physical.129nic
c6.22xlarge.4.physical
c6.22xlarge.4.physical.129nic
- BMS:
x86 nodes: BMSs of the physical.d2, physical.s4, physical.c6ne, and physical.d6ne types are supported.
Arm nodes: BMS of the physical.a1.2xlarge type is supported.
- ECS (VM)
- CCE Turbo cluster
- ECS (VM)
Node Type
Flavor Type
Flavor Name
x86 node
General computing-plus
ac9s, ac9, c9, ac8, ac7, c7, c7n, c7e, c7t, ac6, c6ne, c6sne, and c3n
General computing
s7n, s7, as7, and s6ne
Memory-optimized
am9, m9, am8, m7s, m7, m7n, m3n, m6s, m6ne, m6sne, and am7
Large-memory
e7
Disk-intensive
d7
Ultra-high I/O
i9, d9i, d7i, ai7, i7, i7n, i3ne, ir7, and ir7n
GPU-accelerated
pi2ne
FlexusX
x2, x2e, x1, and x1e
Kunpeng (Arm) node
Kunpeng general computing-plus
kc1n and kc2
Kunpeng memory-optimized
km1n and km2
- ECS (physical server): c6 and c7 are supported.
Node Type
Flavor Name
General computing-plus
c6.22xlarge.2.physical
c6.22xlarge.2.physical.129nic
c6.22xlarge.4.physical
c6.22xlarge.4.physical.129nic
- ECS (VM)
The available specifications of IPv6 dual-stack nodes vary with regions. For details, see Constraints.
What is your overall rating for this page?
Thank 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