HuaKun Kunpeng/ARM: a migration plan for enterprise applications
A practical guide to ARM compatibility, pilot selection and staged migration, from application binaries to recovery tests.
ExploreIT & TELECOM / SOFCON AZERBAIJAN
HuaKun AI and infrastructure platforms
AI application development with TGDataXAI, infrastructure management with TGHCI and distributed storage with HKStor. SOFCONS connects these software layers to your server, data and application requirements.
Prepare an enquiry
SOFCON AZERBAIJANRequirements / solution / delivery
Models and platforms
| Model | Applications | Key features |
|---|---|---|
| TGDataXAI / HuaKun YuanqiManufacturer details ↗ | AI application and development platform for visual workflows and private knowledge bases. |
|
| TGHCIManufacturer details ↗ | Unified management of heterogeneous resources and virtualization. |
|
| HKStorManufacturer details ↗ | Parallel and distributed storage layer for HPC and AI data. |
|
Selection guides
HuaKun AI infrastructure: workstation, server or cluster?
Choose between local inference, PCIe accelerators, modular platforms and clusters using memory, software fit, concurrency and a pilot.
ExploreIT & Telecom01 02 03
From requirements to delivery
Application and knowledge layer
TGDataXAI addresses visual AI workflows, agents, model management and private knowledge applications. The design defines knowledge sources, access permissions and answer evaluation. Embedding/Rerank model selection and import requirements are agreed for the intended version.
Resource management
TGHCI covers x86/ARM infrastructure management, virtualization and CPU/GPU/NPU resource scheduling. Managing mixed architectures does not make application binaries portable between them. Operating-system, driver and runtime compatibility are validated separately.
Data layer
HKStor addresses parallel and distributed HPC/AI storage with hot and cold data tiering. Capacity, protocols, data flows and protection policy are sized for the project; hardware nodes and software platform have separate specifications.
Start with a brief that defines software layers and integration boundaries.