Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I60726c924991f826c2bb121c43e4ba060e39cdee
- Switched default linter to cookstyle
- Renamed rake tasks to better conform with Chef conventions
Change-Id: I84ebeb49823b022e85dddea9fcdd358b27be50a3
* rabbitmq should use the bind_service attribute instead of the endpoint one,
since these could be different
* adapted rabbitmq clustering attributes
* adapted rabbitmq clustering search to point to recipe instead of role
Depends-On: Iae7e302973805af3cb44be1b29d0e61e76eb0aa0
Implements: blueprint cookbook-refactoring
Change-Id: I08ed288e63422078d9beb36d14fd3c05f1cac435
Add missing gate integration task, but use the one from
Common cookbook to make future updates easy.
Change-Id: I1f2b0737585ae67fe31be6e5e32b94cfb1cbcf61
Cleaned up all the minor rubocop issues, the ones left relate to
complex logic and what I think is a bug in rubocop for nested
vs compact modules/class definitions.
Change-Id: I455efbb3f2c97a21dc16d4a9d7909afeaae18565
- deprecated Gemfile
- updated TESTING and README
- updated Rakefile to use chef exec instead of bundle exec
- replaced Runner by SoloRunner in specs
Change-Id: I5300850921f0af06ba65d3a0f7cf681f609e5868
Several fixes and minor enhancements have gone into the rabbitmq
cookbook. This change allows all 3.12 < 4.0 minors to be picked up.
Change-Id: Ica9f4f5165d6c566bd0bddbf35e66fb5412cf987
bootstrap script installs testing dependencies on trusty and relies on
common bootstrap.sh in stackforge/cookbook-openstack-common
blueprint: bootstrap-infra-test-nodes
Change-Id: I10d7c0006ce12498d5d4c725062b2bd7e91336f5
Add attribute to allow mq cluster to be built on-the-fly rather
than searching nodes.
Change-Id: I1196f95465c0cb21824954feb261b9d1cfd84d26
Closes-Bug: #1412886
Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: Ic4c9f8e39efaa618ad228ff5670d587ce1c31c87
After configuring rabbitmq, restart the service to make configuration
take effect. So during OpenStack deployment, OpenStack services can
connect to rabbitmq successfully.
This workaround will notify rabbitmq-server to restart immediately.
This could be remove once the issue #153 is fixed in rabbit cookbook.
Change-Id: Ib017226f46c7e26429bb26df5b63525e1a98bc82
Closes-Bug: #1380940
Because the rabbit user/pass is stored in internal user database,
no need to push them to rabbit cookbook and expose them in config file.
And configuring rabbitmq default password with clear test is insecure,
so remove it.
Change-Id: Iab95e2dc8cd28b4a45574cf8883f1626dc332db0
Closes-Bug: #1381343
* Consistent email across cookbooks
* Add Contributor.md to help out new folks
* Fix broken link in Testing.md
* Readme tweaks
Change-Id: Ifb0019ec4d1c6427b23f41f59fa3e5cf835fa105
Partial-Bug: #1342735
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: Ie245028db93d6d49eb224747f2c0697c9b6bdcf5
blueprint: rakefile
OpenDev Sysadmins