Create a role for installing a chef-client implementation instead of
having it hardcoded within the pre playbook.
Create additional jobs running with cinc-client.
Change-Id: Ib6c592f684072f60962c1be5fccff035fd4c3459
- Update some documentation
- Migrate all Markdown to RST for better rendering
- Drop obsolete bootstrap.sh script
- Update tox.ini as for building docs only python3 is supported
Change-Id: I40a7b02e0a83b516dd7b3cccdb3ddbece2996890
Using the chef-client baked into ChefDK is causing issues with the
fog-openstack gem since it is locked in ChefDK. To work around this and
better mimic how this is used in production, switch the integration
tests to installing chef-client instead of ChefDK.
- Split out pre-run playbooks between delivery and integration (keep
ChefDK for delivery)
- Install Chef 14 by default
- Install Berkshelf in Chef
- Install cookstyle which is needed in the Rakefile
- Update command paths so that berkshelf is available with Chef and
ChefDK
- Update ChefDK to 3.2.30 but not higher due to issues with chefspec and
apache2 [1]
- Upgrade fog-openstack gem to work around extraneous warnings to match
cookbook-openstackclient
- Remove unneeded pip downgrade
[1] https://github.com/sous-chefs/apache2/issues/588
Change-Id: I0b0c2eb80dc0d831685cc7f69a1186a6148e6258
Signed-off-by: Lance Albertson <lance@osuosl.org>
Chef Delivery is the command-line interface for workflow capabilities in Chef
Automate and the standard interface that Chef community cookbooks use for
verification.
Change-Id: I72a1775369f955901260173b061f28640055c808
Implements: blueprint deprecate-rakefiles