Versions Compared

Old Version 16

changes.mady.by.user JPaul Harnisch

Saved on

compared with

New Version 17

changes.mady.by.user Jroy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Automatic

Installation

  • Environment : Redhat/Centos 6.6  ( 64bits )
  • Automatic Installation : http://static.shinken-solutions.com/releases/shinken-enterprise_V02.03.01.tar.gz
    •  « untar » the package.
      • This will create a shinken-entreprise repository that contains the installation script and all the necessary dependencies.

    • Launch the install.sh command that is at the root of the shinken-entreprise repository
      • it will install automatically Shinken Entreprise and its componants
      • However, the VMWare Sdk will require a manual installation.
        • The commands needed to launch thsi installation are visible at the and of the instal.sh.
        • We do recommand to launch it directly afetr the installation. Otherwise you can do it later.

    • Launch the shinken-healthcheck command
      • It will check that Shinken Enterprise is well installed and configured.
 

Update

  • Environment :    Redhat/Centos 6.6  ( 64bits ) with a  02.03.XX version of Shinken Entreprise already installed.
    •  « untar » the package.
      • This will create a shinken-entreprise repository that contains the installation script and all the necessary dependencies.
    • Launch the update.sh script
      • It will update Shinken Entreprise ( it will not have any impact on the configuration file/etc/shinken, so that there is no risk to erase any configuration already done before ).
    • Launch the shinken-healthcheck command
      • It will check that Shinken Enterprise is well
installed and configured.

 

Manually

Prerequisites

The Shinken Enterprise application need some prerequisites:
  • RedHat or Centos 6 64bits
  • Graphite server (bundled into the automatic install)
  • Mongodb server (v2.2+) (bundled into the automatic install)
  • Perl VMWare SDK (delivered into the automatic install))
The Shinken Enterprise installation package need some dependencies. It will automatically install them if they are not already available on the system:
  • epel-release-6-8
  • perl-Socket6
  • perl-Digest-HMAC
  • perl-Digest-SHA1
  • python-simplejson
  • redhat-lsb-core
  • perl-Time-HiRes
  • perl-DateTime
  • python-paramiko
  • perl-IO-stringy
  • python-ldap
  • pycairo
  • perl-DBI
  • perl-DBD-MySQL
  • openssl-devel
  • perl-CPAN
  • uuid-perl
  • uuid-devel
  • perl-libxml-perl
  • perl-DateTime-Format-HTTP
  • perl-Nagios-Plugin
  • pymongo
  • python-bson
  • python-cherrypy-3
  • mongo-10gen-server-2.4.6-mongodb_1.x86_64
  • mongo-10gen-2.4.6-mongodb_1.x86_64

 

SHINKEN ENTREPRISE installation

Installing a CENTRAL server

In order to install a central server you need to launch:
$ tar xfz shinken-enterprise_V02.03.01.tar.gz
$ cd shinken-enterprise
$ ./intall.sh
All the installation is automatic, and is logged into the /root/shinken.enterprise.install.log file.
This script install and enable the following daemons:

  • shinken arbiter
  • shinken synchronizer
  • shinken scheduler
  • shinken poller
  • shinken reactionner
  • shinken receiver
  • shinken broker
  • mongodb
  • graphite (carbon and httpd)

 

Installing a distant poller server

In order to install a central server you need to launch:
$ tar xfz shinken-enterprise_V02.03.01.tar.gz
$ cd shinken-enterprise
$ ./intall.sh --pollernode
All the installation is automatic, and is logged into the /root/shinken.enterprise.install.log file.
This script install and enable the following daemons:

  • shinken scheduler
  • shinken poller

 

Link to the Graphite Server CONFIGURATION

The Shinken Enterprise daemons need to be configured in order to send performance data (metrics) into the Graphite server (the graphite carbon daemon).
If the Graphite server is installed in the central Shinken Enterprise server then you don't have to edit the Shinken Enterprise configuration files.
If your Graphite server is
      • installed
on another server, you must edit two configuration files:
  • /etc/shinken/modules/graphite.cfg: in order to send metrics to a graphite carbon daemon
  • /etc/shinken/modules/webui.cfg: in order to the visualization UI to query the graphite-web daemon

In the /etc/shinken/modules/graphite.cfg file you must change the following parameters:

  • host: by default localhost
  • port : by default 2003 (flat format port of the carbon daemon)

In the /etc/shinken/modules/webui.cfg file you must only change one parameter:

  • graphite_backends: by default *:localhost
It is a comma separated list of REALM:ADDRESS entries. For each realm that have its own graphite server, you must enter the realm name
      • and
the address of the graphite-web server. The * realm name will be used if no other realms are matching (default entry).

Link to the mongoDB server CONFIGURATION

The Shinken Enterprise daemons need to be
      • configured
in order to send various data into a mongodb server.
If the mongodb server is running on the central server then you can skip this configuration part.
Such data will be send in the mongodb server:
  • Configuration data: /etc/shinken/synchronizer.cfg
  • Discovery module data: /etc/shinken/module/discovery-import.cfg
  • Livestatus logs [optional]: /etc/shinken/module/logstore_mongodb.cfg
    • Reporting/SLA data: /etc/shinken/module/sla
      • .
    • cfg
  • Scheduler retention data: /etc/shinken/module/retention-mongodb.cfg

In all the configuration file, you just need to change the mongodb uri (mongodb_uri or uri parameter) like this:
mongodb_uri mongodb://localhost/?safe=false
Just edit the address of your mongodb server.
Notice: Don't change the safe parameter.

SHINKEN ENTREPRISE Launch

Central server

Then you can start your daemons:
$ /etc/init.d/carbon-cache start
$ /etc/init.d/mongodb start
$ /etc/init.d/shinken start

Distant poller server

Then you can start your daemons:
$ /etc/init.d/shinken start