The bind cookbook has been migrated to the Sous Chefs and a new release has
finally been done which removes the need to have this in the pointer (which is
now broken).
In addition, update cacert which is shipped in the python requests package on
RHEL to work around expired LetsEncrypt root certificate.
Depends-On: https://review.opendev.org/813719
Change-Id: Id537867e47ed54c7028abf7037b251077e57de64
Signed-off-by: Lance Albertson <lance@osuosl.org>
This provides some updates so that this cookbook can be run for
individual cookbooks depending on whether or not various services are
enabled or not. This is useful if you're wanting to test just keystone,
and don't need glance or nova just to do that.
Some other changes:
- Update catalog_type for volume to 'volumev3' which matches what we
provide (We may want to change this back to 'volume' at some point).
- Create orchestration recipe to assist with testing heat.
- Create dns recipe to assist with testing designate.
- Remove unused cookbook dependencies for compute, block-storage and
identity. These should get pulled in automatically with how we setup
the test environment in openstack-chef.
- Blacklist
tempest.api.compute.servers.test_create_server.ServersTestBootFromVolume
test from running due to an issue with our cinder environment.
Change-Id: I0eb2247f163132ef343bbcf6f4cc80326b9704d9
Also update the location of the openstackclient cookbook and make it
possible to test patches there as dependencies, too.
Change-Id: I19894b6f71d2a9aaf2ad0b7d93728fee862eb93c
- implemented foodcritic and cookstyle corrections
- switched Tempest installation back to packages since it is now fresh enough for use
- deprecated node.foo.bar method access for node['foo']['bar'] bracket syntax
- removed calls to GitHub for Tempest
- moved apt package_overrides to common cookbook
Implements blueprint modern-chef
Change-Id: Ia315e51d9ef3fd4677b65074cd7f18a47669208d
Depends-On: I5c5371eed12b282a527576822b270cce8b0e76a7
- Now use cookbook-openstackclient to create endpoints role service and
user
- added domain creation and access granting
- edited values to work with identity_v3
- rewrote specs to work again
- edited image_upload to work with domains
Change-Id: I88ea66da9e8c189208d7e69ecc38dcf502d518db
Depends-On: I0f8955f05de9b33711c54b9a198f45018cceb8e1
Depends-On: I2d404a424bd79a6e9b282304e21591fa33a48981
Depends-On: I2f339055883354c6a8a77daa7967ff279c4d18d9
Depends-On: I84f850f32f25a318c3ed3c7337a0dfa6f641a5fe
* Updated berkshelf from 2.0.18 to 3.1.5 in Gemfile
* added supermarket source to Berksfile
* some refactoring of the Berksfile
* removed Gemfile.lock since its not supposed to be in master branches
* also updated chefspec to 4 and foodcritic to 4 (like done some time ago for the other cookbooks)
Change-Id: I787912448337040ccf26a1126d848c76e7148caf
Implements: blueprint update-berkshelf
This first pass gets tempest installed to /opt/tempest, and sets up
necessary users for testing. More work needs to be done on adding
correct configuration to tempest.conf and enabling different features
depending on what exists in the environment. This will most likely
involve exposing everything via different attributes.
Since we checkout master of tempest, the cookbook assumes tempest
will be executed to use a virtual env. This will hopefully safe-guard
us from future package-related issues. Note that at the moment
the python virtual env does NOT build cleanly on RHEL 6.5. According
to devstack, it appears that a number of work-arounds are required to
make tempest run on RHEL 6.5.
Change-Id: I08224d2f4784d2fc041a5806f221e7411d5b813a
Ghanshyam Mann