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: If366dff9394f416b0704bea89ae50c1c472606bf
blueprint: rakefile
Added grizzly rabbbit HA functionality, and switched to the
new mq attributes. Attributes were updated to allow global
and local overrides.
Change-Id: I10f92932fbe1bd256c5a6e10cd357a8ac5e5f1e0
This is a much clearer way to test LWRPs are executed with
the proper options. The previous approach was hacky, and
relied upon too much stubbing and ruby magik. Also, updated
to berkshelf 2.0 where Berksfile.lock is respected. This
is necessary for berkshelf to lock to the proper cookbook
deps in openstack's CI system.
Change-Id: I21c1c000581f2d3c94ff2f9628f0cea0f6536013
* Updates the attributes to align with openstack-common and
the other AT&T-standardized OpenStack cookbooks
* Splits the single server recipe out into recipes for
common, api, setup, volume and scheduler so that nodes
can get the Cinder API, Cinder Scheduler and/or Cinder Volume
service installed separately
* Pull in the isci and tgt packages, matching RCBOps volume recipe