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>
They still haven't released the cookbook however they've updated the release to
3.1.0 which is breaking tests globally. This should resolve the issue.
Depends-On: https://review.opendev.org/c/openstack/openstack-chef/+/800815
Change-Id: Ie196f920b9431392e3c0d44eb97ee6e6685719db
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
- 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: I8fa06acd27a9705cd4eada9214c1fd2d9fed1c1c
The poise-python cookbook is no longer maintained by the upstream maintainer and
is causing lots of issues for the testing pipeline. Instead, install tempest
directly using pip via an execute resource.
Change-Id: I6991581056d6037eb269a6753b1af7e5c2ba7d90
Signed-off-by: Lance Albertson <lance@osuosl.org>
- 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
- Style and lint fixes for newer chefdk
- Removed ancient Gemfile
- Rewrote metadata.rb for readability
Change-Id: I7c2950270f88cc9d54de593460009c6741913796
- 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
* adapted enpoint calls for identity endpoints
* added installation of package curl since its used to upload/guard the upload
of the needed images
Depends-On: I0547182085eed91d05384fdd7734408a839a9a2c
Depends-On: I3262b2e6f792f37c32a446e6567790b82bdd4613
Depends-On: Ifa5a7f4e1df47a3961976e64f654224864c3dcb4
Depends-On: I9ac9eeb29ab27f31394830e4b6f999d5870cc0e4
Depends-On: Idadc97bd7380d6c4f9f6f33d9c6b1215a5f24772
Implements: blueprint cookbook-refactoring
Change-Id: Ifd11f86c576d7dbb709bdd302d41e39e900e1b74
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: I94577ea628c4f6ee81f3f9dadb24309ca7c856a3
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