Go to file

Craig Bryant eb7b56fc50 Require the user to supply Vertica JDBC jar

Vertica JDBC jar can't be redistributed so require user to place jar
in directory where vagrant up is done. This cookbook will then
place the jar in the correct place.

Also, updated maintainer information in metadata.rb

Change-Id: I426d9585b4564872b5ad43eed4e2082148b5597b

2014-08-18 07:20:52 -06:00

attributes

Get initial build to work.

2014-07-17 10:06:12 -06:00

recipes

Require the user to supply Vertica JDBC jar

2014-08-18 07:20:52 -06:00

spec

Get initial build to work.

2014-07-17 10:06:12 -06:00

templates/default

fixed configuration file to go with agent changes

2014-07-30 12:41:20 -07: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

Require the user to supply Vertica JDBC jar

2014-08-18 07:20:52 -06:00

README.md

Require the user to supply Vertica JDBC jar

2014-08-18 07:20:52 -06:00

Strainerfile

Get initial build to work.

2014-07-17 10:06:12 -06:00

README.md

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/mon/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/mon/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/mon/vertica if run using Chef Solo.