_Nodetool is not connecting to JMX port._

• Tried with both 9080 and 7199 ports

TODO

• metadata - #1
• lint - #2
• Test coverage
  • unit test: valid config file(s) written
  • integration test: valid package downloaded, service created.
• Get CI working on each commit: run tests, lint code
• tag release for Berkshelf usage

To migrate to this cookbook, we need to be able to transition away from https://github.com/mmi-cookbooks/cassandra-chef, which is currently managing cass at v1.0.5.

• cut release of latest ele-cassandra once feature complete for managing Cassandra >= v1.0.x
• Make chef.git PR
  • update Berksfile
  • set common attributes overrides, match directories and config settings in-place

https://github.com/goru97/ele-cassandra/blob/master/Gemfile#L1-L17

We should lint this code.

$ gem install rubocop
$ rubocop -a

See Foobar's {Gemfile, Rakefile, .rubocop.yml}. Example PR

https://github.com/goru97/ele-cassandra/blob/master/metadata.rb#L2-L3

Since Travis is working, we should wire it up. https://travis-ci.org/goru97/ele-cassandra

Badge to add to readme.md:

[![Build Status](https://travis-ci.org/goru97/ele-cassandra.svg?branch=master)](https://travis-ci.org/goru97/ele-cassandra)

Ensure that there is a webhook/service integration with Travis, so that it builds on each commit/PR

There are various opinions on how to handle this, but MMI cookbooks tend to have any dependencies listed in metadata.rb (apt, python, java, etc) also be listed in Berksfile.

Version locking to a specific cookbook should generally happen in the Berksfile, but not the metadata file.

Since this is going to be a wrapper cookbook, we should have an example test cookbook that exercises the overrides/wrapping logic that we will rely on.

• create cookbook test/fixtures/cookbooks/test/recipes/default.rb
• update kitchen config's run_list to call test:: instead of ele-cassandra::default directly
• update .kitchen.yml config and/or update integration tests to test both installing/configuring cass 1.x and 2.x