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

druid (2) Versions 0.0.2

Installs/Configures druid

Berkshelf/Librarian
Policyfile
Knife
cookbook 'druid', '~> 0.0.2'
cookbook 'druid', '~> 0.0.2', :supermarket
knife cookbook site install druid
knife cookbook site download druid
README
Dependencies
Quality 33%

Druid Cookbook

Installs and configures the Druid real-time analytics system

Requirements

This cookbook is for Debian-based linux systems. It has been tested with Ubuntu using Vagrant as well as Amazon's AWS OpsWorks. Services are managed via upstart.

Recipes

There is one recipe per Druid service:

  • broker
  • coordinator
  • historical
  • middleManager
  • overlord
  • peon (rarely needed)
  • realtime
  • router (upcoming service)

Attributes

Most attributes are simply passed through to Druid's runtime.properties files. See attributes/default.rb for the others.

<table> <tr> <th>Key</th> <th>Description</th> </tr> <tr> <td><tt>['druid']['properties'][<i>property name</i>]</tt></td> <td>properties which apply to all services</td> </tr> <tr> <td><tt>['druid'][<i>service name</i>]['properties'][<i>property name</i>]</tt></td> <td>properties which apply to one service</td> </tr> </table>

Usage

See the druid-example cookbook for a working example.

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 and Authors

Copyright 2014 N3TWORK, Inc.<br> Licensed under Apache 2.0<br> Written by Yuval Oren (yuval@n3twork.com)

Collaborator Number Metric
            

0.0.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.0.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.0.2 failed this metric

FC064: Ensure issues_url is set in metadata: druid/metadata.rb:1
FC065: Ensure source_url is set in metadata: druid/metadata.rb:1
FC066: Ensure chef_version is set in metadata: druid/metadata.rb:1
FC067: Ensure at least one platform supported in metadata: druid/metadata.rb:1
FC069: Ensure standardized license defined in metadata: druid/metadata.rb:1
Run with Foodcritic Version 12.2.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.0.2 passed this metric

No Binaries Metric
            

0.0.2 passed this metric

Publish Metric
            

0.0.2 passed this metric

Supported Platforms Metric
            

0.0.2 failed this metric

druid should declare what platform(s) it supports.

Testing File Metric
            

0.0.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.0.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