LTS

    Innovation Version

      Quick Start

      This document uses openEuler 22.03 LTS SP2 installed on the TaiShan 200 server as an example to describe how to quickly install and use openEuler OS. For details about the installation requirements and methods, see the Installation Guide.

      Making Preparations

      • Hardware Compatibility

        Table 1 describes the types of supported servers.

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

        ComponentMinimum Hardware SpecificationsDescription
        Architecture
        • AArch64
        • x86_64
        • 64-bit Arm architecture
        • 64-bit Intel x86 architecture
        CPU
        • Huawei Kunpeng 920 series
        • Intel ® Xeon® processor
        -
        Memory≥ 4 GB (8 GB or higher recommended for better user experience)-
        Drive≥ 120 GB (for better user experience)
        • IDE, SATA, and SAS drives are supported.
        • A driver software is required to use the NVMe drive with the DIF feature. Contact the drive manufacturer if the feature is not available.

      Obtaining the Installation Source

      Perform the following operations to obtain the openEuler release package:

      1. Visit the openEuler website.
      2. Click Downloads.
      3. Click Community Editions. The version list is displayed.
      4. Click Download on the right of openEuler 22.03-LTS-SP2.
      5. Download the required openEuler release package and the corresponding verification file based on the architecture and scenario.
        1. If the architecture is AArch64:
          1. Click AArch64.
          2. For local installation, download the Offline Standard ISO or Offline Everything ISO release package openEuler-22.03-LTS-SP2-(everything-)aarch64-dvd.iso to the local host.
          3. For network installation, download the Network Install ISO release package openEuler-22.03-LTS-SP2-netinst-aarch64-dvd.iso to the local host.
        2. If the architecture is x86_64:
          1. Click x86_64.
          2. For local installation, download the Offline Standard ISO or Offline Everything ISO release package openEuler-22.03-LTS-SP2-(everything-)x86_64-dvd.iso to the local host.
          3. For network installation, download the Network Install ISO release package openEuler-22.03-LTS-SP2-netinst-x86_64-dvd.iso to the local host.

      Checking the Release Package Integrity

      To prevent incomplete download of the software package due to network or storage device problems during the transmission, you need to check the integrity of the obtained openEuler software package.

      Prerequisites

      The following files need to be prepared:

      ISO file: openEuler-22.03-LTS-SP2-aarch64-dvd.iso

      Verification file: Copy and save the SHA256 value corresponding to the ISO file.

      Verification Procedure

      1. Calculate the SHA256 verification value of the file. Run the following command:

        sha256sum openEuler-22.03-LTS-SP2-aarch64-dvd.iso
        

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

      2. Check whether the verification value is the same as that in the local verification file.

        If the verification values are the same, the .iso file is not damaged. If they are not the same, the file is damaged and you need to obtain the file again.

      Starting Installation

      1. Log in to the iBMC WebUI.

        For details, see TaiShan 200 Server User Guide (Model 2280).

      2. Choose Configuration from the main menu, and select Boot Device from the navigation tree. The Boot Device page is displayed.

        Set Effective and Boot Medium to One-time and DVD-ROM, respectively, and click Save, as shown in Figure 1.

        Figure 1 Setting the boot device

      3. Choose Remote Console from the main menu. The Remote Console page is displayed.

        Select an integrated remote console as required to access the remote virtual console, for example, Java Integrated Remote Console (Shared).

      4. On the toolbar, click the icon shown in the following figure.

        Figure 2 Drive icon

        An image dialog box is displayed, as shown in the following figure.

        Figure 3 Image dialog box

      5. Select Image File and then click Browse. The Open dialog box is displayed.

      6. Select the image file and click Open. In the image dialog box, click Connect. If Connect changes to Disconnect, the virtual CD/DVD-ROM drive is connected to the server.

      7. On the toolbar, click the restart icon shown in the following figure to restart the device.

        Figure 4 Restart icon

      8. A boot menu is displayed after the system restarts, as shown in Figure 5.

        NOTE:

        • If you do not perform any operations within 1 minute, the system automatically selects the default option Test this media & install openEuler 22.03_LTS_SP2 and enters the installation page.
        • During physical machine installation, if you cannot use the arrow keys to select boot options and the system does not respond after you press Enter, click on the BMC page and configure Key & Mouse Reset.

        Figure 5 Installation wizard

      9. On the installation wizard page, press Enter to select the default option Test this media & install openEuler 22.03_LTS_SP2 to enter the GUI installation page.

      Performing Installation

      After entering the GUI installation page, perform the following operations to install the system:

      1. Set an installation language. The default language is English. You can change the language based on the site requirements, as shown in Figure 6.

        Figure 6 Selecting a language

      2. On the INSTALLATION SUMMARY page, set configuration items based on the site requirements.

        • A configuration item with an alarm symbol must be configured. When the alarm symbol disappears, you can perform the next operation.
        • A configuration item without an alarm symbol is configured by default.
        • You can click Begin Installation to install the system only when all alarms are cleared.

        Figure 7 Installation summary

        1. Select Software Selection to set configuration items.

          Based on the site requirements, select Minimal Install on the left box and select an add-on in the Add-Ons for Selected Environment area on the right, as shown in Figure 8.

          Figure 8 Selecting installation software

          NOTE:

          • In Minimal Install mode, not all packages in the installation source are installed. If a required package is not installed, you can mount the installation source to the local host as a repo source, and use DNF to install the package.
          • If you select Virtual Host, the virtualization components QEMU, libvirt, and edk2 are installed by default. You can select whether to install components such as OVS in the add-on area.

          After the setting is complete, click Done in the upper left corner to go back to the INSTALLATION SUMMARY page.

        2. Select Installation Destination to set configuration items.

          On the INSTALLATION DESTINATION page, select a local storage device.

          NOTICE:

          • The NVMe data protection feature is not supported because the NVMe drivers built in the BIOSs of many servers are of earlier versions. (Data protection: Format disk sectors to 512+N or 4096+N bytes.) Therefore, when selecting a proper storage medium, do not select an NVMe SSD with data protection enabled as the system disk. Otherwise, the OS may fail to boot.
          • You can consult the server vendor about whether the BIOS supports NVMe disks with data protection enabled as system disks. If you cannot confirm whether the BIOS supports NVMe disks with data protection enabled as system disks, you are not advised to use an NVMe disk to install the OS, or you can disable the data protection function of an NVMe disk to install the OS.

          You also need to configure the storage to partition the system. You can either manually configure partitions or select Automatic for automatic partitioning. Select Automatic if the system is installed in a new storage device or the data in the storage device is not required, as shown in Figure 9.

          Figure 9 Setting the installation destination

          NOTE:

          • During partitioning, to ensure system security and performance, you are advised to configure the following partitions: /boot, /var, /var/log, /var/log/audit, /home, and /tmp.
          • If the system is configured with the swap partition, the swap partition is used when the physical memory of the system is insufficient. Although the swap partition can be used to expand the physical memory, when the swap partition is used due to insufficient memory, the system responds slowly and the system performance deteriorates. Therefore, you are advised not to configure the swap partition in a system with sufficient physical memory or a performance-sensitive system.
          • If you need to split a logical volume group, select Custom to manually partition the logical volume group. On the MANUAL PARTITIONING page, click Modify in the Volume Group area to reconfigure the logical volume group.

          After the setting is complete, click Done in the upper left corner to go back to the INSTALLATION SUMMARY page.

        3. Select Root Password and set the root password.

          On the ROOT PASSWORD page, enter a password that meets the Password Complexity requirements and confirm the password, as shown in Figure 10.

          NOTE:

          • The root account is used to perform key system management tasks. You are not advised to use the root account for daily work or system access.

          • If you select Lock root account on the Root Password page, the root account will be disabled.

          Password Complexity

          The password of the root user or a new user must meet the password complexity requirements. Otherwise, the password setting or user creation will fail. The password must meet the following requirements:

          1. Contains at least eight characters.

          2. Contains at least three of the following: uppercase letters, lowercase letters, digits, and special characters.

          3. Different from the user name.

          4. Not allowed to contain words in the dictionary.

          NOTE: In the openEuler environment, you can run the cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt command to export the dictionary library file dictionary.txt. You can check whether the password is in this dictionary.

          Figure 10 root password

          After the settings are completed, click Done in the upper left corner to go back to the INSTALLATION SUMMARY page.

        4. Select Create a User and set the parameters.

          Figure 11 shows the page for creating a user. Enter the user name and set the password. The password complexity requirements are the same as those of the root password. In addition, you can set the home directory and user group by clicking Advanced, as shown in Figure 12.

          Figure 11 Creating a use

          Figure 12 Advanced user configuration

          After the settings are completed, click Done in the upper left corner to go back to the INSTALLATION SUMMARY page.

        5. Set other configuration items. You can use the default values for other configuration items.

      3. Click Start the Installation to install the system, as shown in Figure 13.

        Figure 13 Starting the installation

      4. After the installation is completed, restart the system.

        openEuler has been installed. Click Reboot to restart the system.

      Viewing System Information

      After the system is installed and restarted, the system CLI login page is displayed. Enter the username and password set during the installation to log in to openEuler and view the following system information. For details about system management and configuration, see the openEuler 22.03_LTS_SP2 Administrator Guide.

      • View the system information:

        $ cat /etc/os-release
        NAME="openEuler"
        VERSION="22.03 (LTS-SP2)"
        ID="openEuler"
        VERSION_ID="22.03"
        PRETTY_NAME="openEuler 22.03 (LTS-SP2)"
        ANSI_COLOR="0;31"
        
      • View system resource information.

        View the CPU information.

        lscpu
        

        View the memory information.

        free
        

        View the drive information.

        fdisk -l
        
      • View the IP addresses.

        ip addr
        

      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.
      Bug Catching
      编组 3备份