Long-Term Supported Versions

    Innovation Versions

      Installation and Deployment

      The sysmaster service can be used in containers and VMs. This document uses the AArch64 architecture as an example to describe how to install and deploy sysmaster in both scenarios.

      Software

      • OS: openEuler 22.03 LTS SP3

      Hardware

      • x86_64 or AArch64 architecture

      Installation and Deployment in Containers

      1. Install Docker.

        yum install -y docker
        systemctl restart docker
        
      2. Load the base container image.

        Download the container image.

        wget https://repo.openeuler.org/openEuler-22.03-LTS-SP3/docker_img/aarch64/openEuler-docker.aarch64.tar.xz
        xz -d openEuler-docker.aarch64.tar.xz
        

        Load the container image.

        docker load --input openEuler-docker.aarch64.tar
        
      3. Build the container.

        Create a Dockerfile based on the image name queried by the docker images command, for example, openEuler-22.03-LTS-SP3.

        cat << EOF > Dockerfile
        FROM openEuler-22.03-LTS-SP3
        RUN yum install -y sysmaster
        CMD ["/usr/lib/sysmaster/init"]
        EOF
        

        Build the container.

        docker build -t openEuler-22.03-LTS-SP3:latest .
        
      4. Start and enter the container.

        Start the container.

        docker run -itd --privileged openEuler-22.03-LTS-SP3:latest
        

        Obtain the container ID.

        docker ps
        

        Use the container ID to enter the container.

        docker exec -it CONTAINERID /bin/bash
        

      Installation and Deployment in VMs

      1. Create an initramfs image.
        To avoid the impact of systemd in the initrd phase, you need to create an initramfs image with systemd removed and use this image to enter the initrd procedure. Run the following command:

        dracut -f --omit "systemd systemd-initrd systemd-networkd dracut-systemd" /boot/initrd_withoutsd.img
        
      2. Add a boot item.
        Add a boot item to grub.cfg, whose path is /boot/efi/EFI/openEuler/grub.cfg in the AArch64 architecture and /boot/grub2/grub.cfg in the x86_64 architecture. Back up the original configurations and modify the configurations as follows:

        • menuentry: Set the item name to openEuler sysmaster.
        • linux: Change root=/dev/mapper/openeuler-root ro to root=/dev/mapper/openeuler-root rw.
        • linux: if Plymouth is installed in the environment, add plymouth.enable=0 to disable it.
        • linux: Add init=/usr/lib/sysmaster/init.
        • initrd: Set to /initrd_withoutsd.img.
      3. Install sysmaster.

        yum install sysmaster
        
      4. If the openEuler sysmaster boot item is displayed after the restart, the configuration is successful. Select it to log in to the VM.

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