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

Select Status

RSS

nsca (4) Versions 0.1.2

Installs/Configures NSCA daemon/client

Policyfile
Berkshelf
Knife
cookbook 'nsca', '= 0.1.2', :supermarket
cookbook 'nsca', '= 0.1.2'
knife supermarket install nsca
knife supermarket download nsca
README
Dependencies
Quality 29%

NSCA

Cookbook Version
Build Status

Description

Chef cookbook to install and configure NSCA server/client.

Repository

https://github.com/parallels-cookbooks/nsca

Chef Super Market

https://supermarket.chef.io/cookbooks/nsca

Requirements

Chef

Chef version 0.10.10+ and Ohai 0.6.12+ are required.

Platforms

  • Debian 6.X, 7.X
  • Ubuntu 14.04
  • Red Hat Enterprise Linux (CentOS/Amazon/Scientific/Oracle) 5.X, 6.X
  • Fedora 22

Notes: This cookbook has been tested on the listed platforms. It may work on other platforms with or without modification.

Cookbooks

  • yum-epel

Recipes

server

Configure NSCA server.

client

Configure NSCA client.

Attributes

platform specific attributes (auto set based on platform)

  • node['nsca']['conf_dir'] - location of the nsca configuration
  • node['nsca']['user'] - NSCA user
  • node['nsca']['group'] - NSCA group
  • node['nsca']['mode'] - chmod configuration file
  • node['nsca']['command_file'] - path to nagios/icinga command pipe
  • node['nsca']['alternate_dump_file'] - path to alternative dump file when pipe is closed

config file options

  • node['nsca']['pid_file'] - path to pid file
  • node['nsca']['server_address'] - address for NSCA binding
  • node['nsca']['nsca_chroot'] - path to NSCA chroot
  • node['nsca']['server_port'] - NSCA port binding
  • node['nsca']['debug'] - This option determines whether or not debugging messages are logged to the syslog facility.
  • node['nsca']['aggregate_writes'] - This option determines whether or not the nsca daemon will aggregate writes to the external command file for client connections that contain multiple check results.
  • node['nsca']['append_to_file'] - This option determines whether or not the nsca daemon will open the external command file for writing or appending.
  • node['nsca']['max_packet_age'] - This option is used by the nsca daemon to determine when client data is too old to be valid.
  • node['nsca']['password'] - This option is used for password if data bag doesn't exist.
  • node['nsca']['decryption_method'] - This option determines the method by which the nsca daemon will decrypt the packets it receives from the clients.

Data bags

Password for NSCA can be described in data bag node['nsca']['data_bag_item']. There should be an item which name is the value of node['nsca']['data_bag_item'].
In our case it is set to data bag "apps" and item to "nsca".

Refer to examples from the "nsca" cookbook: https://github.com/parallels-cookbooks/nsca/tree/master/test/fixtures/data_bags/apps

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

License & Authors

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

yum-epel >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

0.1.2 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.2 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.2 failed this metric

FC064: Ensure issues_url is set in metadata: nsca/metadata.rb:1
FC065: Ensure source_url is set in metadata: nsca/metadata.rb:1
FC066: Ensure chef_version is set in metadata: nsca/metadata.rb:1
FC069: Ensure standardized license defined in metadata: nsca/metadata.rb:1
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.1.2 passed this metric

No Binaries Metric
            

0.1.2 passed this metric

Testing File Metric
            

0.1.2 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.2 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 include a tag that matches this cookbook version number