I hope that is better now, but it supports Chef ~> 11.0.
If somebody is interesting on collectd cookbook it will be great if you
will try my (It is my first try to write serious cookbook).
Here is major changes:
Added many skeleton files (Gemfile, Berksfile, Rake, Kitchen, etc)
Introduced full testing with rubocop, foodcritic, chefspec,
test-kitchen
Attributes have been converted from symbols to strings
Cookbook by default does not install any plugin
Supported platform for now Debian and Ubuntu
Definition has been removed
Added HWR and many HWP (provider is chosen dynamically by name of the
plugin)
Added possibility to multiply times call collectd_plugin resource
from different recipes or cookbooks. Options are merged!
Cookbook is flexible: if you want to add custom plugin or override
behavior of existing one just define class
Chef::Provider::CollectdPlugin <
Chef::Provider::CollectdPlugin.
Recipe “collectd::_test_plugins” added. You can use it as
example/reference. Also specs are using this recipe for tests
I haven't had time to look at what you've done. But, here at RightScale
we have a fork that added support for CentOS that we haven't gotten
around to contributing back. You may wish to take a look and see if you
can incorporate similar changes into your version:
I hope that is better now, but it supports Chef ~> 11.0.
If somebody is interesting on collectd cookbook it will be great if you
will try my (It is my first try to write serious cookbook).
Here is major changes:
Added many skeleton files (Gemfile, Berksfile, Rake, Kitchen, etc)
Introduced full testing with rubocop, foodcritic, chefspec, test-kitchen
Attributes have been converted from symbols to strings
Cookbook by default does not install any plugin
Supported platform for now Debian and Ubuntu
Definition has been removed
Added HWR and many HWP (provider is chosen dynamically by name of
the plugin)
Added possibility to multiply times call collectd_plugin resource
from different recipes or cookbooks. Options are merged!
Cookbook is flexible: if you want to add custom plugin or override
behavior of existing one just define class
Chef::Provider::CollectdPlugin <
Chef::Provider::CollectdPlugin.
Recipe "collectd::_test_plugins" added. You can use it as
example/reference. Also specs are using this recipe for tests
I hope that is better now, but it supports Chef ~> 11.0.
If somebody is interesting on collectd cookbook it will be great if you
will try my (It is my first try to write serious cookbook).
Here is major changes:
Added many skeleton files (Gemfile, Berksfile, Rake, Kitchen, etc)
Introduced full testing with rubocop, foodcritic, chefspec,
test-kitchen
Attributes have been converted from symbols to strings
Cookbook by default does not install any plugin
Supported platform for now Debian and Ubuntu
Definition has been removed
Added HWR and many HWP (provider is chosen dynamically by name of the
plugin)
Added possibility to multiply times call collectd_plugin resource
from different recipes or cookbooks. Options are merged!
Cookbook is flexible: if you want to add custom plugin or override
behavior of existing one just define class
Chef::Provider::CollectdPlugin <
Chef::Provider::CollectdPlugin.
Recipe "collectd::_test_plugins" added. You can use it as
example/reference. Also specs are using this recipe for tests
@Douglas, I've created task. Not sure I can directly apply this pull
request, but will try to apply changes manually.
@Greg, Yes I saw this repo and it is pretty cool! But there are few moments:
I need a standalone collectd (not client or server mode). Yes, it sends
metrics to graphite directly.
I need enough flexibility. Cookbook should uses default, system way of
installation and provides smart HWRPs. It easy to wrap it or use anywhere.
I need to customize collectd_plugin behavior
Main feature I've implemented is ability to define collectd_plugin anywhere
in any order any times. Here is my case:
I have my-collectd wrapper. By default it installs collectd and some basics
plugins I want (load, memory, users, swap, df, process monitor for
chef-client, push to graphite).
Also I have my-apache cookbook. Here I have collectd_plugin 'apache'. The
same for other services. They automatically adds required plugins. And no
matter in which order I use in run_list:
["recipe[my-collectd]", "recipe[my-apache]"] or ["recipe[my-apache]",
"recipe[my-collectd]"] it works.
Previously, if you say in one cookbook "collectd_plugin 'processes' ..."
then you will be unable to extend this definition from other cookbook. You
have to completely build options manually and define final LWRP only ones.
I hope that is better now, but it supports Chef ~> 11.0.
If somebody is interesting on collectd cookbook it will be great if you
will try my (It is my first try to write serious cookbook).
Here is major changes:
Added many skeleton files (Gemfile, Berksfile, Rake, Kitchen, etc)
Introduced full testing with rubocop, foodcritic, chefspec,
test-kitchen
Attributes have been converted from symbols to strings
Cookbook by default does not install any plugin
Supported platform for now Debian and Ubuntu
Definition has been removed
Added HWR and many HWP (provider is chosen dynamically by name of
the
plugin)
Added possibility to multiply times call collectd_plugin resource
from different recipes or cookbooks. Options are merged!
Cookbook is flexible: if you want to add custom plugin or override
behavior of existing one just define class
Chef::Provider::CollectdPlugin <
Chef::Provider::CollectdPlugin.
Recipe "collectd::_test_plugins" added. You can use it as
example/reference. Also specs are using this recipe for tests