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
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

Resource Specifications

Updated on 2024-10-29 GMT+08:00

Overview

The bursting add-on can select appropriate resource specifications based on the vCPUs and memory of the workloads to improve resource utilization. This section describes how appropriate resource specifications are selected.

Constraints

  • At least one container in each pod to be scheduled to CCI must have the vCPU limit or request.
  • The operations described in this section for rounding up resources can only be used for cloud native bursting. The CCI 2.0 console and APIs have separate operations for rounding up pod specifications.

How Resource Specifications Are Calculated

The resource specifications of pods scheduled to CCI are calculated based on the requests and limits of container resources and adjusted to the pod specifications allowed by CCI.

The resource specifications of a pod are calculated based on the following rules:

  • Requests and limits of a resource are set to the same value for all app containers and init containers. If a limit is configured, the limit will be applied. If no limit is configured, the request will be applied.
  • If requests are not equal to limits, the larger value of the following two items will be applied:
    • Sum of limits set for a resource on all app containers
    • Maximum resource limit of all init containers

There are some restrictions on pod specifications.

  • The number of vCPUs in a pod must be greater than 0.
  • After automatic resource adjustment, the number of vCPUs for the pod is 48 or 64 or ranges from 0.25 to 32, the memory is an integer multiple of 1 GiB and ranges from 1 GiB to 512 GiB, and the ratio of vCPUs to memory ranges from 1:2 to 1:8.

How Resource Quotas Are Rounded Up

Assume that the vCPUs and memory are calculated based on the pod resource specifications. The resource specifications are rounded up as follows:

  1. The number of vCPUs for each app container and init container (except BestEffort containers) in the pod is increased to an integer multiple of 0.25, and the memory to a value greater than or equal to 0.2 GiB.
    NOTE:

    If the version of the bursting add-on is 1.5.16 or later, container resource specifications will not be rounded up, and only pod resource specifications are rounded up.

  2. The pod resources are continuously adjusted until the number of vCPUs of the pod is greater than 32 or the memory is greater than 256 GiB.
  3. The number of vCPUs in the pod is increased to an integer multiple of 0.25, and the memory to an integer multiple of 1 GiB.
  4. If the ratio of vCPUs to memory of the pod is less than 1:2, the pod memory is increased to a value greater than or equal to twice the number of vCPUs and is an integer multiple of 1 GiB.
  5. If the ratio of vCPUs to memory of the pod is greater than 1:8, the number of vCPUs for the pod is increased to a value greater than or equal to 1/8 of the memory and is an integer multiple of 0.25.
The vCPU and memory increments for rounding up the resource specifications are added to the first non-BestEffort container.
CAUTION:

A BestEffort container is a container that is not configured with requests and limits.

After resource specifications are rounded up, the pod specifications are as follows:

  • The number of vCPUs for the pod ranges from 0.25 to 32 or is 48 or 64, and it must be an integer multiple of 0.25.
  • The pod memory is an integer ranging from 1 GiB to 256 GiB or is 384 GiB or 512 GiB.
  • The ratio of vCPUs to memory is between 1:2 and 1:8.
You can view the specifications rounded up using the annotations of the pods in CCE.
  • virtual-kubelet.cci.io/burst-pod-cpu: 0.5u
  • virtual-kubelet.cci.io/burst-pod-memory: 1Gi

Cases of Rounding Up Resource Specifications

Resource Specifications (vCPUs and Memory)

Specifications Rounded Up (vCPUs and Memory)

Description

37U 37Gi

The workloads cannot be scheduled to CCI.

Invalid vCPU quota.

30U 257Gi

The workloads cannot be scheduled to CCI.

If the ratio of vCPUs to memory is greater than 1:8, the number of vCPUs is increased. However, the vCPU quota cannot be met.

0.35U 0.5Gi

0.5U 1Gi

The number of vCPUs is rounded up to an integer multiple of 0.25, and the memory to an integer multiple of 1. The ratio of vCPUs to memory meets the requirements and does not need to be adjusted.

0.35U 1.5Gi

0.5U 2Gi

The number of vCPUs is rounded up to an integer multiple of 0.25, and the memory to an integer multiple of 1. The ratio of vCPUs to memory meets the requirements and does not need to be adjusted.

0.45U 18Gi

2.25U 18Gi

The number of vCPUs is rounded up to an integer multiple of 0.25, and the memory to an integer multiple of 1. If the ratio of vCPUs to memory is greater than 1:8, the number of vCPUs is increased.

2U 2Gi

2U 4Gi

If the ratio of vCPUs to memory is less than 1:2, the memory is increased.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback