Automatique

Installation

• Environment : Redhat/Centos 6.6  ( 64bits )

• Automatic Installation :

• •  « Un-tar » the package.
    • tar zvxf shinken-enterprise_V02.03.

• • • XX-LANGUAGE.tar.gz

• • • This will create a shinken-

• • • enterprise repository that contains the installation script and all the necessary dependencies.
      
      
  • Launch the install.sh command that is at the root of the shinken-

• • enterprise repository
    • it will install automatically Shinken

• • • Enterprise and its

• • • components.
    • However, the VMWare Sdk will require a manual installation.
      • The commands needed to launch

• • • • this installation are visible at the and of the

• • • • install.sh.
      • We do

• • • • recommend to launch it directly

• • • • after the installation

• • • • , even if you can

• • • • postpone it

• • • • .
        
        
  • Launch the shinken-healthcheck command
    • It will check

• • • if Shinken Enterprise is well

• • • configured and up and

• • • running.

Update

• Environment :    Redhat/Centos 6.6  ( 64bits ) with a  02.03.XX version of Shinken Entreprise already installed.

• Automatic Update:

• •  « Un-tar » the package.
    • tar zvxf shinken

• • • -enterprise_V02.03.

• • • XX-LANGUAGE.tar.gz

• • • This will create a shinken-

• • • enterprise 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.
      

Manuel

Installation (Advanced Mode)

• Advanced Partial Automatic Installation (enable only selected daemons) :
  
  
  • « untar » the package.
    • tar zvxf shinken

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))

• 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

• • • -enterprise_V02.03.

• • • XX-LANGUAGE.tar.gz

• • • This will create a shinken-enterprise

• • •  repository that contains the installation script and all the necessary dependencies.
      
      
  • Launch the install.sh command that is at the root of the shinken-enterprise repository but with options based on the daemons you want to be enabled on your system:
    

    • --pollernode: enable the Poller daemon (launch checks)

    • --reactionnernode: enable the Reactionner daemon (launch notifications)

    • --schedulernode: enable the scheduler daemon (schedule checks)

    • --arbiternode: enable the arbiter daemon (central distribution role)

    • --receivernode: enable the receiver daemon (receive checks)

    • --synchronizernode: enable the Synchronizer daemon (manage configuration)

    • --brokernode: enable the broker daemon (export data)

• • Launch the shinken-healthcheck command
    • It will check that Shinken Enterprise is well installed and configured and that daemons are running well (only those enabled).
      
      
• After the initial installation, It is useless to relaunch the install.sh command to activate/de-activate daemons 
  • if you miss a daemon use the shinken-daemons-enable command.
  • see the chapter Daemons listing/enable/disable commands, for more details.

• 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