- Switch to Stein release
- Cookstyle fixes
- Update cookbook etcd to ~> 5.6
- Update README
- Add myself to author list and OSU Copyright
- Properly fix completions recipe and ensure it works
- Create and start the etcd service in the etcd recipe
- Update delivery configuration to exclude integration cookbooks
- Refactor and update RenderConfigFileMatcher to work with newer
ChefSpec. This fixes output which was passing but showing error
messages.
Depends-On: https://review.opendev.org/701027
Change-Id: Iba3eeabe85ab9303147e43eeb550212a46d190f3
- Replace git.openstack.org with opendev.org
- Update some documentation
- Move README.md to README.rst for better rendering
- Drop obsolete bootstrap.sh script
Change-Id: If732a5e840a7080691097e429e692a18f5286db6
- changed the default RDBMS to MariaDB in accordance with install docs[0]
- removed deprecated database, apt and yum cookbooks
- incorporated `database' and MySQL-specific abstractions from database
cookbook
- implemented foodcritic and cookstyle corrections
- deprecated node.foo.bar method access for node['foo']['bar'] bracket syntax
- updated default recipe for core apt resource
- use /etc/apt/apt.conf.d on Ubuntu instead of passing the dpkg overrides as
command line options in every cookbook
[0]: https://docs.openstack.org/install-guide/environment-sql-database.html
Implements blueprint modern-chef
Change-Id: I143e0ed0a2bdd76269fc0c402052696426d96d81
Depends-On: I00e2237cef0c9aa35f78d3ccec04a1c7b9271ce8
Depends-On: I7ee0f5eae4e79e5c70ee8de4a0094a7c34fdd18f
- Bumped chefdk to 1.6.1
- Switched release to pike
- Added is_release attribute for testing, defaults to false
- Added RDO deps repo for testing pre-release packages
- Added ubuntu-cloud proposed repo for testing pre-release packages
- Switched the default linter to cookstyle
- Normalized the banner message
- Dropped pip installation method for python-openstackclient since the
packages are fresh enough
Change-Id: I7a67ba2520b8e44efec6edd8506f96b0e0dc913b
* added exception for cloning the chef-repo unless it exists
which is possible when depending on chef-repo itself
Change-Id: I1451b74b232a80fa5be649f4118e6aea273fc6ca
The sym link was not working, looks like the permissions have
changed a bit. Using sudo to create the sym-link seems to
do the trick. I'm leaviing in the dir outputs for future
debugging.
Change-Id: I9d2dc9fcdd8f21f49da2a7fc35090c60221b80a3
added common integartion task to allow this rake file to be used by other cookbooks
Depends-On: Ie84d5258a4290110df9bf7754eb3dfce7791e223
Depends-On: I6bddae9fc83a5fc133e43a27e96e1a7110c94cfb
Change-Id: I4834e9557b07db05591b78d28ef27a6046e4c0f0
This uses the repo integration task. It also take advantage of the
repo Berksfil REPO_DEV support to pull in the current patch.
Change-Id: I5a0fe1b938f113a922b4a8ea1de9756c47f06dcd
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: I3951f7bf3b474f1b7aab46c16d91a9b431a787bf
blueprint: rakefile
Ghanshyam Mann