DaVINCI Installation
Contents
|
A short overview
DaVINCI is a tool designed to help you generating dynamic views for your IT Services and Infrastructure Objects using a currently established Nagios™ or GroundWork™ installation as source for status data. Its simple drag and drop interface turn your job easier, you just need to plug DaVINCI into your running Nagion™ or GroundWork™ installation and you are ready to go.
To assure an accurate data fetch, DaVINCI uses a server side connector called ANA(Advanced Nagios™ Adapter) that can be easily integrated with various Nagios™ event brokers, for instance NDO(Nagios™ Data Out)¹ and MKLiveStatus², and uses JSON as data exchange format.
DaVINCI's client is developed using the most advanced technology when refering to graphical representation, it is completely accessible by modern web browsers in a platform independent way.
Supported Nagios™ Event Brokers
DaVINCI is fully integrated with the following Nagios™ Event Brokers:
- NDO(Nagios™ Data Out) ¹
- MKLiveStatus ²
Prerequisites
In order to install and configure DaVINCI you will need to provide a very specific group of prerequisites in your server environment. They are listed below:
- A running Nagios™ installation with one of the supported event brokers or a GroundWork™ installation (both must be running in a RedHat™ Enterprise Linux or in a CentOS environment) - We currently support CentOS 5.x and RHEL 5
- Apache HTTP Server
- MySQL Database Server
- PHP version 5.2
- ionCube PHP Encoder
- PHP module for MySQL
- PHP module for JSON
- PHP module for SOAP (In case of GroudWork Network Monitor)
You don't need to worry about this dependencies by now, the installation script will warn you in case of missing any of them. Regarding the client side dependencies, you will just need an Internet Browser with a working Flash™ Player plug-in.
Installation process
Once you have registered to OpServices website just proceed to [download section] and get the opservices-ana-davinci.bin file, download it and upload the file to your Nagios™ or GroundWork™ server.
With the file in place, you need to log-in into Nagios™ server with Administrator(root) credentials(in order to assure the correct dependency fullfilment the DaVINCI installation agent needs Administrator privileges). First of all, we need to assure the correctness of opservices-ana-davinci.bin file permissions, just enter to the directory where you have uploaded the file and type the following:
With this measure, we assure that we have execution permission on the DaVINCI's agent installation file. Now we can run the agent as below:
After running the script we will see a welcome message:
The default option, in this case, is yes(y). In order to proceed to the next step, just press ENTER and you will be presented to the following screen:
Here you need to select what kind of back-end DaVINCI will use. Just type the number according to your system and press ENTER, remembering that the default option at this screen is to perform a Nagios™ integration. If you are going to proceed with a GroudWork integration, please refer to the section “GroundWork™ Installation” at this document, for a Nagios™ configuration, look for section “Nagios™ Installation” below.
Nagios™ integration
After select Nagios™ as back-end, we will need to submit some basic additional information:
At the screen above, just type the Nagios™ main configuration path and press ENTER. Once again, the DaVINCI installation agent will provide you with a default option(/usr/local/nagios/etc/nagios.cfg).
After Nagios™ main configuration file, the agent will ask you about the CGI main configuration file(usualy cgi.cfg) as demonstrated below:
Providing the right information for both Nagios™ main configuration and CGI configuration files, the agent will present you with a brief summary of parsed information, more specifically about the CGI URL PATH:
Just press ENTER to proceed to dependencies check. Now we are ready to check automatically for Operating System environment dependencies, just press ENTER again when the below screen shows up on the screen:
First of all, the agent will check for Apache availability in the system. In case of dependency check error(as you can see below) the agent will stop and inform you about the unfilled dependency:
In the case above, you will need to install Apache Web Server before continue. To achieve this goal, you need to attempt to install Apache using the package administration program 'yum'. Once you installed Apache, start the DaVINCI installation agent again in order to finish integration.
The next dependency checked is MySQL database server:
DaVINCI installation agent will ask you for the database host(IP address of the MySQL server) and the database credentials to connect to it. Just fill the fields and at the end the agent will try a connection to assure a correct configuration as you can see below:
After the MySQL database configuration the agent will check for PHP related dependencies, including the PHP, as you can see below:
Among the dependencies, the agent will check for ionCube PHP Encoder³. Due to licensing system, you will need to add ionCube support to your running PHP installation. You do not need to worry about the encoder, because the DaVINCI installation agent can automatically install and configure it for you, as follow:
If you want to automatically install ionCube Loader, just press ENTER and the installation and configuration will automatically take place, otherwise you can stop the DaVINCI installation agent answering No to above question and install ionCube loader manually⁴:
This is the end of dependency check stage, now the installation agent is ready to install the packages. DaVINCI is composed by four different RPM packages, and they are only installed once all dependencies are fullfiled:
- opservices-ana-1.0-1.noarch.rpm
- opservices-davinci-4.5.0-1.noarch.rpm
- opservices-oplib-4.5.0-1.noarch.rpm
- opservices-oplib-extjs-4.5.0-1.noarch.rpm
The package versions could be slightly different, because DaVINCI is a work in progress and there are new versions being released constantly. The DaVINCI installation agent will now proceed to RPM package installation as you can see below:
To install the four RPM packages, just press ENTER:
At this time, we have done the basic configuration of DaVINCI, now is the time do define the used Nagios™ Event Broker. The installation agent will ask you which Broker you are using:
Just pick the right choice and go to the right section on this document to proceed: to configure a NDO or a NagiosXI installation, please refer to “NDO/NagiosXI Installation” section, and for a MK LiveStatus installation, refer to “MK LiveStatus installation”.
NDO/NagiosXI Installation
For an NDO integration, we just need to provide the NDO2DB main configuration file(usualy ndo2db.cfg) path on the screen below :
The default option, in this case is /usr/local/nagios/etc/ndo2db.cfg. After you fullfil the path, the DaVINCI installation agent will perform some internal verification and the following screen will appears:
Now you can proceed to “Authentication Configuration” section on this document.
MK Livestatus Installation
For MK LiveStatus installation, you will need to provide the path for the pipe used by this broker as showed below:
The MK LiveStatus pipe is generally located at /usr/local/nagios/var/rw/live. If this is your case, just press ENTER, otherwise type the right path followed by ENTER:
Now you can proceed to “Authentication Configuration” section on this document.
Authentication Configuration
DaVINCI can integrate the authentication with Nagios™ in two different ways. The first is using the Apache/Basic authentication, in this case you will be able to see in DaVINCI main interface, all hosts and services that you can visualize in Nagios™ with you logged user. This is the most likely way once DaVINCI will seamlessly respect your Nagios™ configuration options. The second way is to define a fixed user, using this method once you log-in DaVINCI main interface, you will be able to see all hosts and services that this fixed user can visualize. Bare in mind that the fixed user must be a valid Nagios™ contact, created and registered into Broker's database.
Let's proceed to our authentication configuration process:
If you choose the first option(Apache/Basic), the DaVINCI installation agent will ask you for the path of your Apache's main configuration file in order to extract some vital information:
Just type the right path to httpd.conf file and press ENTER:
This process will create an appropriate .htaccess file on demand for you. If you pick the 'Fixed User' option, DaVINCI installation agent will ask you for a Nagios™ valid contact name:
Just type the desired contact name and press ENTER. As default you can use the contact nagiosadmin. Please attempt to the fact that DaVINCI installation agent does not check if the provided contact is actually a valid contact from Nagios™' point of view(you can change this contact in the future):
Pressing ENTER now will lead you to a screen where the final configurations are made:
Just type ENTER and the last DaVINCI installation agent screen will appears, showing you a summary of the previously selected options:
Now its time to test our installation, on a desktop just open a browser and access the URL http://YOUR_SERVER_ADDRESS/ana changing YOUR_SERVER_ADDRESS by Nagios™ server IP address.
All software installed by RPM packages will be located under /usr/local/opmon directory. You can change the options passed during the installation using the Web interface or editing the file /usr/local/opmon/share/ana/config.ini with your favorite text editor.
GroundWork™ integration
After select GroundWork™ as back-end, we will need to submit some basic additional information about our environment:
On the screen above, you need to provide the base path for you GroundWork™ installation and press ENTER. After that, the DaVINCI installation agent will perform some internal check to verify the availability of GroundWork™ internal components:
Just validate the data supplied by DaVINCI installation agent and press ENTER to proceed to dependencies check process:
Pressing ENTER will lead the DaVINCI installation agent to a complete verification. The first dependency check is related to MySQL:
DaVINCI installation agent will ask you for the database host(IP address of the MySQL server) and the database credentials to connect to it. Just fill the fields and at the end the agent will try a connection to assure a correct configuration.
After the MySQL database configuration the agent will check for PHP related dependencies, including the PHP. Among these dependencies, the agent will check for ionCube PHP Encoder³. Due to licensing system, you will need to add ionCube load support to your running PHP installation. You do not need to worry about the ionCube loader, because DaVINCI installation agent is designed to automatically install and configure it for you, as follow:
If you want to automatically install ionCube Loader, just press ENTER and the installation and configuration will automatically take place, otherwise you can stop the DaVINCI installation agent answering No to above question and install ionCube loader manually⁴:
This is the end of dependency check stage, now the installation agent is ready to install the packages. DaVINCI is composed by four different RPM packages, and they are only installed once all dependencies are fullfiled:
- opservices-ana-1.0-1.noarch.rpm
- opservices-davinci-4.5.0-1.noarch.rpm
- opservices-oplib-4.5.0-1.noarch.rpm
- opservices-oplib-extjs-4.5.0-1.noarch.rpm
The package versions could be slightly different, because DaVINCI is a work in progress and there are new versions being released constantly. The DaVINCI installation agent will now proceed to RPM package installation as you can see below:
To install the four RPM packages, just press ENTER:
After RPM installation process, the DaVINCI installation agent will perform a last verification on your system and create the needed databases:
Just type ENTER and the last DaVINCI installation agent screen will appears, showing you a summary of the previously selected options:
Now its time to test our installation, on a desktop just open a browser and access the URL http://YOUR_SERVER_ADDRESS/ana changing YOUR_SERVER_ADDRESS by GroundWork™ server IP address.
All software installed by RPM packages will be located under /usr/local/opmon directory. You can change the options passed during the installation using the Web interface or editing the file /usr/local/opmon/share/ana/config.ini with your favorite text editor.
Uninstalling DaVINCI
During the DaVINCI installation process, an uninstall agent will be created, allowing you to easily uninstall all the environment configured. If you want to uninstall DaVINCI, just log-in to the server where it is configured and, as Administrator(root), type on terminal:
Press ENTER and a confirmation message will appear on your screen:
Just type 'y' and press ENTER:
The DaVINCI uninstaller agent will ask you if you want o remove the ionCube support from PHP, choose the desired option, press ENTER and you are done:
¹ http://exchange.nagios.org/directory/Addons/Database-Backends/NDOUtils/details
