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

Method 2: Deploying an HPC Cluster

Updated on 2023-10-16 GMT+08:00

Scenarios

If you want to use existing cloud servers to deploy an HPC cluster, perform operations in this section.

NOTICE:

Select a master node and then compute nodes. These nodes must have the same CPU architecture and OS version and in the same VPC and security groups.

Notes

  • When you use VPC for the first time, the system automatically creates a VPC for you, including a default security group and NIC. You can also create a VPC by yourself. For more information about VPC, see Virtual Private Cloud User Guide.
  • You can use the default security group provided by the system or create a security group by yourself.

    To allow secure access to cloud servers in the cluster, ensure that port 22 in the security group rule is open. For details, see Adding a Security Group Rule.

  • Scalable File Service (SFS) is used for shared file access spanning cloud servers. For more information about SFS, see Scalable File Service User Guide.

Procedure

  1. Log in to the HPC-S² console.
  2. Click in the upper left corner and select your region and project.
  3. Click Deploy HPC Cluster.

    The Deploy HPC Cluster page is displayed.

  4. Select a region.

    Cloud servers in different regions cannot communicate with each other over an intranet. For low network latency and quick resource access, select the nearest region.

  5. Set a cluster name.

    The name must comply with the naming rules in the following table.

    Table 1 Cluster naming rules

    Item

    Requirements

    Example Value

    Cluster name

    • Consists of 1 to 52 characters.
    • Contains only letters, digits, hyphens (-), and periods (.).
    • Cannot start or end with a hyphen (-) or period (.).
    • Cannot contain consecutive hyphens (-) and periods (.) or the combination of them, for example, --, .., -., or .-.

    hpc-001.p1

  6. Select a cloud server as the master node.

    The master node must:

    • Be in the region selected in 2.
    • Be in the Running state.
    • Have an EIP bound.
    • Not be included in other clusters under the current account.
  7. Select security groups.

    A security group controls the access to the cloud servers added to this group by defining access rules. You can select multiple security groups.

  8. Select compute nodes.

    The compute nodes must:

    • Be in the region selected in 2.
    • Be in the Running state.
    • Use the same CPU architecture as the master node.
    • Be in the same VPC and security groups as the master node.
    • Use the same major OS version as the master node.
    • Be no more than 50 in quantity.
  9. Select a VPC.

    This parameter is automatically set to the VPC of the master node.

  10. Set the login mode.

    Only Password is available. If any of the selected cloud servers is using key pair authentication, go to the corresponding service console to change it to password authentication. In addition, set a strong password to protect yourself from malicious attacks.

    The initial password of user root will be used for authenticating Linux login, while that of user Administrator will be used for authenticating Windows login. The password must meet the following requirements.

    Table 2 Password complexity requirements

    Item

    Requirements

    Example Value

    Password

    • Consists of 8 to 26 characters.
    • Contains at least three of the following character types:
      • Uppercase letters
      • Lowercase letters
      • Digits
      • Special characters: $!@%-_=+[]:./^,{}?
    • Cannot contain the username or the username spelled backwards.
    • Cannot contain more than two characters in the same sequence as they appear in the username. (This requirement applies only to Windows cloud servers.)

    YNbUwp!dUc9MClnv

    NOTE:

    The example password is generated randomly. Do not copy it for use.

  11. Select a file system.

    Available file systems are filtered and displayed in the drop-down list based on the network settings. If no files systems are available, you can create one and add it to the VPC specified in 9. For details, see Create a File System.

  12. Select a scheduler.

    Currently, only the slurm and sge schedulers are available. The default one is slurm.

  13. Confirm the configurations and click Deploy HPC Cluster.
  14. After the order is submitted, the system returns back to the Clusters page, where you can see that the cluster is in the Deploying state. Wait until the cluster status changes to Running which indicates that the cluster is successfully deployed.

Follow-up Operations

View the cluster details, nodes, and shared storage, as instructed in Viewing HPC Clusters.

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