Hi, David.
Thanks for looking into this and also thinking about puppet impl.
There's a lot of common ground between these things, so definitely the
issues should at least be linked with your commentary.
An aside, which is related. jclouds has a chef library that handles
things like cookbook queries and automated bootstrap. This is under
continuous integration at CloudBees, but I'm not positive it is being
published to sonatype/central, yet.
Another thing is I'm not sure it has been updated to Chef 10, yet.
Here's some code that might be interesting (note this uses the word
"tag" which should be "group"):
if (any(cookbookVersions, containsRecipe(recipe))) {
List<String> runList = new RunListBuilder().addRecipe(recipe).build();
chefContext.getChefService().updateRunListForTag(runList, tag);
}
bootstrap =
chefContext.getChefService().createClientAndBootstrapScriptForTag(tag);
nodes = computeContext.getComputeService().createNodesInGroup(tag,
1, runScript(bootstrap));
Here's a few links in case you are interested:
https://github.com/jclouds/jclouds-chef/wiki/Quick-Start
https://github.com/jclouds/jclouds-chef/wiki/Compute-Integration
https://github.com/jclouds/jclouds-chef/blob/master/compute/src/test/java/org/jclouds/chef/compute/ChefComputeServiceLiveTest.java
If you are interested in this, I can help dust it off a bit.
-Adrian
On Fri, Aug 26, 2011 at 10:05 AM, David Alves <[email protected]> wrote:
> Hi All
>
> I implemented a chef service.
> The service itself installs ruby and chef-solo and it provides easy to
> use classes to run recipes on the cluster that could be used by other
> services.
>
> I still has some limitations as I only tested in rackspace, the
> implementation for RHEL based distros is still partly missing, and it only
> accepts cookbooks by url (does not fetch them from the central repo yet).
> Nonetheless it might be interesting to someone else.
>
> My question is:
> - I got a sense from the puppet issue that another direction was
> decided in terms of provisioning (e.g., not making chef or puppet common
> services but part of a provisioning abstraction). Did I misunderstand? is it
> still worth attaching the patch to the chef issue?
>
> Cheers
> David Alves
>
