Removed Spiceweasel

We don't use Spiceweasel anymore, so this is the removal and references
to it.

Change-Id: I966f5043a5180040cf23db7dfc39c96bd49813ab
Tested-by: JJ Asghar <jj@getchef.com>
This commit is contained in:
JJ Asghar 2015-06-29 12:45:16 -05:00
parent f7d1057c6b
commit 81769c8873
3 changed files with 5 additions and 96 deletions

View File

@ -3,7 +3,6 @@ source 'https://rubygems.org'
gem 'chef', '~> 11.18.6'
gem 'dep-selector-libgecode', '~> 1.0.2'
gem 'json', '<= 1.7.7' # chef 11 dependency
gem 'spiceweasel', '~> 2.8.0' # remove after gates move to rake
gem 'berkshelf', '~> 3.2.1'
gem 'hashie', '~> 2.0'
gem 'rubocop', '~> 0.29.1'

View File

@ -1,25 +1,6 @@
# Testing the Openstack Cookbook Repo #
# Testing the Openstack Cookbook Repo
Basic tests are rubucop and Berks. To run these test use:
This cookbook uses [bundler](http://gembundler.com/) and [berkshelf](http://berkshelf.com/) to isolate dependencies. Make sure you have `ruby 1.9.x`, `bundler`, 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).
## Bundle required gems ##
Berkshelf 3.x needs the to use the system gecode 3.x libraries
For ubuntu 12.04 use:
$ sudo apt-get update
$ sudo apt-get install -y libgecode-dev libxml2-dev libxml2 libxslt-dev build-essential
$ USE_SYSTEM_GECODE=1 bundle install --path=.bundle --jobs 1 --retry 3 --verbose
For other platforms use:
$ bundle install --path=.bundle --jobs 1 --retry 3 --verbose
## Vendor the Cookbooks ##
$ bundle exec berks vendor .cookbooks
## Run the Spiceweasel test ##
$ bundle exec spiceweasel infrastructure.yml --debug
```bash
$ chef exec rake
```

View File

@ -1,71 +0,0 @@
berksfile:
options: '--no-freeze --halt-on-frozen'
cookbooks:
roles:
- allinone-compute:
- os-bare-metal:
- os-bare-metal-api:
- os-bare-metal-conductor:
- os-base:
- os-block-storage:
- os-block-storage-api:
- os-block-storage-scheduler:
- os-block-storage-volume:
- os-block-storage-backup:
- os-client:
- os-compute-api:
- os-compute-api-ec2:
- os-compute-api-metadata:
- os-compute-api-os-compute:
- os-compute-cert:
- os-compute-conductor:
- os-compute-scheduler:
- os-compute-setup:
- os-compute-single-controller:
- os-compute-single-controller-no-network:
- os-compute-vncproxy:
- os-compute-worker:
- os-dashboard:
- os-identity:
- os-image:
- os-image-api:
- os-image-registry:
- os-image-upload:
- os-network:
- os-network-dhcp-agent:
- os-network-l3-agent:
- os-network-metadata-agent:
- os-network-openvswitch:
- os-network-server:
- os-object-storage-account:
- os-object-storage-container:
- os-object-storage-management:
- os-object-storage-object:
- os-object-storage-proxy:
- os-object-storage-setup:
- os-ops-caching:
- os-ops-database:
- os-ops-messaging:
- os-orchestration:
- os-orchestration-api:
- os-orchestration-api-cfn:
- os-orchestration-api-cloudwatch:
- os-orchestration-engine:
- os-telemetry:
- os-telemetry-agent-central:
- os-telemetry-agent-compute:
- os-telemetry-agent-notification:
- os-telemetry-alarm-evaluator:
- os-telemetry-alarm-notifier:
- os-telemetry-api:
- os-telemetry-collector:
environments:
- example:
- testing:
data bags:
nodes: