Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

RSS

opennms_helm (2) Versions 0.1.0

Installs/Configures OpenNMS Helm

Berkshelf
Policyfile
Knife
cookbook 'opennms_helm', '= 0.1.0'
cookbook 'opennms_helm', '= 0.1.0', :supermarket
knife supermarket install opennms_helm
knife supermarket download opennms_helm
README
Dependencies
Quality 63%

opennms-helm

This cookbook allows you to manage the installation and configuration of Grafana + OpenNMS Helm with Chef.

Requirements

  • CentOS 6 or 7
  • An OpenNMS system, ideally managed with the OpenNMS Chef cookbook, potentially on the same Chef node.
  • Chef >= 12.14
  • A yum repository that contains the Helm RPM.

Usage

The easiest way to deploy is to add this cookbook's default recipe to a Chef node that already has the OpenNMS managed by Chef. Continue reading for additional options, however.

Prerequisites

Yum Repo

If you'd like to manage the yum repo that contains the Helm RPM in it with Chef, include the opennms::repositories recipe in your node's run list.

OpenNMS Server Attributes

When not adding the default recipe to a node that also has OpenNMS managed by Chef, you need to set some additional node attributes. Set the following node attributes (via role, environment, wrapper cookbook, etc):

  • node['opennms']['host']
  • node['opennms']['properties']['jetty']['port']
  • node['opennms']['secure_admin_password']

Advanced Options

Tweaking Grafana

grafana.ini

Any option in the Grafana ini file can be changed with node attributes. For example, to change the temp data lifetime to 48 hours, you would set this node attribute:

node['grafana_ini']['paths']['temp_data_lifetime'] = '48h'

This would result in the [paths] section of the ini file looking something like: [paths] temp_data_lifetime = '48h' Each ini section has a Chef mash key in attributes/default.rb. (Future versions of Grafana will likely introduce additional ini sections (or remove some of the existing ones), but you can easily override these to fit whatever version of Grafana you want to use).

ldap.toml

If you'd like to use LDAP for authentication you can customize the ldap.toml file provided with Grafana. See attributes/default.rb for defaults. Note that you will need to set one or more node attributes to modify the ini file for this to do anything:

node['grafana_ini']['auth.ldap']['enabled'] = true
node['grafana_ini']['auth.ldap']['enabled'] = true
`

Configuration of LDAP via node attributes is similar to grafana.ini however the base template contains a bit more static content. See `templates/default/ldap.toml.erb` along with the default values under the `grafana_ldap` key in `attributes/default.rb` for more details along with [Grafana's docs on LDAP authentication](http://docs.grafana.org/installation/ldap/) for more information. 

## License
Apache 2.0

## Author
David Schlenk (<dschlenk@convergeone.com>)

Development
===========

This cookbook uses common ChefDK tools for testing like test kitchen, inspec, ChefSpec, foodcritic, and cookstyle.

The default rake task will run the style, lint and unit tests.

Use `rake integration:vagrant` to run the integration tests. 

Pull requests welcome!

FAQs
====

Q: Why aren't you using the [grafana cookbook](https://github.com/sous-chefs/grafana) to install Grafana?
A: I don't have a particularly good reason. In fact, the next release most likely will use that cookbook to handle the installation of Grafana and will also let you decide if you want to handle installation of grafana on your own (with your own wrapper or whatnot).

Q: Who is using this?
A: Right now, mostly tests in the main OpenNMS cookbook, but once refactored to use the Grafana cookbook it should prove quite useful for anyone that wants to use Helm.

Q: Can I do multiple OpenNMS data sources?
A: Not yet. After the refactor, yes.

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

0.1.0 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

0.1.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.1.0 passed this metric

No Binaries Metric
            

0.1.0 passed this metric

Publish Metric
            

0.1.0 passed this metric

Supported Platforms Metric
            

0.1.0 passed this metric

Testing File Metric
            

0.1.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.1.0 passed this metric