Opscode has recently made efforts to decouple the mysql cookbook from using specifically mysql, so that it can be used as a dependency for drop-in replacements.
I was working on a cookbook to scratch my own itch, and was wondering whether you'd consider accepting a PR to move your own cookbook in that direction. I'm totally willing to do the legwork :)
Here's my repo:
@patcon I'm not familiar with this current initiative. I would certainly be happy to consider it. Can you point me at some reference documentation so I can see what would be involved and how these changes would affect the current project?
haha sorry, no official initiative at all, just trying to remove the chaos of all the cookbooks :)
I suppose the closest thing to real written docs would be the recent CHANGELOG.md in the the mysql cookbook (it should reference all the relevant tickets):
[COOK-1236] - Move package names into attributes to allow percona to free-ride
Also, forgot that this guy was interested in drop-in replacements for mysql too. He might be interested in helping out too:
Maybe we could move discussion into the more general, let's-work-together thread for now?
EDIT: oops, can't close this myself...
@patcon no problem. We'll continue this discussion at customink-webops/percona-install#6.
Hm. Sorry to be a bother, but I guess this is still the best place to discuss the refactoring that would need to happen for the actual dependency. My bad. Reopen?
Just wanted to post that this ticket is the final piece needed in order to have mysql be used in a percona recipe. Still waiting on the merge.
Initial attempt to leverage mysql cookbook. Stuck on complex percona:…
I was hoping to do this without pushing anything onto you, but it seems you've diverged a bit since you forked the mysql cookbook (?). There's lots that's the same, but some that different. Any chance you could take a look when you get the time and see whether you think it's possible to reconcile? (with PR's to the mysql cookbook, or otherwise)
@patcon I'm definitely open to these updates. This cookbook was started from scratch and was not a fork from any existing cookbooks.
I just merged one of your other pull requests and now this can't be automatically merged at the moment. Would you mind rebasing and pushing so I can take a closer look? Thanks!
Oh god, it wasn't ready to merge anyhow :)
It will take a lot of care to merge in the server recipe without disrupting how you're using it, so I'd probably need some help testing it with your setup (and maybe giving advice on whether we could take the mysql cookbook's approach to solving a problem you might have tackled a littler differently).
I'll reroll the in-progress changes though
@patcon any movement on this? I've got another window to look at it with you if you're still interested.
Unfortunately no movement, as my cookbook (in extending the mysql cookbook) solved my needs at the time, and it was always just a personal itch to scratch in backporting the extra features of this cookbook :)
I've commented on a few issues, but my thoughts are that this is the canonical issue that makes sense to work on before duplicating efforts in resolving some of the others. I have no pressing plans to backport, but it's still something I'd like to do when I revisit the depending project
/cc @santiagogil since he was interested in this as well.
This pull request is pretty out of date at this point. I am closing it for now but will re-open if there is any new activity.