Go to file
Craig Bryant 12671c255d Changes to use monasca instead of mon
Changed to use monasca_api instead of mon_api. Added monasca_api
user to group monasca so the api can write to /var/log/monasca and
read the config file in /etc/monasca

Change data bag names to monasca_api instead of mon_api

Place jar file in /opt/monasca

Change service name from mon-api to monasca-api

Change-Id: Ic2a8db0b6b1451872f42373077cf5f2911de3652
2014-09-16 11:34:26 -06:00
attributes Changes to use monasca instead of mon 2014-09-16 11:34:26 -06:00
recipes Changes to use monasca instead of mon 2014-09-16 11:34:26 -06:00
spec Get initial build to work. 2014-07-17 10:06:12 -06:00
templates/default Changes to use monasca instead of mon 2014-09-16 11:34:26 -06:00
.gitreview Get initial build to work. 2014-07-17 10:06:12 -06:00
.rubocop.yml Get initial build to work. 2014-07-17 10:06:12 -06:00
Berksfile Get initial build to work. 2014-07-17 10:06:12 -06:00
Gemfile Get initial build to work. 2014-07-17 10:06:12 -06:00
metadata.rb Changes to use monasca instead of mon 2014-09-16 11:34:26 -06:00
README.md Changes to use monasca instead of mon 2014-09-16 11:34:26 -06:00
Strainerfile Get initial build to work. 2014-07-17 10:06:12 -06:00

Description

Configures and sets up the Monasca api. Includes attributes for log backups, ossec file watching and ossec rules. Also included is an icinga check for the service health check.

Using Vertica

If Vertica is used as the database for Monasca, the Vertica JDBC jar that matches the Vertica version must be placed in /opt/monasca/vertica. The jar from Vertica will be named like vertica-jdbc-7.0.1-0.jar and must be renamed to vertica_jdbc.jar when placed in /opt/monasca/vertica. You can find the Vertica JDBC jar in /opt/vertica/java on a system with the Vertica database installed. This cookbook will copy the Vertica JDBC Jar from /vagrant and place it in /opt/monasca/vertica if run using Chef Solo.