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
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
- 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
- Switched default linter to cookstyle
- Renamed rake tasks to better conform with Chef conventions
Change-Id: If9ef1641600ca2d4bea1e3b538304dd2f1d3651f
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
- 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
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 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
Ghanshyam Mann