Moogsoft Docs

Moogsoft AIOps v7.3.x - Offline RPM pre-installation steps

You must perform certain preparatory tasks before you install Moogsoft AIOps v7.3.x.

Follow these steps if you have root access to the machine or machines on which you will install or upgrade Moogsoft AIOps, but you cannot connect to Yum repositories outside your network from those machines.

For RPM pre-installation steps, see v7.3.x - RPM pre-installation steps.

For Tarball pre-installation steps, see v7.3.x - Tarball pre-installation steps.

Before you begin

Before you begin to prepare for the installation, verify the following:

Download the installation files

Complete the following steps before you perform an offline RPM installation of Moogsoft AIOps v7.3.x:

  1. Download the two archives required for the offline installation, using the following links:

  2. Copy the downloaded Tarball files to your offline system.

  3. Download the Percona and dependency packages using cURL on an internet-connection host:

    curl -L -O;
    curl -L -O;
    curl -L -O;
    curl -L -O;
    curl -L -O;

Prepare the local Yum repositories

Follow these steps to create local Yum repositories to house the installation packages. If you are running a distributed installation, perform these steps on each machine that will run Moogsoft AIOps components.

  1. Create two directories to house the repositories. For example:

    sudo mkdir -p /media/localRPM/BASE/
    sudo mkdir -p /media/localRPM/ESR/
  2. Extract the two Tarball files into separate directories. For example:

    tar xzf *-MoogsoftBASE7_offline_repo.tar.gz -C /media/localRPM/BASE/
    tar xzf *-MoogsoftESR_7.3.1_offline_repo.tar.gz -C /media/localRPM/ESR/
  3. Back up the existing /etc/yum.repos.d directory. For example:

    mv /etc/yum.repos.d /etc/yum.repos.d-backup
  4. Create an empty /etc/yum.repos.d directory. For example:

    mkdir /etc/yum.repos.d
  5. Create a local.repo file ready to contain the local repository details:

    vi /etc/yum.repos.d/local.repo
  6. Edit local.repo and configure the baseurl paths for BASE and ESR to point to the your directories. For example:

    name=MoogCentOS-$releasever - MoogRPM
    name=MoogCentOS-$releasever - MoogRPM
  7. Clean the Yum cache:

    yum clean all
  8. Verify that Yum can detect the newly created repositories. For example:

    yum info "moogsoft-*"
    Available Packages
    Arch        : x86_64
    Version     : 7.3.1
    Release     : XYZ
    Size        : 76 M
    Repo        : ESR
    Summary     : Algorithmic Intelligence for IT Operations
    URL         :
    License     : Proprietary
    Description : Moogsoft AIOps (7.3.1) - Build: XYZ - (Revision: XYZ)

    The results should include the following packages:

    Name        : moogsoft-db
    Name        : moogsoft-integrations
    Name        : moogsoft-integrations-ui
    Name        : moogsoft-mooms
    Name        : moogsoft-search
    Name        : moogsoft-server
    Name        : moogsoft-ui
    Name        : moogsoft-utils
    Name        : moogsoft-common
  9. Install Percona on all servers that will house a database node. The script configures multiple nodes to run as a cluster. A single node is also supported. This command should be run on an internet-connected host in order to download the installer. If this host does not have internet access, download the script on a different host before copying it to this host.

    Ensure that any host Percona will be installed on has the Percona RPMs (detailed above) in the current directory, and the offline yum repository has also been deployed

    Substitute your "speedy" Yum repo user credentials:

    cat > << _EOF_
    echo "Please provide access credentials for the 'speedy' yum repository in order to download the Percona setup script"
    read -p "AIOps Repository Username: " AIOPS_USER
    export AIOPS_USER
    read -p "AIOps Repository Password: " -s AIOPS_PASS
    export AIOPS_PASS
    curl -L -O https://\$AIOPS_USER:\$ 2>/dev/null

    Install the downloaded RPMs:

    yum -y install Percona-XtraDB-Cluster-*.rpm percona-xtrabackup-24-2.4.15-1.el7.x86_64.rpm

    Now run the script:


    The script guides you through the installation process. To configure a single database node on the same server as Moogsoft AIOps, use these settings:

    • Configure Percona as "Primary".

    • Do not set the server to "DB only".

    • Set the first database node IP address to the server IP address.

    • When prompted to enter the IP addresses of the second and third nodes, press Enter to skip these settings.

  10. Install Java 11:

    VERSION=; yum -y install java-11-openjdk-headless-${VERSION} java-11-openjdk-${VERSION} java-11-openjdk-devel-${VERSION}
  11. Set SELinux to permissive mode or disable it completely. For example, to set SELinux to permissive mode:

    setenforce 0

    If you want to disable SELinux at boot time, edit the file /etc/sysconfig/selinux.

  12. Optional: GPG key validation of the RPMs

    For users wishing to validate the RPMs before installation, the following steps must be followed:

    1. Download the key from this site:
    2. Copy the key to the server onto which the RPMs or tarball will be installed (it will be an .asc file)

    3. Import the key:

      gpg --import 2529C94A49E42429EDAAADAEC7A2253BFC50512A.asc
    4. Download all the '7.3.1' RPMs and .sig files from the speedy yum repository using a browser, providing speedy credentials when asked by the browser:

    5. Move the RPMs and .sig files into the same folder. For example, /tmp, as used in the example below.

    6. Copy the following code into a bash terminal and run it to perform the validation:

      while read RPM
      	echo "Current RPM: $RPM"
      	gpg --verify ${RPM}.sig ${RPM} 2>&1
      done < <(find /media/localRPM/ESR/RHEL/ -name '*.rpm');
    7. Confirm that all the commands for each RPM report:

      Good signature from "Moogsoft Information Security Team "<>"

Your local Yum repositories are now ready. Proceed with your offline installation or upgrade. See Upgrade Moogsoft AIOps for the instructions relevant to your deployment.