Closed mwrock closed 7 years ago
Hey @mwrock -- this is great. I don't use Couchbase anymore (Chef doesn't use it) but I'm happy to take the contribution as others might find it useful.
I'd definitely like to see this PR broken up into features and if we could leave testing as Vagrant, that would be the lowest common denominator for everyone. The join
action is something folks have been asking for for a while, so I think that's the most valuable & where I'd start.
Awesome. Will send this stuff on once I get some cycles.
@juliandunn sentiment seconded
+1
Was wondering the status on this?
This branch has conflicts that must be resolved Use the command line to resolve conflicts before continuing. Conflicting files .gitignore .kitchen.yml attributes/server.rb files/default/test/server_test.rb libraries/client.rb recipes/server.rb templates/default/setup.iss.erb
I forked this cookbook to illustrate how one might use test-kitchen to perform multi-node testing. See http://www.hurryupandwait.io/blog/multi-node-testing-with-test-kitchen-and-docker. I made several changes that I'd like to submit back. The changes are included in this PR however I assume you would prefer this PR to be broken up. Thats totally cool but I thought I'd at least submit this initial PR to see if there was general interest.
Here is what is included:
netstat
since many docker base images do not include net tools. I think this check is unnecessary anyways considering that an HTTP check is later performed..kitchen.yml
to use docker for all linux platformsjoin
action to the cluster resource so that one may add nodes to a cluster.Might be a couple weeks before I get time to send propper PRs but I have fixed up all unit tests and added tests here where appropriate and I have also added Kitchen tests to cover multinode scenarios.
Please feel free to comment if there are items you'd rather not take. For example maybe you want to keep everything testing in vagrant.
Thanks!