ea199ff4a3
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have. |
||
---|---|---|
attributes | ||
recipes | ||
spec | ||
templates/default | ||
.gitreview | ||
.rubocop.yml | ||
Berksfile | ||
Gemfile | ||
metadata.rb | ||
README.md | ||
Strainerfile |
WARNING!!
Monasca is now deployed via Ansible. This project is no longer maintained and may be out of date. It will be moved to the StackForge attic soon.
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.