Graphite cookbook release and breaking changes


#1

Hi Chefs!

In the near future we’ll be releasing a significantly different version of
the graphite cookbook.

This change is a long time coming and some of you may have noticed that
it’s been sitting around on a branch (
https://github.com/hw-cookbooks/graphite/tree/teh-futur) for some time now.
While there’s always refinements to be made it’s been in production use at
a few sites and is ready to be merged to master.

This change will move the cookbook to a library style cookbook and require
your own custom wrapper cookbook to make use of it. Overall we think this
fits much better with the many ways graphite can be deployed., but is
definitely a breaking change from the current cookbook.

Further details are here: https://github.com/hw-cookbooks/graphite/pull/147

Example wrapper usage can be found here:
https://github.com/hw-cookbooks/graphite/tree/teh-futur/example

We’ll make sure to bump the version to 1.0.0 prior to merging so for anyone
currently using the cookbook be sure to pin things to the current version,
0.4.8, if you’re not doing so already.

As always, we love feedback so please ask related questions for PR 147 on
github or irc.


Sean | webframp


#2

Very much looking forward to this. Thanks for all the hard work!

On Aug 13, 2014, at 9:21 PM, Sean Escriva sean.escriva@gmail.com wrote:

Hi Chefs!

In the near future we’ll be releasing a significantly different version of the graphite cookbook.

This change is a long time coming and some of you may have noticed that it’s been sitting around on a branch (https://github.com/hw-cookbooks/graphite/tree/teh-futur) for some time now. While there’s always refinements to be made it’s been in production use at a few sites and is ready to be merged to master.

This change will move the cookbook to a library style cookbook and require your own custom wrapper cookbook to make use of it. Overall we think this fits much better with the many ways graphite can be deployed., but is definitely a breaking change from the current cookbook.

Further details are here: https://github.com/hw-cookbooks/graphite/pull/147

Example wrapper usage can be found here: https://github.com/hw-cookbooks/graphite/tree/teh-futur/example

We’ll make sure to bump the version to 1.0.0 prior to merging so for anyone currently using the cookbook be sure to pin things to the current version, 0.4.8, if you’re not doing so already.

As always, we love feedback so please ask related questions for PR 147 on github or irc.


Sean | webframp


#3

I welcome improvements and thank you guys for putting the time and effort
into this :slight_smile:

However I have one thing I don’t quite understand about Chef cookbooks -
the effort of making community cookbooks require a wrapper cookbook.

I honestly just want to include a recipe in a role or runlist and have it
do something simple by default. Like what a default
nginx/mysql/graphite/haproxy/etc setup would do if you’d install one from a
package.

I understand that writing library-style cookbooks is a lot more powerful
from the code perspective, but I’d be happy to see one (or a few)
“ready-to-use” recipes included which I can just begin using without having
to write a new recipe myself.

Just a thought… isn’t really limited to graphite cookbook in particular.

On Wed, Aug 13, 2014 at 7:02 PM, Tony Burns tabolario@gmail.com wrote:

Very much looking forward to this. Thanks for all the hard work!

On Aug 13, 2014, at 9:21 PM, Sean Escriva sean.escriva@gmail.com wrote:

Hi Chefs!

In the near future we’ll be releasing a significantly different version of
the graphite cookbook.

This change is a long time coming and some of you may have noticed that
it’s been sitting around on a branch (
https://github.com/hw-cookbooks/graphite/tree/teh-futur) for some time
now. While there’s always refinements to be made it’s been in production
use at a few sites and is ready to be merged to master.

This change will move the cookbook to a library style cookbook and require
your own custom wrapper cookbook to make use of it. Overall we think this
fits much better with the many ways graphite can be deployed., but is
definitely a breaking change from the current cookbook.

Further details are here:
https://github.com/hw-cookbooks/graphite/pull/147

Example wrapper usage can be found here:
https://github.com/hw-cookbooks/graphite/tree/teh-futur/example

We’ll make sure to bump the version to 1.0.0 prior to merging so for
anyone currently using the cookbook be sure to pin things to the current
version, 0.4.8, if you’re not doing so already.

As always, we love feedback so please ask related questions for PR 147 on
github or irc.


Sean | webframp


Best regards, Dmitriy V.


#4

I haven’t looked at the new graphite cookbook but I was pretty happy with
the current one(except that graphite needs to start from /opt/graphite/bin
instead of /etc/init.d/ for some reason, so reboots would break it?). OOTB
it had graphite running, then I just created a super basic wrapper recipe
to override some attributes before including the graphite recipe when I was
ready to customize some stuff. I did view the changes to the new version a
few months back, but I just don’t see myself moving away from the current
version. That’s probably just the tragic story of most cookbooks though;
I’m loath to upgrade anything because it just means fixing breaking changes
to get right back to where I was :expressionless:

-Greg

On Thu, Aug 14, 2014 at 7:10 PM, DV vindimy@gmail.com wrote:

I welcome improvements and thank you guys for putting the time and effort
into this :slight_smile:

However I have one thing I don’t quite understand about Chef cookbooks -
the effort of making community cookbooks require a wrapper cookbook.

I honestly just want to include a recipe in a role or runlist and have it
do something simple by default. Like what a default
nginx/mysql/graphite/haproxy/etc setup would do if you’d install one from a
package.

I understand that writing library-style cookbooks is a lot more powerful
from the code perspective, but I’d be happy to see one (or a few)
“ready-to-use” recipes included which I can just begin using without having
to write a new recipe myself.

Just a thought… isn’t really limited to graphite cookbook in particular.

On Wed, Aug 13, 2014 at 7:02 PM, Tony Burns tabolario@gmail.com wrote:

Very much looking forward to this. Thanks for all the hard work!

On Aug 13, 2014, at 9:21 PM, Sean Escriva sean.escriva@gmail.com wrote:

Hi Chefs!

In the near future we’ll be releasing a significantly different version
of the graphite cookbook.

This change is a long time coming and some of you may have noticed that
it’s been sitting around on a branch (
https://github.com/hw-cookbooks/graphite/tree/teh-futur) for some time
now. While there’s always refinements to be made it’s been in production
use at a few sites and is ready to be merged to master.

This change will move the cookbook to a library style cookbook and
require your own custom wrapper cookbook to make use of it. Overall we
think this fits much better with the many ways graphite can be deployed.,
but is definitely a breaking change from the current cookbook.

Further details are here:
https://github.com/hw-cookbooks/graphite/pull/147

Example wrapper usage can be found here:
https://github.com/hw-cookbooks/graphite/tree/teh-futur/example

We’ll make sure to bump the version to 1.0.0 prior to merging so for
anyone currently using the cookbook be sure to pin things to the current
version, 0.4.8, if you’re not doing so already.

As always, we love feedback so please ask related questions for PR 147 on
github or irc.


Sean | webframp


Best regards, Dmitriy V.


#5

Completely agree DV!
Em 14/08/2014 04:11, “DV” vindimy@gmail.com escreveu:

I welcome improvements and thank you guys for putting the time and effort
into this :slight_smile:

However I have one thing I don’t quite understand about Chef cookbooks -
the effort of making community cookbooks require a wrapper cookbook.

I honestly just want to include a recipe in a role or runlist and have it
do something simple by default. Like what a default
nginx/mysql/graphite/haproxy/etc setup would do if you’d install one from a
package.

I understand that writing library-style cookbooks is a lot more powerful
from the code perspective, but I’d be happy to see one (or a few)
“ready-to-use” recipes included which I can just begin using without having
to write a new recipe myself.

Just a thought… isn’t really limited to graphite cookbook in particular.

On Wed, Aug 13, 2014 at 7:02 PM, Tony Burns tabolario@gmail.com wrote:

Very much looking forward to this. Thanks for all the hard work!

On Aug 13, 2014, at 9:21 PM, Sean Escriva sean.escriva@gmail.com wrote:

Hi Chefs!

In the near future we’ll be releasing a significantly different version
of the graphite cookbook.

This change is a long time coming and some of you may have noticed that
it’s been sitting around on a branch (
https://github.com/hw-cookbooks/graphite/tree/teh-futur) for some time
now. While there’s always refinements to be made it’s been in production
use at a few sites and is ready to be merged to master.

This change will move the cookbook to a library style cookbook and
require your own custom wrapper cookbook to make use of it. Overall we
think this fits much better with the many ways graphite can be deployed.,
but is definitely a breaking change from the current cookbook.

Further details are here:
https://github.com/hw-cookbooks/graphite/pull/147

Example wrapper usage can be found here:
https://github.com/hw-cookbooks/graphite/tree/teh-futur/example

We’ll make sure to bump the version to 1.0.0 prior to merging so for
anyone currently using the cookbook be sure to pin things to the current
version, 0.4.8, if you’re not doing so already.

As always, we love feedback so please ask related questions for PR 147 on
github or irc.


Sean | webframp


Best regards, Dmitriy V.


#6

This is awesome. Hugely appreciative of the work you’ve put in, this is going to really simplify the provisioning and composition of new graphite buildouts.

On August 13, 2014 at 8:22:37 PM, Sean Escriva (sean.escriva@gmail.com) wrote:

Hi Chefs!

In the near future we’ll be releasing a significantly different version of the graphite cookbook.

This change is a long time coming and some of you may have noticed that it’s been sitting around on a branch (https://github.com/hw-cookbooks/graphite/tree/teh-futur) for some time now. While there’s always refinements to be made it’s been in production use at a few sites and is ready to be merged to master.

This change will move the cookbook to a library style cookbook and require your own custom wrapper cookbook to make use of it. Overall we think this fits much better with the many ways graphite can be deployed., but is definitely a breaking change from the current cookbook.

Further details are here: https://github.com/hw-cookbooks/graphite/pull/147

Example wrapper usage can be found here: https://github.com/hw-cookbooks/graphite/tree/teh-futur/example

We’ll make sure to bump the version to 1.0.0 prior to merging so for anyone currently using the cookbook be sure to pin things to the current version, 0.4.8, if you’re not doing so already.

As always, we love feedback so please ask related questions for PR 147 on github or irc.


Sean | webframp