bootstrap script installs testing dependencies on trusty and relies on
common bootstrap.sh in stackforge/cookbook-openstack-common
- fixed mixup in dependency for knife task in Rakefile
- deprecated Gemfile
- updated TESTING.md
blueprint: bootstrap-infra-test-nodes
Change-Id: Ia6e457570fc585874dbf56751c2f8388eb637bbc
Having a Rakefile will allow us to change the actual test commands on
our side rather than relying on changes to the openstack-infra
repository. This should make it a lot faster to change things, but also
easier to test since the jenkins jobs are actually run in this
repository, not the openstack-infra one.
This commit defines the jobs we previously had defined in Jenkins and
uses 'high-level' naming consistently (i.e. lint, style vs. foodcritic,
rubocop).
There is also a :clean task to help with deleting the files generated by
the other jobs.
Also changed foodcritic to run on the source cookbook rather than the
one installed by berks, see
e.g. https://github.com/berkshelf/berkshelf/issues/931#issuecomment-29668369
Change-Id: Id085444027efd90049508abe6a309fed7dfffee8
blueprint: rakefile
* Updated berkshelf from 2.0.18 to 3.1.5 in Gemfile
* added supermarket source to Berksfile
* some refactoring of the Berksfile
* removed Gemfile.lock since its not supposed to be in master branches
* also updated chefspec to 4 and foodcritic to 4 (like done some time ago for the other cookbooks)
Change-Id: I787912448337040ccf26a1126d848c76e7148caf
Implements: blueprint update-berkshelf
This first pass gets tempest installed to /opt/tempest, and sets up
necessary users for testing. More work needs to be done on adding
correct configuration to tempest.conf and enabling different features
depending on what exists in the environment. This will most likely
involve exposing everything via different attributes.
Since we checkout master of tempest, the cookbook assumes tempest
will be executed to use a virtual env. This will hopefully safe-guard
us from future package-related issues. Note that at the moment
the python virtual env does NOT build cleanly on RHEL 6.5. According
to devstack, it appears that a number of work-arounds are required to
make tempest run on RHEL 6.5.
Change-Id: I08224d2f4784d2fc041a5806f221e7411d5b813a
Ghanshyam Mann