Installation Preparations

This section describes the compatibility of the hardware and software and the related configurations and preparations required for the installation.

Obtaining the Installation Source

Obtain the openEuler release package and verification file before the installation.

Perform the following operations to obtain the openEuler release package:

  1. Visit the openEuler website.
  2. Click Download > Software Packages.
  3. Click Server Image below openEuler 20.03 LTS SP2. The ISO list is displayed.
    • aarch64: ISO image files of the AArch64 architecture
    • x86_64: ISO image files of the x86_64 architecture
    • source: ISO image files of the openEuler source code
  4. Select the target openEuler release package and verification file based on the actual environment.
    • AArch64 architecture:

      1. Click aarch64.
      2. If you install openEuler from a local source, download the release package openEuler-20.03-LTS-SP3-aarch64-dvd.iso and the verification file openEuler-20.03-LTS-SP3-aarch64-dvd.iso.sha256sum to the local host.
      3. If you install openEuler through the network, download the release package openEuler-20.03-LTS-SP3-netinst-aarch64-dvd.iso and the verification file openEuler-20.03-LTS-SP3-netinst-aarch64-dvd.iso.sha256sum to the local host.
    • x86_64 architecture:

      1. Click x86_64.
    1. If you install openEuler from a local source, download the release package openEuler-20.03-LTS-SP3-x86_64-dvd.iso and the verification file openEuler-20.03-LTS-SP3-x86_64-dvd.iso.sha256sum to the local host.
      1. If you install openEuler through the network, download the release package openEuler-20.03-LTS-SP3-netinst-x86_64-dvd.iso and the verification file openEuler-20.03-LTS-SP3-netinst-x86_64-dvd.iso.sha256sum to the local host.

Note:
When the network is available, install the environment on the network because the ISO release package is small. The release package with AArch64 architecture supports UEFI mode, and the one with x86_64 architecture supports UEFI and Legacy modes.

Performing Release Package Integrity Check

NOTE:
This section describes how to verify the integrity of the release package in the AArch64 architecture. The procedure for verifying the integrity of the release package in the x86_64 architecture is the same.

Introduction

To prevent the software package from being incompletely downloaded due to network or storage device faults during transmission, you need to verify its integrity after obtaining it. Only the software packages that pass the verification can be installed.

Compare the verification value recorded in the verification file with the .iso file verification value calculated manually to check whether the software package passes the verification. If the verification values are consistent, the .iso file is not damaged. If not, the file is damaged and you need to obtain the release package again.

Prerequisites

Before verifying the integrity of the release package, prepare the following files:

ISO file: openEuler-20.03-LTS-SP3-aarch64-dvd.iso

Verification file: openEuler-20.03-LTS-SP3-aarch64-dvd.iso.sha256sum

Procedure

To verify the file integrity, perform the following operations:

  1. Obtain the verification value in the verification file. Run the following command:

    $ cat openEuler-20.03-LTS-SP3-aarch64-dvd.iso.sha256sum 
    
  2. Calculate the SHA256 verification value of the file. Run the following command:

    $ sha256sum openEuler-20.03-LTS-SP3-aarch64-dvd.iso
    

    After the command is run, the verification value is displayed.

  3. Check whether the values obtained from step 1 and step 2 are consistent.

    If the verification values are consistent, the .iso file is not damaged. If not, the file is damaged and you need to obtain the release package again.

Installation Requirements for PMs

To install the openEuler OS on a PM, the PM must meet the following hardware compatibility and minimum hardware requirements.

Hardware Compatibility

You need to take hardware compatibility into account during openEuler installation. Table 1 describes the types of supported servers.

NOTE:

  • TaiShan 200 servers are backed by Huawei Kunpeng 920 processors.
  • Currently, only Huawei TaiShan and FusionServer Pro servers are supported. More servers from other vendors will be supported in the future.

Table 1 Supported servers

Server TypeServer NameServer Model
Rack serverTaiShan 2002280 balanced model
Rack serverFusionServer ProFusionServer Pro 2288H V5
NOTE:
The server must be configured with the Avago 3508 RAID controller card and the LOM-X722 NIC.

Minimum Hardware Specifications

Table 2 lists the minimum hardware specifications supported by openEuler.

Table 2 Minimum hardware specifications

ComponentMinimum Hardware Specifications
ArchitectureAArch64 or x86_64
CPUTwo CPUs
Memory≥ 4 GB (8 GB or higher recommended for better user experience)
Hard disk≥ 32 GB (120 GB or higher recommended for better user experience)

Installation Requirements for VMs

To install the openEuler OS on a VM, the VM must meet the following hardware compatibility and minimum hardware requirements.

Virtualization Platform Compatibility

When installing openEuler, pay attention to the compatibility of the virtualization platform. Currently, the following virtualization platforms are supported:

  • A virtualization platform created by the openEuler virtualization components (openEuler is used as the host OS, and the virtualization components are QEMU and KVM provided in the release package)
  • x86 virtualization platform of Huawei public cloud

Minimum Virtualization Space

Table 3 lists the minimum virtualization space required by openEuler.

Table 3 Minimum virtualization space

ComponentMinimum Virtualization Space
ArchitectureAArch64 or x86_64
CPUTwo CPUs
Memory≥ 4 GB (8 GB or higher recommended for better user experience)
Hard disk≥ 32 GB (120 GB or higher recommended for better user experience)

Bug Catching

Buggy Content

Bug Description

Submit As Issue

It's a little complicated....

I'd like to ask someone.

PR

Just a small problem.

I can fix it online!

Bug Type
Specifications and Common Mistakes

● Misspellings or punctuation mistakes;

● Incorrect links, empty cells, or wrong formats;

● Chinese characters in English context;

● Minor inconsistencies between the UI and descriptions;

● Low writing fluency that does not affect understanding;

● Incorrect version numbers, including software package names and version numbers on the UI.

Usability

● Incorrect or missing key steps;

● Missing prerequisites or precautions;

● Ambiguous figures, tables, or texts;

● Unclear logic, such as missing classifications, items, and steps.

Correctness

● Technical principles, function descriptions, or specifications inconsistent with those of the software;

● Incorrect schematic or architecture diagrams;

● Incorrect commands or command parameters;

● Incorrect code;

● Commands inconsistent with the functions;

● Wrong screenshots.

Risk Warnings

● Lack of risk warnings for operations that may damage the system or important data.

Content Compliance

● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

● Copyright infringement.

How satisfied are you with this document

Not satisfied at all
Very satisfied
Submit
Click to create an issue. An issue template will be automatically generated based on your feedback.