Architecture Awareness Service Manual


Manual Installation

  • Installing using the repo source mounted by Yum.

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

    [openEuler21.09] # openEuler 21.09 official source
    [Epol] # openEuler 21.09:Epol official source

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

    # A-Ops architecture awareness service, usually installed on the master node
    yum install gala-spider 
    yum install python3-gala-spider
    # A-Ops architecture awareness probe, usually installed on the master node
    yum install gala-gopher 
  • 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-spider-vx.x.x-x.oe1.aarch64.rpm
    rpm -ivh gala-gopher-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_ragdol:

   enable: false
   continue: false
   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.

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.