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: I6e007888e1b37a54628ab5c09e62f636a0b622ed
blueprint: rakefile
Add two new supported service type(orchestration and cloudformation)
to resource, which will be used to create heat service and endpoint.
partially-addresses: blueprint heat-support
Change-Id: I28bb662a9c3e98380e69e0c5c7156065ea0515ec
We now have a helper method `#address_for` to return the
IP of a given interface. Switched out the ohai use
in favor of `#address_for`. Also, updated berkshelf
to 2.x which handles dep resolution correctly. I run
into problems getting berkshelf to lock to the new 0.3.0
openstack-common w/o updating berkshelf.
Change-Id: If5988dc5290ed8d5faa3950c1995f9943d9efe65
Ghanshyam Mann