Orphaned Cookbooks?


#1

Hi everyone!

A topic that was discussed at this year’s Chef Community Summit was
the occurrence/problem of orphaned cookbooks.

In the past, the topic of namespacing the community site was
discussed, and I thought it might be prudent to determine the scope of
the problem.

I am trying to aggregate a list of cookbooks that you believe to be
abandoned/orphaned, and are effectively “squatting” on a cookbook name
that you think is either a “bad” cookbook that is not being
maintained, and that you may have sent patches to or tried to
communicate with the maintainer unsuccessfully.

Here’s an example I have:
scout_agent 0 - I’ve tried to communicate with the maintainer
unsuccessfully, and I’m committed to maintaining this cookbook.

So feel free to respond, either publicly or privately, and I will
collect whatever results I get for the next couple of weeks.

This information may inform future proposals in regards to community
maintenance of cookbooks, but the effort won’t be made unless the
problem can be proven.

Thanks for your time, and hope that your 2013 has started out well!

-Mike Fiedler
e: miketheman@gmail.com
g: @miketheman
t: @mikefiedler


#2

Are you asking only for cookbooks that appear in the
community.opscode.comlisting or any cookbooks living out there in
github land as well?

I will nominate:

I don’t know that I’m qualified to maintain the cookbooks, though I do at
least have a pull request open against the route53 cookbook.

-ben

p.s. sending publicly in case the maintainer of either is on this list and
cries “Hey, that’s mine!” and then accepts my patch. :slight_smile:

On Thu, Jan 3, 2013 at 4:49 PM, Mike miketheman@gmail.com wrote:

Hi everyone!

A topic that was discussed at this year’s Chef Community Summit was
the occurrence/problem of orphaned cookbooks.

In the past, the topic of namespacing the community site was
discussed, and I thought it might be prudent to determine the scope of
the problem.

I am trying to aggregate a list of cookbooks that you believe to be
abandoned/orphaned, and are effectively “squatting” on a cookbook name
that you think is either a “bad” cookbook that is not being
maintained, and that you may have sent patches to or tried to
communicate with the maintainer unsuccessfully.

Here’s an example I have:
scout_agent 0 - I’ve tried to communicate with the maintainer
unsuccessfully, and I’m committed to maintaining this cookbook.

So feel free to respond, either publicly or privately, and I will
collect whatever results I get for the next couple of weeks.

This information may inform future proposals in regards to community
maintenance of cookbooks, but the effort won’t be made unless the
problem can be proven.

Thanks for your time, and hope that your 2013 has started out well!

-Mike Fiedler
e: miketheman@gmail.com
g: @miketheman
t: @mikefiedler


#3

Are you asking only for cookbooks that appear in the community.opscode.com
listing or any cookbooks living out there in github land as well?
Let’s start with the ones on the Community Site.

Thanks!
-M

On Thu, Jan 3, 2013 at 9:02 PM, Ben Hartshorne ben@parse.com wrote:

Are you asking only for cookbooks that appear in the community.opscode.com
listing or any cookbooks living out there in github land as well?

I will nominate:

I don’t know that I’m qualified to maintain the cookbooks, though I do at
least have a pull request open against the route53 cookbook.

-ben

p.s. sending publicly in case the maintainer of either is on this list and
cries “Hey, that’s mine!” and then accepts my patch. :slight_smile:

On Thu, Jan 3, 2013 at 4:49 PM, Mike miketheman@gmail.com wrote:

Hi everyone!

A topic that was discussed at this year’s Chef Community Summit was
the occurrence/problem of orphaned cookbooks.

In the past, the topic of namespacing the community site was
discussed, and I thought it might be prudent to determine the scope of
the problem.

I am trying to aggregate a list of cookbooks that you believe to be
abandoned/orphaned, and are effectively “squatting” on a cookbook name
that you think is either a “bad” cookbook that is not being
maintained, and that you may have sent patches to or tried to
communicate with the maintainer unsuccessfully.

Here’s an example I have:
scout_agent 0 - I’ve tried to communicate with the maintainer
unsuccessfully, and I’m committed to maintaining this cookbook.

So feel free to respond, either publicly or privately, and I will
collect whatever results I get for the next couple of weeks.

This information may inform future proposals in regards to community
maintenance of cookbooks, but the effort won’t be made unless the
problem can be proven.

Thanks for your time, and hope that your 2013 has started out well!

-Mike Fiedler
e: miketheman@gmail.com
g: @miketheman
t: @mikefiedler


#4

Hi Peter - can you help me figure out one thing with the same cookbook?

How does chef know which data bag item to use for the server you’re
deploying to?

For instance - the documentation says you need to create a databag named
cassandra and create an item named clusters. Then in there you can create
a hash for each server.

For the life of me, I cant seem to get cassandra.yaml to have the
cluster_name I’m specifying. When the server is provisioned, I can see
ohai has the right value.

Any suggestions?

On Wed, Jan 9, 2013 at 1:01 PM, Peter Norton pn+chef-list@knewton.comwrote:

I’ve got an in-house cassandra cookbook that’s been getting some love
here. It’s the ben black -> infochimps cookbook, with ironfan stuff
removed, and a focus on AWS and using Priam to discover nodes so it works
with chef-solo. I’ll look at releasing it sometime in the near future.

On Wed, Jan 9, 2013 at 12:46 PM, Three Tee threetee@gmail.com wrote:

+1 to this, especially as tools like berkshelf also encourage users to
default to the community site for cookbooks.

On Jan 9, 2013, at 4:58 AM, Cassiano Leal cassianoleal@gmail.com wrote:

Looks good! I’ll have a look at this one and maybe switch to using it.

Either way, I think that the community cookbooks should have a better
management strategy in terms of cookbook usability.

It’s quite daunting for a new user to go around hunting for better
cookbooks on github than the ones in the opscode repo. This was a major
source of anger and frustration for me when I was starting to learn Chef. :slight_smile:


Cassiano Leal

On Wednesday, January 9, 2013 at 10:52, Andrea Campi wrote:

I’ve been using this one with success:
https://github.com/brianbianco/redisio ; every pull request I’ve sent
has been merged in a reasonable time.

On Wed, Jan 9, 2013 at 1:01 PM, Cassiano Leal cassianoleal@gmail.comwrote:

I’ll second the redis-angst as I’m going through it myself.

This [0] seems to be the most usable redis cookbook out there, but it
hasn’t been updated in a while and has to be patched in order to install
the latest version of the redis server.

I’m currently using my own fork of it, but by looking through the pull
requests it’s obvious that there are other people in the same situation.

[0] https://github.com/ctrabold/chef-redis


Cassiano Leal

On Wednesday, January 9, 2013 at 09:58, Mike wrote:

Hey all,

There’s been lackluster response to this.

I currently have this list:

  • route53
  • cassandra
  • node, nodejs, npm - candidates for rollup
  • scout_agent

I know there’s also some redis-angst out there.

-Mike


#5

My fork is older, and doesn’t have this:

https://github.com/infochimps-labs/ironfan-pantry/blob/master/cookbooks/cassandra/recipes/config_from_data_bag.rb

The cassandra.yaml is generated using node[:cassandra] attributes, so you
should dump out node[:cassandra] at that point and see what’s there. Drop
me an email off-list if I can help you with more specifics, OK?

-Peter

On Fri, Mar 1, 2013 at 8:32 PM, Maven User maven.2.user@gmail.com wrote:

Hi Peter - can you help me figure out one thing with the same cookbook?

How does chef know which data bag item to use for the server you’re
deploying to?

For instance - the documentation says you need to create a databag named
cassandra and create an item named clusters. Then in there you can create
a hash for each server.

For the life of me, I cant seem to get cassandra.yaml to have the
cluster_name I’m specifying. When the server is provisioned, I can see
ohai has the right value.

Any suggestions?

On Wed, Jan 9, 2013 at 1:01 PM, Peter Norton pn+chef-list@knewton.comwrote:

I’ve got an in-house cassandra cookbook that’s been getting some love
here. It’s the ben black -> infochimps cookbook, with ironfan stuff
removed, and a focus on AWS and using Priam to discover nodes so it works
with chef-solo. I’ll look at releasing it sometime in the near future.

On Wed, Jan 9, 2013 at 12:46 PM, Three Tee threetee@gmail.com wrote:

+1 to this, especially as tools like berkshelf also encourage users to
default to the community site for cookbooks.

On Jan 9, 2013, at 4:58 AM, Cassiano Leal cassianoleal@gmail.com
wrote:

Looks good! I’ll have a look at this one and maybe switch to using it.

Either way, I think that the community cookbooks should have a better
management strategy in terms of cookbook usability.

It’s quite daunting for a new user to go around hunting for better
cookbooks on github than the ones in the opscode repo. This was a major
source of anger and frustration for me when I was starting to learn Chef. :slight_smile:


Cassiano Leal

On Wednesday, January 9, 2013 at 10:52, Andrea Campi wrote:

I’ve been using this one with success:
https://github.com/brianbianco/redisio ; every pull request I’ve sent
has been merged in a reasonable time.

On Wed, Jan 9, 2013 at 1:01 PM, Cassiano Leal cassianoleal@gmail.comwrote:

I’ll second the redis-angst as I’m going through it myself.

This [0] seems to be the most usable redis cookbook out there, but it
hasn’t been updated in a while and has to be patched in order to install
the latest version of the redis server.

I’m currently using my own fork of it, but by looking through the pull
requests it’s obvious that there are other people in the same situation.

[0] https://github.com/ctrabold/chef-redis


Cassiano Leal

On Wednesday, January 9, 2013 at 09:58, Mike wrote:

Hey all,

There’s been lackluster response to this.

I currently have this list:

  • route53
  • cassandra
  • node, nodejs, npm - candidates for rollup
  • scout_agent

I know there’s also some redis-angst out there.

-Mike


#6

Hey all,

There’s been lackluster response to this.

I currently have this list:

  • route53
  • cassandra
  • node, nodejs, npm - candidates for rollup
  • scout_agent

I know there’s also some redis-angst out there.

-Mike


#7

I’ll second the redis-angst as I’m going through it myself.

This [0] seems to be the most usable redis cookbook out there, but it hasn’t been updated in a while and has to be patched in order to install the latest version of the redis server.

I’m currently using my own fork of it, but by looking through the pull requests it’s obvious that there are other people in the same situation.

[0] https://github.com/ctrabold/chef-redis


Cassiano Leal

On Wednesday, January 9, 2013 at 09:58, Mike wrote:

Hey all,

There’s been lackluster response to this.

I currently have this list:

  • route53
  • cassandra
  • node, nodejs, npm - candidates for rollup
  • scout_agent

I know there’s also some redis-angst out there.

-Mike


#8

I’ve been using this one with success:
https://github.com/brianbianco/redisio ; every pull request I’ve sent has
been merged in a reasonable time.

On Wed, Jan 9, 2013 at 1:01 PM, Cassiano Leal cassianoleal@gmail.comwrote:

I’ll second the redis-angst as I’m going through it myself.

This [0] seems to be the most usable redis cookbook out there, but it
hasn’t been updated in a while and has to be patched in order to install
the latest version of the redis server.

I’m currently using my own fork of it, but by looking through the pull
requests it’s obvious that there are other people in the same situation.

[0] https://github.com/ctrabold/chef-redis


Cassiano Leal

On Wednesday, January 9, 2013 at 09:58, Mike wrote:

Hey all,

There’s been lackluster response to this.

I currently have this list:

  • route53
  • cassandra
  • node, nodejs, npm - candidates for rollup
  • scout_agent

I know there’s also some redis-angst out there.

-Mike


#9

Looks good! I’ll have a look at this one and maybe switch to using it.

Either way, I think that the community cookbooks should have a better management strategy in terms of cookbook usability.

It’s quite daunting for a new user to go around hunting for better cookbooks on github than the ones in the opscode repo. This was a major source of anger and frustration for me when I was starting to learn Chef. :slight_smile:


Cassiano Leal

On Wednesday, January 9, 2013 at 10:52, Andrea Campi wrote:

I’ve been using this one with success: https://github.com/brianbianco/redisio ; every pull request I’ve sent has been merged in a reasonable time.

On Wed, Jan 9, 2013 at 1:01 PM, Cassiano Leal <cassianoleal@gmail.com (mailto:cassianoleal@gmail.com)> wrote:

I’ll second the redis-angst as I’m going through it myself.

This [0] seems to be the most usable redis cookbook out there, but it hasn’t been updated in a while and has to be patched in order to install the latest version of the redis server.

I’m currently using my own fork of it, but by looking through the pull requests it’s obvious that there are other people in the same situation.

[0] https://github.com/ctrabold/chef-redis


Cassiano Leal

On Wednesday, January 9, 2013 at 09:58, Mike wrote:

Hey all,

There’s been lackluster response to this.

I currently have this list:

  • route53
  • cassandra
  • node, nodejs, npm - candidates for rollup
  • scout_agent

I know there’s also some redis-angst out there.

-Mike


#10

+1 to this, especially as tools like berkshelf also encourage users to default to the community site for cookbooks.

On Jan 9, 2013, at 4:58 AM, Cassiano Leal cassianoleal@gmail.com wrote:

Looks good! I’ll have a look at this one and maybe switch to using it.

Either way, I think that the community cookbooks should have a better management strategy in terms of cookbook usability.

It’s quite daunting for a new user to go around hunting for better cookbooks on github than the ones in the opscode repo. This was a major source of anger and frustration for me when I was starting to learn Chef. :slight_smile:


Cassiano Leal

On Wednesday, January 9, 2013 at 10:52, Andrea Campi wrote:

I’ve been using this one with success: https://github.com/brianbianco/redisio ; every pull request I’ve sent has been merged in a reasonable time.

On Wed, Jan 9, 2013 at 1:01 PM, Cassiano Leal cassianoleal@gmail.com wrote:

I’ll second the redis-angst as I’m going through it myself.

This [0] seems to be the most usable redis cookbook out there, but it hasn’t been updated in a while and has to be patched in order to install the latest version of the redis server.

I’m currently using my own fork of it, but by looking through the pull requests it’s obvious that there are other people in the same situation.

[0] https://github.com/ctrabold/chef-redis


Cassiano Leal

On Wednesday, January 9, 2013 at 09:58, Mike wrote:

Hey all,

There’s been lackluster response to this.

I currently have this list:

  • route53
  • cassandra
  • node, nodejs, npm - candidates for rollup
  • scout_agent

I know there’s also some redis-angst out there.

-Mike


#11

I’ve got an in-house cassandra cookbook that’s been getting some love here.
It’s the ben black -> infochimps cookbook, with ironfan stuff removed, and
a focus on AWS and using Priam to discover nodes so it works with
chef-solo. I’ll look at releasing it sometime in the near future.

On Wed, Jan 9, 2013 at 12:46 PM, Three Tee threetee@gmail.com wrote:

+1 to this, especially as tools like berkshelf also encourage users to
default to the community site for cookbooks.

On Jan 9, 2013, at 4:58 AM, Cassiano Leal cassianoleal@gmail.com wrote:

Looks good! I’ll have a look at this one and maybe switch to using it.

Either way, I think that the community cookbooks should have a better
management strategy in terms of cookbook usability.

It’s quite daunting for a new user to go around hunting for better
cookbooks on github than the ones in the opscode repo. This was a major
source of anger and frustration for me when I was starting to learn Chef. :slight_smile:


Cassiano Leal

On Wednesday, January 9, 2013 at 10:52, Andrea Campi wrote:

I’ve been using this one with success:
https://github.com/brianbianco/redisio ; every pull request I’ve sent has
been merged in a reasonable time.

On Wed, Jan 9, 2013 at 1:01 PM, Cassiano Leal cassianoleal@gmail.comwrote:

I’ll second the redis-angst as I’m going through it myself.

This [0] seems to be the most usable redis cookbook out there, but it
hasn’t been updated in a while and has to be patched in order to install
the latest version of the redis server.

I’m currently using my own fork of it, but by looking through the pull
requests it’s obvious that there are other people in the same situation.

[0] https://github.com/ctrabold/chef-redis


Cassiano Leal

On Wednesday, January 9, 2013 at 09:58, Mike wrote:

Hey all,

There’s been lackluster response to this.

I currently have this list:

  • route53
  • cassandra
  • node, nodejs, npm - candidates for rollup
  • scout_agent

I know there’s also some redis-angst out there.

-Mike