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
- Adopt for the use of python3 on Ubuntu
- Use the endpoint_type attribute
- Install recent tempest version
- Make sure to install matching requirements
- Adjust default tempest.conf to work in our minimal scenario
Change-Id: Ib413971c15d11cbb46befda55ffc28f3c16f2a8a
fog-openstack-1.x already appends "auth/tokens" so we no longer need to
do that. In addition, comment out endpoint type until this PR [1] gets
merged and released.
[1] https://github.com/fog/fog-openstack/pull/494
Depends-On: https://review.opendev.org/666176
Change-Id: I929722b032e37970fe74018e609b76c1682e0db9
Signed-off-by: Lance Albertson <lance@osuosl.org>
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>
In order to maintain consistency for pip versions, align pip, wheels,
and setuptools. Use OSA as a basis for consistency between deploy
projects.
Depends-On: I573bd84e1f15b6e9bda8ebb1d8e12fa66970757a
Change-Id: I123508ad8c65805f6d95abe5e592e7e761d63142
In Chef 13+, resource duplication behaves differently. By centralizing
python_runtime to openstack-common, the resource executes once in a
given Chef run, instead of attempting to reinstall python multiple
times.
Change-Id: Ife452a1e21a82c877f4aceb85d768ed2f758e0de
- due to inconsistencies in RDO versus UCA packaging, Tempest performs more
consistently from upstream git
- update cirros references to 0.4.0
Change-Id: I374497db1b602683f1f9c62489f523b18c50266c
Implements: blueprint modern-chef
- 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
This patch removes the openstack_user resource with :grant_domain
action. A user is always created within a specific domain; such a
membership cannot be tacked on later. This resource gave the user the
role intended for their project for the domain (i.e., for the Default
domain instead of for the service project).
We add the domain_name attribute that creates the tempest users in the
desired domain. Note that this change needs a sufficiently recent
openstackclient cookbook -- otherwise the domain_name attribute is
ignored (which does not matter as long as the tempest users are to be
created in the Default domain).
Change-Id: I345826bc3dae80d25b8f8826c63c5914cf1c2db5
This patch removes the role_name when using openstack_user's :create
action (it gets ignored by the target method).
Note that the spec test would still pass if only the line in
identity_registration.rb (but not the test) were changed, because the
code that actually does grant the role to the resource is executed right
after user creation and before any tests check the resource for the
existence of the role_name attribute. In other words: if the argument
were required in a call but only supplied in another call, the spec
tests would not catch it. Something to watch out for.
Change-Id: I92b47cd0156e4146a40ca7be89c102a625b5bdf6
- Switched default linter to cookstyle
- Renamed rake tasks to better conform with Chef conventions
Change-Id: If9ef1641600ca2d4bea1e3b538304dd2f1d3651f
- Style and lint fixes for newer chefdk
- Removed ancient Gemfile
- Rewrote metadata.rb for readability
Change-Id: I7c2950270f88cc9d54de593460009c6741913796
python-dev is not the correct package for RHEL systems and is instead
python-devel. It looks as thought this package is also installed in other places
for Ubuntu/Debian systems so this seems like logical to remove the duplicate
package resource.
Change-Id: Ifb6c439171ed6a65ba67cc6fe8076d2fa42da32d
- Untangle venv dir and git repo
- Install tempest into venv properly
- Install wrapper script to run tempest from venv
- Use latest stable cirros image
Change-Id: If64fd079a8955d417daa76d431959f0335280467
Since the 'scheme' for the identity endpoint is defined as a
node attribute, we can use this value when constructing the auth
URI in the tempest.conf
Closes-Bug: #1650364
Change-Id: Ieaadef347661547cb549870e42e2a0d92c722b8e
- 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
Create and use m1.nano flavor.
Disable volume snapshots.
Use local-net created in repo integration test runs.
Remove python virtualenv package, it contains old setuptools for centos
Change-Id: I42216a174930b17a4771e78c639da54e170a288c
* 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
For automation, there's usually no need to clone the entire
revision history.
Change-Id: I766fc0ef100376578daac985cb7a85a9a07dd6ed
Closes-Bug: #1455240
Now that admin_endpoint, public_endpoint, and internal_endpoint
in the common library are working, these are the changes to use
them in the openstack-integration-test recipes.
No endpoints are created in these recipes, so no new tests
were added.
Change-Id: Ib38c9bf9675e688a8a4de7e7e8e04993eba57911
Partial-Bug: 1412919
This change adds an automated upload of the needed (here just a standard
cirros) images for the tempest integration tests.
Change-Id: I95e8c01703822c4adc6d1fbf369fc6fa1115406b
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