Versions Compared

Old Version 9

changes.mady.by.user Jroy

Saved on

compared with

New Version 10

changes.mady.by.user Jroy

Saved on

Key

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

Automatique

Instalation

  • Environnent : Redhat/Centos 6.6  ( 64bits )
  • Installation automatique : http://static.shinken-solutions.com/releases/shinken-enterprise_V02.03.01.tar.gz
    •  « Dé-tarez » le package.
      • Cela vous créera un répertoire shinken-entreprise contenant le script d’installation et les dépendances nécessaire à l’installation.

    • Lancer la commande ./install.sh qui se trouve à la base du répertoire shinken-entreprise
      • Il installera Shinken Entreprise et ses composants automatiquement.
      • Cependant, le Sdk VMWare nécessitera une installation manuelle.
        • Les commandes à exécuter pour lancer l’installation du Sdk VMWare sont affichées à la fin du install.sh.
        • Nous vous conseillons de les exécuter en suivant, mais elles peuvent aussi être exécutées ultérieurement.

    • Lancez la commande shinken-healthcheck
      • Elle vérifiera que Shinken Entreprise est bien configuré et fonctionnel.

 

Mise à Jour

  • Environnent :    Redhat/Centos 6.6  ( 64bits ) avec un version 02.03.XX de Shinken Entreprise déjà installé.
  • Mise à jour:       http://static.shinken-solutions.com/releases/shinken-enterprise_V02.03.01.tar.gz
    • « Dé-tarez » le package
      • Cela vous créera un répertoire shinken-entreprise contenant le script de mise à jour et les dépendances nécessaire à l’installation.

    • Lancer script update.sh
      • Il mettra à jour Shinken Entreprise ( mais n'aura aucune incidence sur le dossier de configuration de /etc/shinken, évitant tous risque d’écrasement qu’une configuration que vous auriez défini ).
      •  Exécutez la commande shinken-healthcheck.
        • Vérifiera que Shinken Entreprise est bien configuré et en cours d'exécution.

Manuel

Prerequites


The Shinken Enterprise application need some prerequites:

  • 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
Al the installation is automatic, and is loggued into the /root/shinken.enterprise.install.log file.
This installation 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
Al the installation is automatic, and is loggued into the /root/shinken.enterprise.install.log file.
This installation 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