move from bundler to chefdk

- deprecated Gemfile
- updated Rakefile to use chef exec instead of bundle exec
- updated TESTING.md

Change-Id: Iac4f7c1145090a265588e235030f44cde967f704

Gemfile

@@ -1,3 +1,7 @@
+## THIS GEMFILE IS DEPRECATED AND WILL BE REMOVED AFTER THE NEXT RELEASE
+## THERE WON'T BE ANY UPDATES TO THIS FILE DURING THIS RELEASE CYCLE
+## WE SWITCHED TO CHEFDK AS THE BUNDLE FOR THE NEEDED GEMS
+
 source 'https://rubygems.org'
 
 gem 'chef', '~> 11.18.6'

Rakefile

@@ -2,32 +2,25 @@ task default: ["test"]
 
 task :test => [:lint, :style, :unit]
 
-task :bundler_prep do
-  mkdir_p '.bundle'
-  sh %{bundle install --path=.bundle --jobs 1 --retry 3 --verbose}
+task :berks_prep do
+  sh %{chef exec berks vendor}
 end
 
-task :berks_prep => :bundler_prep do
-  sh %{bundle exec berks vendor}
+task :lint do
+  sh %{chef exec foodcritic --epic-fail any --tags ~FC003 --tags ~FC023 .}
 end
 
-task :lint => :bundler_prep do
-  sh %{bundle exec foodcritic --epic-fail any --tags ~FC003 --tags ~FC023 .}
-end
-
-task :style => :bundler_prep do
-  sh %{bundle exec rubocop}
+task :style do
+  sh %{chef exec rubocop}
 end
 
 task :unit => :berks_prep do
-  sh %{bundle exec rspec --format documentation}
+  sh %{chef exec rspec --format documentation}
 end
 
 task :clean do
   rm_rf [
-    '.bundle',
     'berks-cookbooks',
-    'Gemfile.lock',
     'Berksfile.lock'
   ]
 end

TESTING.md

@@ -1,38 +1,18 @@
 # Testing the Cookbook #
 
-This cookbook uses [bundler](http://gembundler.com/) and [berkshelf](http://berkshelf.com/) to isolate dependencies.
-
-## Using Rake ##
-
-Make sure you have `ruby 1.9.x`, `bundler`, `rake`, build essentials and the header files for `gecode` installed before continuing. Make sure that you're using gecode version 3. More info [here](https://github.com/opscode/dep-selector-libgecode/tree/0bad63fea305ede624c58506423ced697dd2545e#using-a-system-gecode-instead).
+This cookbook uses [chefdk](https://downloads.chef.io/chef-dk/) and [berkshelf](http://berkshelf.com/) to isolate dependencies. Make sure you have chefdk and the header files for `gecode` installed before continuing. Make sure that you're using gecode version 3. More info [here](https://github.com/opscode/dep-selector-libgecode/tree/0bad63fea305ede624c58506423ced697dd2545e#using-a-system-gecode-instead). For more detailed information on what needs to be installed, you can have a quick look into the bootstrap.sh file in this repository, which does install all the needed things to get going on ubuntu trusty. The tests defined in the Rakefile include lint, style and unit. For integration testing please refere to the [openstack-chef-repo](https://github.com/stackforge/openstack-chef-repo).
 
 We have three test suites which you can run either, individually (there are three rake tasks):
 
-    $ rake lint
-    $ rake style
-    $ rake unit
+    $ chef exec rake lint
+    $ chef exec rake style
+    $ chef exec rake unit
 
 or altogether:
 
-    $ rake test
+    $ chef exec rake
 
-The `rake` tasks will take care of installing the needed gem dependencies and cookbooks with `berkshelf`.
-
-## Using Berkshelf directly ##
-
-``Rake`` simplifies the use of ``berkshelf``, you can still use ``berkshelf`` directly but it will require more substantial efforts:
-
-To setup the dependencies:
-
-    $ bundle install --path=.bundle # install gem dependencies
-    $ bundle exec berks vendor .cookbooks # install cookbook dependencies and create the folder .cookbooks
-
-To run the tests:
-
-    $ export COOKBOOK='openstack-compute'
-    $ bundle exec foodcritic -f any -t ~FC003 -t ~FC023 .cookbooks/$COOKBOOK
-    $ bundle exec rubocop .cookbooks/$COOKBOOK
-    $ bundle exec rspec --format documentation .cookbooks/$COOKBOOK/spec
+The `rake` tasks will take care of installing the needed cookbooks with `berkshelf`.
 
 ## Rubocop  ##
 
@@ -47,4 +27,4 @@ To run the tests:
 
 ## Chefspec
 
-[ChefSpec](https://github.com/sethvargo/chefspec/) is a unit testing framework for testing Chef cookbooks. ChefSpec makes it easy to write examples and get fast feedback on cookbook changes without the need for virtual machines or cloud servers.
+[ChefSpec](https://github.com/sethvargo/chefspec) is a unit testing framework for testing Chef cookbooks. ChefSpec makes it easy to write examples and get fast feedback on cookbook changes without the need for virtual machines or cloud servers.