Browse files


  • Loading branch information...
1 parent 8b708c2 commit 8e5ba94c3b1f140beefd58d4ff2d941e7a275ce4 Michael Klishin committed Feb 22, 2013
Showing with 2 additions and 2 deletions.
  1. +2 −2
@@ -13,7 +13,7 @@ doing so for single-server installations won't be difficult.
This cookbook currently provides
* Cassandra 1.1.x via tarballs
- * Cassandra 1.0.x (DataStax Community Edition) via packages.
+ * Cassandra 1.2.x (DataStax Community Edition) via packages.
## Supported OS Distributions
@@ -25,7 +25,7 @@ Ubuntu 11.04, 11.10, 12.04.
Two provided recipes are `cassandra::tarball` and `cassandra::datastax`. The former uses official tarballs
and thus can be used to provision any specific version.
-The latter uses DataStax Debian repository and provisions Cassandra `1.0`.
+The latter uses DataStax Debian repository and provisions Cassandra `1.2`.
## Attributes

4 comments on commit 8e5ba94


Hi @michaelklishin -- I was just trying out this cookbook and noticed the metadata file didn't include a name for the cookbook. Then, I looked and found you were still actively developing (per this recent commit) and figured I'd ask you: what's your recommended way to make use of this cookbook?


@michaelklishin PS -- here's a diff I made locally to get the cookbook working. I can submit a Pull Request if that would be useful, but I figured I might be missing something obvious that I don't understand about how you've constructed the cookbook so I thought I'd ask first.

diff --git a/cassandra/metadata.rb b/cassandra/metadata.rb
index 74cdcd0..acee2e4 100644
--- a/cassandra/metadata.rb
+++ b/cassandra/metadata.rb
@@ -1,6 +1,13 @@
+name             "Cassandra"
 maintainer       "Michael S. Klishin"
 maintainer_email ""
 license          "Apache 2.0"
 description      "Installs/Configures OpsCode Apache Cassandra"
 long_description, ''))
 version          "1.0.0"
+recipe           "cassandra::datastax",                "Uses DataStax Debian repository and provisions Cassandra"
+recipe           "cassandra::tarball",                 "Uses official tarballs and thus can be used to provision any specific version"
+depends          "build-essential"
+depends          "apt"
\ No newline at end of file

Copy it to your cookbooks repo, use it like any other cookbook. As it improves (which you can participate in by submitting pull requests), sync your repo with upstream.


@michaelklishin Got it - I meant more like "is there some reason the recipes aren't defined in the metadata" (my diff above does this). I'll likely fork the repo and our team can send you some PRs! I see you're very active and really appreciate all of your contributions -- really incredible work

Please sign in to comment.