Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This section covers installing Squirro on a Linux system without internet access. This complements the Setup on Linux section.

Table of Contents

Prerequisites

Please refer to the Architecture and Prerequisites sections of Setup on Linux. Both of these sections also apply for an offline installation.

For an offline installation Squirro will provide you with a tar.gz file which contains all the required RPM files. Make that file available on the server, for example by copying it over using scp.

YUM Repositories

Extract Repository

The tar.gz file above contains a YUM repository that can be used offline. To use this on the server, extract it:

[root@localhost ~]# mkdir -p /opt/squirro
[root@localhost ~]# cd /opt/squirro
[root@localhost ~]# tar -xvf /tmp/squirro-xxx.tar.gz

This creates the folder /opt/squirro/repo and populates it with al the RPM files.

Squirro

Create the file /etc/yum.repos.d/squirro.repo.

/etc/yum.repos.d/squirro.repo
[squirro]
name=Squirro
baseurl=file:///opt/squirro/repo/
enabled=1
metadata_expire=300
gpgcheck=0

Storage Node Installation

Installation of the storage node happens with two separate packages. The first package installs the required Linux users and the second installs the services. Use the following two commands for the installation:

[root@localhost ~]# yum install squirro-storage-node-users
[root@localhost ~]# yum install squirro-storage-node

Cluster Node Installation

Installation of the Squirro cluster node happens with two separate packages. The first package installs the required Linux users and the second installs the services. Use the following commands for the installation:

Important step for RHEL7 / CentOS7

Support for RHEL7 is still experimental. The default MySQL variant for MySQL on RHEL7/CentOS7 is MariaDB. Our RPM packages are however not yet ready for this change.

Please execute the following workaround before you execute the next step:

echo "Installing Squirro dependency MariaDB"
yum install -y mariadb-server
yum install -y policycoreutils-devel
if [ -f /lib/systemd/system/mariadb.service ]; then
    systemctl stop mariadb
    mv /lib/systemd/system/{mariadb,mysqld}.service
    systemctl enable mysqld
    systemctl start mysqld
fi

Note that once we've release official support this renaming of the mariadb script will have to be undone.


[root]# yum install squirro-cluster-node-users
[root]# yum install squirro-cluster-node

If the Storage and Cluster node are not the same physical machine, then you need now to adjust the file /etc/nginx/conf.d/upstream-elastic.inc to point to the IP or Hostnames of the storage node(s).

Examples:

Single Server both rolesDedicated Storage NodeMultiple Storage Nodes
upstream elastic {
    server 127.0.0.1:9200;
    keepalive 32;
}
upstream elastic {
 server 192.168.0.20:9200;
 keepalive 32;
}
upstream elastic {
 server 192.168.0.20:9200;
 server 192.168.0.21:9200;
 server 192.168.0.22:9200;
 keepalive 32;
}

If changes have been made to this file, reload the nginx configuration

service nginx reload

Finally start the Squirro Services


RHEL6 /Centos6RHEL7/CentOS7
[root]# service monit start
[root]# monit -g all-manual start
echo "Starting Squirro services"
cd /lib/systemd/system
for service in $(ls sq*d.service); do
    echo "Starting $service"
    systemctl restart $service
done

At the time of writing monit is not yet part of our RHEL7/CentOS packages.



  • No labels