Innovation Version



      Table 1 lists users who are involved in the running of x2openEuler functions. Maintain user information routinely and ensure user security.

      The root user has all the operation permissions. Logging in to the server as the root user may pose security risks. For security purposes, disable the SSH login of the root user. Perform the following operations: Log in to the server as a common user, switch to the root user, and check the value of PermitRootlogin in the /etc/ssh/sshd_config file. If the value of PermitRootlogin is no, the root user is not allowed to log in to the server. If the value is yes, change it to no.

      Table 1 Users

      EnvironmentUser/User TypeDefault PasswordRoleRemarks
      x2openEuler web serverx2openEulerAdminNonex2openEuler administrator
      • Creates common x2openEuler users.
      • Configures x2openEuler system settings.
      • Creates, executes, and manages x2openEuler tasks.
      • Manages the weak password dictionary.

      Common x2openEuler user

      Common users are created by the x2openEuler administrator.
      Creates, executes, and manages x2openEuler tasks.
      x2openEuler deployment environmentx2openEulerNoneDedicated user for the assessment and analysis functions of x2openEulerRemote login is disabled for the user by default.
      rootNoneroot user in the x2openEuler deployment environmentUsed for deploying x2openEuler.
      UserNoneCommon user in the x2openEuler deployment environmentUsed for deploying x2openEuler.
      Node to be upgradedrootNoneroot user on the node to be upgradedUsed for upgrade tasks.
      UserNoneCommon user on the node to be upgradedUsed for creating tasks.
      x2openEuler (MariaDB database)rootNoneMariaDB administratorCreates common x2openEuler users and maintains the database.
      x2openEulerNonex2openEuler database userOperates the database of x2openEuler.


      Utilities of x2openEuler are stored in /usr/local/x2openEuler/portal/service after x2openEuler is installed, as described in Table 2.

      Table 2 Utilities

      UtilityPathExecution CommandOptionsFunction change_ip_x2openEuler.shNoneChanges the IP address for accessing the x2openEuler WebUI. delete_file.shNoneSafely deletes files. mariadb.shNoneControls the database service. service_daemon.shNoneDetects the Nginx and Gunicorn services. service_init.shNoneInitializes the x2openEuler service. set_ssh_host_key_check_config.shNoneSpecifies whether to enable public key check for SSH connections. service_gunicorn.shNoneControls the Gunicorn service. service_nginx.shNoneControls the Nginx service. update_db_pwd.shNoneSynchronizes changed passwords to x2openEuler.

      Operating Environment Data


      Data used by the functions of x2openEuler is described in Table 3. Please ensure the security of the data.

      Operating Environment Data Scenarios

      Table 3 Data usage description

      Scenario or Function Where Data Is CollectedCommands and Files That Collects DataData Collection NecessityExcessive Data CollectionPurpose of Data UseData Storage and ProtectionData Destruction
      • Configuration and hardware information collection
      • Configuration difference analysis
      • Hardware compatibility assessment
      • /bin/cat /boot/grub2/grub.cfg
      • /usr/sbin/lspci -nvvv
      • /usr/sbin/lspci -xxx
      • /bin/netstat -npl
      • /usr/sbin/sysctl -a
      • /usr/sbin/dmidecode -t bios -t system -t baseboard -t chassis -t processor -t memory -t cache -t connector -t slot
      • /usr/sbin/dmidecode -s system-product-name
      • /bin/cat /boot/efi/EFI/centos/grub.cfg
      • /bin/cat /etc/default/grub
      NecessaryNoneFor hardware compatibility assessment and configuration difference analysis
      • The data collected for hardware compatibility assessment is stored in the memory and is not permanently stored.
      • The collected configuration and hardware information is saved in a file whose owner and owner group are x2openEuler. Other users do not have access to the file.
      • The x2openEuler user can delete the files that store collected configuration and hardware information in the /opt/x2openEuler/output/ directory.
      • The files that store collected configuration and hardware information in the /opt/x2openEuler/output/ directory are deleted when x2openEuler is uninstalled.
      • /boot/grub2/grub.cfg
      • /etc/default/grub
      • /usr/include/asm/unistd_64.h
      • /etc/fstab
      • /etc/profile
      • /etc/sysctl.conf
      • /boot/conifg-*
      NecessaryNoneFor configuration difference analysis

      Table 4 Related links

      openEuler Community
      openEuler Development Resources
      openEuler repositories
      openEuler oec-application project
      Huawei Cloud open source mirror
    • OS upgrade database support packages


      Physical machineA machine installed with a regular operating system or a bare metal machine without an operating system, in contrast to a host machine.
      ServerA special computer that provides services for clients over a network.
      Service softwareMain software installed for service running, excluding the software on which software installation and running depend.
      Virtual machineA special type of software in computer science, which creates an environment between the computer platform and end users. End users can operate software applications in the created environment.

      Acronyms and Abbreviations

      BINBinaryA binary file format
      GZIPGNU ZIPA file compression format
      JARJava ArchiveA Java software package format
      PY-Python script file
      PYC-A binary file format
      RPMRPM Package ManagerA Linux software package format
      TAR-A Linux software package format
      ZIP-A file compression format

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.


      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.


      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

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


      ● 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
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份