Installation

...

• Environment :                 Redhat/Centos 6.6  ( 64bits )
• Automatic install :          http://static.shinken-solutions.com/releases/shinken-enterprise_V02.03.01.tar.gz
  • « Un-tar » the package
    • It will automatically create a shinken-enterpise repository including the installation script and the dependencies needed
  • Launch the script install.sh that you will find on the root of the shinken-enterpise repository
    • It will install Shinken and all its dependencies.
    • Please not that the VMWare sdk will require a manual installation       
      • The command needed to launch it is stated at the end of the install.sh script.
      • We recommend that you launch it immediately, even if you can postpone it.
    • Run the command shinken-healthcheck
      • => will check if shinken is well configured and up and running.

• Update package (your current Shinken Enterprise):
  • Environment :                 Redhat/Centos 6.6  ( 64bits ) with an already install Shinken 02.03.00
  • Automatic update :          http://static.shinken-solutions.com/releases/shinken-enterprise_V02.03.01.tar.gz
    • « Un-tar » the package
    • Launch the script update.sh
      • It will update Shinken (but will not have any impact on /etc/shinken configuration folder).
      • Run the command shinken-healthcheck.
        • => will check if shinken is well configured and running.

• Demo ( Virtual Machine ):
  • VMWare:                          http://static.shinken-solutions.com/releases/shinken-enterprise-V02.03-01-vmware.ova
    • Import it on an ESXi environement.
    • Or use the official WMWare player ( see player: http://www.vmware.com/fr/products/player/playerpro-evaluation.html )

...

automatique

manuel

Mise à jour

Automatique

Manuel

...

Prerequites

The Shinken Enterprise application need some prerequites:

...

• 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:

...

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:

...

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