On 13.04.2011, at 19:20, Edward Sargisson wrote:
Hi,
Yes - I think that answers the question and I can see what I need to do.
BTW, I meant no criticism of Edmund for the download method in the tomcat6 package - I just wanted to be clear on the reasoning.
criticism as in there-are-no-wrong-questions is always welcome. My reasoning was that I was not satisfied with the tomcat6 package on centos.
I always want to leverage what the os gives me. but if there isn't anything already packaged I tend to go the "this is how it should be installed" route
of the package. I really don't like source compiling install chef recipes either.
In this special case with tomcat, which IS already compiled I does not feel that dirty to install it from the archive. As it is true with installing e.g.
Wordpress from the archive (first which came to mind ..).
After this discussion I again gave the os package install a shot. But again they just give a starting point. I used the tomcat (not tomcat6) cookbook to install
tomcat 6 on a ubuntu box. And I get a tomcat home directory owned by "root:root". So the the next step would be to contact the package
maintainer for this change (which might be just desired by me to have it owned tomcat6:tomcat6) OR use chef for that.
The same is true with installing the mysql jdbc jar files which do not get picked up from tomcat automagically.
Same with the tomcat native stuff.
So in the end I feel better of (in such cases) to maintain my best practice aka cookbook.
cu edi
Thanks,
Edward
On Wed, Apr 13, 2011 at 9:29 AM, Noah Kantrowitz
<
">
> wrote:
The general trend seems to be to have a foo::package and a foo::source recipe in these situations, with the default recipe dispatching to one of them. Would this address your concerns in this case?
--Noah
Haselwanter Edmund <
" target="_blank">
> wrote:
On 13.04.2011, at 17:58, Edward Sargisson wrote:
Hi all,
I'm just starting out with Chef and I have a question about cookbook design.
I've noticed that some cookbooks use the OS packaging system to get what's required while other cookbooks download a binary file.
For example, the tomcat6 package
this happens if there is no "right" choice in the packaging system. at the time I've written the tomcat6 cookbook there was no up-to-date tomcat6 package available for centos.
will get the file from the apache website and install from there while the mysql cookbook will use the package resource.
What guidelines do people use to decide which one to do?
if the package which comes through the packaging system is what you want to have use this one
I personally prefer to use the packaging system and feel uncomfortable installing from a download unless there's something in that version I really need.
me too.
This means I can be confident that what I've installed will work with my system - because the package maintainer and the community have tested it pretty thoroughly and the package will install it according to the OS layout standards.
I'm using Ubuntu but I think my comments apply generally.
Thoughts?
In my case, I'm considering modifying the public tomcat6 cookbook to get what I need via packages.
there is another tomcat cookbook available. it is called tomcat and uses the tomcat package of ubuntu
Thanks,
Edward