Innovation Version

      gala-ragdoll Usage Guide


      Manual Installation

      • Installing using the repo source mounted by Yum.

        Configure the Yum sources openEuler22.03 and openEuler22.03:Epol in the /etc/yum.repos.d/openEuler.repo file.

        [everything] # openEuler 22.03 officially released repository
        [Epol] # openEuler 22.03:Epol officially released repository

        Run the following commands to download and install gala-ragdoll and its dependencies.

        yum install gala-ragdoll # A-Ops configuration source tracing service
        yum install python3-gala-ragdoll
        yum install gala-spider # A-Ops architecture awareness service
        yum install python3-gala-spider
      • Installing using the RPM packages. Download gala-ragdoll-vx.x.x-x.oe1.aarch64.rpm, and then run the following commands to install the modules. (x.x-x indicates the version. Replace it with the actual version number.)

        rpm -ivh gala-ragdoll-vx.x.x-x.oe1.aarch64.rpm

      Installing Using the A-Ops Deployment Service

      Editing the Task List

      Modify the deployment task list and enable the steps for gala_ragdoll:

         enable: false
         continue: false
      Editing the Host List

      For details about the host configuration, see section in the Deployment Management Manual.

      Editing the Variable List

      For details about the variable configuration, see section in the Deployment Management Manual.

      Executing the Deployment Task

      See section 3 in the Deployment Management Manual to execute the deployment task.

      Configuration File Description

      /etc/yum.repos.d/openEuler.repo is the configuration file used to specify the Yum source address. The content of the configuration file is as follows:


      YANG Model Description

      /etc/yum.repos.d/openEuler.repo is expressed using the YANG language. For details, see gala-ragdoll/yang_modules/openEuler-logos-openEuler.repo.yang. The following extended fields are added:

      Extended Field NameExtended Field FormatExample
      typeConfiguration file typeini, key-value, json, text, and more
      spacerSpacer between a configuration item and its value" ", "=", ":", and more

      Attachment: Learning the YANG language:

      Creating Domains using Configuration Source Tracing

      Viewing the configuration file.

      gala-ragdoll contains the configuration file of the configuration source tracing.

      [root@openeuler-development-1-1drnd ~]# cat /etc/ragdoll/gala-ragdoll.conf
      [git] // Defines the current Git information, including the directory and user information of the Git repository.
      git_dir = "/home/confTraceTestConf" 
      user_name = "user"
      user_email = "email"
      [collect] // The collect interface provided by A-Ops.
      collect_address = ""
      collect_api = "/manage/config/collect"
      port = 11114

      Creating the Configuration Domain

      Adding Managed Nodes to the Configuration Domain

      Adding Configurations to the Configuration Domain

      Querying the Expected Configuration

      Deleting Configurations

      Querying the Actual Configuration

      Verifying the Configuration

      Configuration Synchronization

      Not provided currently.

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