Split cookbook into zookeeper and exhibitor cookbooks about zookeeper-cookbook HOT 6 CLOSED

Hey @wolf31o2, I'm probably +1 on this, but I don't think any of us really have the time to tackle it right now. If you want to PR the change, we'd be happy to review it. Thanks!

from zookeeper-cookbook.

OK. I did everything necessary for this, I think.

I am going to open up two PR's and reference this bug in them. One will be against this cookbook/repository. The other is against my new chef-exhibitor repository, which was started as a clone of this one. If you guys approve, I will transfer chef-exhibitor to your organization, so that you can maintain it as you wish.

from zookeeper-cookbook.

I have added @jakedavis and @mwhooker as contributors on wolf31o2/chef-exhibitor and filed evertrue/exhibitor-cookbook#1 to merge the new chef-exhibitor cookbook code to master in that repo. Since you both have full access to the repository, you can transfer it to your organization after merging the PR. 👍

from zookeeper-cookbook.

thought I'd contribute my 2 cents here. I don't maintain this cookbook any more, so it's up to the community to decide the direction.

This cookbook is probably poorly named, but it should be thought of as installing Exhibitor. That it also installs zookeeper is a side effect. I don't believe the two can be layered, ie an exhibitor cb which depends on a zk cookbook, because all exhibitor needs is to extract a zk binary. It doesn't set up logging, configuration, back ups, essentially all the things exhibitor does for us. A decent standalone zk cookbook would need to do all those things.

I'd be +1 to creating a new zk cookbook, maybe called 'zookeeper' or 'zookeeper-bare', and renaming this one as appropriate.

I just hopped over to the mesos repo to see what's going on and to better understand the concerns. It seems like they're requiring the zk cookbook to get access to https://github.com/SimpleFinance/chef-zookeeper/blob/master/libraries/exhibitor_discovery.rb ?

In that case, it might be a good idea to create an exhibitor_client gem which would have that functionality.

If you want to chat more I'd be happy to hop on IRC

from zookeeper-cookbook.

I have a full-blown, does everything set of recipes for zookeeper and zookeeper-server in the community hadoop cookbook, which use the zookeeper packages shipped by Hortonworks or Cloudera. It sets up configuration, logging, etc. This is pretty much a requirement for meeting dependencies when using those platforms and any of their components (HBase, Hive, etc). This is why I didn't split it out into a separate cookbook.

I could split it, if we thought that was the correct approach to take.

The mesos cookbook is only using this for discovery and nothing more, you are correct. A gem would probably be the perfect solution. Unfortunately, my Ruby-fu is nowhere near as good as my Chef-fu, so I wouldn't be much help there.

I am up for any solution, really. Splitting this cookbook, renaming this cookbook, splitting out a new zookeeper cookbook, simply taking over maintenance of the community cookbook, creating a gem, etc. I will do what I can to help, which is why I went ahead and took the initiative to create the split cookbooks.

from zookeeper-cookbook.

This is basically done, I think.

from zookeeper-cookbook.