In Puppet 3 there was a need to use absolute
names to prevent issues. Since Puppet 4 everything
is absolute by default which makes this not needed.
We need to change this everywhere so that we can
revert the pin in [1] that now prevents us from
using the latest version of the puppet-lint check
puppet-lint-absolute_classname_check that properly
checks that we dont use absolute names.
[1] https://review.opendev.org/#/c/697742/
Change-Id: I78b74fbeb08be7234189e4d266412fb7fb7a73c0
Removes from upstream Neutron in Train release and will be
removed from puppet-neutron in this [1] commit.
[1] https://review.opendev.org/#/c/658801/
Change-Id: Ica68eacc724dad6207b9f085198f921db0279ef6
Adds testing for the bgp-dragent that is
shipped by neutron-dynamic-routing in
scenario004.
Depends-On: https://review.openstack.org/#/c/586462/
Change-Id: I8998a1a0f0a8e944cd5f836b3cbe568aa99fcedb
keystone is creating default roles for member since [1]. This
is "member" and it's not configurable so we need to switch it
in p-o-i too to avoid conflicting names errors (keystone is not
case sensitive in object names).
[1] https://review.openstack.org/#/c/572243/
Depends-On: Icd91bd27d0c0f375d2e99e9c018d3971fc49ce18
Change-Id: Id838d69e4ace9b2ea6c2a9cc6f8fd079d2115dd6
Ironic removed the 'fake' drivers in [1], this
patch removes it setup in poi, instead set
fake-hardware in enabled_hardware_types.
Also add other ironic, tempest config required by
fake-hardware type.
[1] https://review.openstack.org/#/c/572454/
Depends-On: I47e886f67e51edf8f4cee3ded44496287d2298d4
Change-Id: I7ea51b6bcee0a93dda7ff54fd3388469d14a9ba8
Currently we are setting "DNS.0 = ::1", but ::1 is not a valid
A-Label for IDNA so the certificate is not correct.
Additionally, we are setting wrong value for DNS.0 = 127.0.0.1
in the ipv4 certificate.
Finally, removing issuerAltName from both ipv4 and ipv6 certificates
as they are not needed for the jobs.
New versions of python-cryptography are more strict to check
certificates content and does not allow to have not compliant
DNS names so we need to fix the certificate to bump python-cryptography.
Note that horizont tempest plugin does not support ipaddress SANs based
certificate validation so I'm disablint certificate validation for
dashboard in this patch.
Depends-On: Iea7a4b85ac64572fac0f0ad871649a79fbc1c0f5
Change-Id: Ib519d222e07e26d3683b24359e2f67728cdd8029
This submission will enable L2GW on scenario004
and one of its tempest test.
Change-Id: I87fb7ca3671cf93d6b47ac393e047e1810daf375
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
This submission will enable the BGPVPN API
on scenario004 and one of its tempest test.
Change-Id: I9d7853bedd822a9d182f1c5dcd7db85e7cd59c07
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
If we don't, the default 'all' is used, which means tempest executes all
tests irrespective of whether the setup supports all those extensions,
or not. For example, trunk service plugin is not enabled by the repo;
neither port_security ml2 extension driver is. If a test that requires
any of those features land in tempest repo, the gate will immediately
break. Actually, tempest already has some tests for port_security, but
they are not executed at the moment by the virtue of a special
port_security config option that is False by default. That may change in
the future [1].
It's good practice to explicitly configure the list of extensions that
are known to work for the setup in question.
[1] I471575bdc106e1a6d1ecdb313dbe77b4102d8f15
Change-Id: I323ff03c5798a41de4870ed99e71ed5a9456a6af
Depends-On: I31105600dfd5632ec4341b35ca3e8a13af3bb945
We want to validate compute services with ssh connection, to catch more
issues in our CI, so enable this option which is disabled by default in
Tempest.
Depends-On: I5edc8c2a33c29c64dc2ff49300b550f145415185
Change-Id: Idd07337f936613471227f689e774db21eb2d8477
* TEMPEST_FROM_SOURCE is set to true to install tempest from source.
* Added capability to use tempest rpm
* change the cirros image directory to /tmp/openstack/image
if the image gets firstly downloaded in tempest workspace,
Tempest init will fail to create tempest workspace.
* Create image_dir if not exists.
Change-Id: I349783ace314a3575e93e6c853a7756f0f9b85ac
The gabbi library is needed for tempest and it's not being installed by
the Ubuntu tempest package. So let's add it to try and fixup the tempest
test.
Change-Id: I711543f3706735966b52f5e56b5b9349b6d2cced
Glance registry is not required for the v2 of the API and there are
plans to deprecate it in the glance community. Allow for it to be
disabled in tests.
Change-Id: I89f319f18f4cbda4244e96732a16df81a0f836b0
Configure cinder backup to use swift and test
Change-Id: I9b645b2e7b76e97403b95459578979ec9f53c0b4
Depends-On: I588c9864cd20c75de7caecf733603a3587c34d12
Trove Tempest plugin was fixed upstream.
Also specify db_flavor_ref that is required when the flavor is different
from default value (1).
Closes-Bug: #1612398
Depends-On: Id2d6b9ae571515d90f6232a13a9beecd357703cd
Change-Id: I2153bda14b870a2746d9b20808d8e8ac01b04ee1
Be more granular on what package we deploy for Tempest tests.
Our current CI only test LBaaS and FWaaS, not VPNaaS.
Change-Id: Ic53b462a3bcb9a1329ee8017f72e33f1201c64f1
Depends-On: Ied0881f93a020ba1954334e0c7549c216e6b76b1
* drop workaround to deploy Gabbi from pip, and use RDO package.
* Add gnocchi in the Puppet Tempest interface.
* Add gnocchi tests in the list of tests we want to run.
Change-Id: I51094b28c42f7c64d4357f49d0932e027cbd6310
First try to deploy OpenStack Newton on Ubuntu Xenial.
Depends-On: I2ad1b7ee1b9e3f23e37e4053751ca794e5107e73
Change-Id: I67d9cd9e22742659afd2fe2b1991c3ffd3e15c22
1) Remove usage of verbose in Trove.
2) Rename Tempest parameter.
3) Rename Swift parameter.
4) Update parameters for Heat so we use 'password' auth_plugin.
5) Remove metering_secret, replaced by telemetry_secret.
Change-Id: Id770a7b03323b72ba37317e48085d9c15f106bc1
Do not merge, testing with v3 auth
* Deploy Mistral on scenario003
* Run Tempest tests for Mistral
* Bump repo to recent RDO repo that contains a fix in Mistral to make
Tempest tests working.
Change-Id: Ia43427cc207ee5b7b95e9610f06a568992fb58cd
puppet-zaqar is freshly new and we want to test it.
* configure mongodb replicaset (required for zaqar): 'openstack'.
* deploy zaqar on scenario002 with mongodb backend.
* configure tempest to test zaqar.
* run TestManageQueue tempest tests in tempest.
Note about TestManageQueue:
Zaqar does not maintain Tempest tests, and run their own functional
testing tools. api.messaging.test_queues tests are known to work, so
they will be the only tests run in our CI to validate Zaqar is working.
Note:
* SSL does not work out of the box, we need to add support for WSGI
deployment with Apache, but Zaqa does not provide WSGI app, it's in
their roadmap.
* IPv6 binding on default wsgi does not work, so using IPv4 now.
Change-Id: I1aa563f37aa7a231b2218f79b72c73c668d968f3
We want to run Tempest tests for a maximum of projects we're testing.
Tests are moving from Tempest tree to projects tree.
It takes care of installing tempest-lib which is required system wide to
run Tempest plugin tests.
To run tests from projects tree, we need to run tox with -eall-plugin
option.
This patch aims to change the way we run tox.
It also set manage_tests_packages to True so puppet-tempest will take
care of packaging dependencies required to run Tempest plugins tests in
RDO.
Depends-On: Iac9a57c2ba006bb2a660d2b54ee05bbe68125abf
Depends-On: I8f26968b5b817ffbb9f4dc4a0cb19ca0a1ef7d3d
Change-Id: I0942a7c9456d18528a2d84e143ae056973a7674f
This patch enables SSL by default on scenario003 for both Ubuntu &
CentOS7, like it's done for scenario001 and 002.
Note: we don't enable SSL for Sahara because of:
https://bugs.launchpad.net/sahara/+bug/1565082
Change-Id: I7e25b8acaeda2fc51a1a83b3a3aae0c89f332323
* Deploy Self-Signed Certificates for both IPv6 & IPv4 deployments.
* Disable IPv6 for RabbitMQ now, for SSL reasons, will be enabled again
later in a next iteration.
* Deploy Ironic API under WSGI instead of eventlet.
* Switch Glance API, Ironic API and Keystone to SSL.
* Configure Tempest with SSL endpoints when needed.
* Reduce the Ironic tests because of [1].
[1] https://bugs.launchpad.net/ironic/+bug/1554237
Note #1: puppet-swift, and puppet-cinder will require some work to support SSL, so it's not
implemented in this patch.
Note #2: we don't enable SSL for Neutron because of
https://bugs.launchpad.net/neutron/+bug/1514424
Change-Id: Ib2b5289b6f5e82f43cf60dee3152b2c2ddd5a014
This patch enables robust and complete testing of a compute scenario
where RBD is used for Cinder and Nova.
* Allow cinder.pp and nova.pp to configure RBD backend.
* Switch scenario001 to run Cinder and Nova with RBD backend.
* Update README with more documentation about Cinder & Nova backends.
* Configure volume_clear option to 'none' so volumes are quickly
deleted.
* Enable rbd_default_features to 15 to increase ceph performances.
* Increase compute build_interval in Tempest to 60s, useful for
Bootfromvolume test where instance deletion can take time with RBD
backend.
Depends-On: I69a7d40e7d1847be06a843986ace4f0602272fe1
Depends-On: I7302b89da5a995e779ec349ab0c0f519c69a3a98
Depends-On: Ic410cb66e7620b6ca6acbea38360d8dd890000c9
Change-Id: I5c8d9cf2ff8fc361553b3eed73b697ad87170434
* Create manifest to deploy Ironic services with 'fake' driver.
* Add bits to tempest class to enable the service.
* Update README.
* Add api.baremetal tests so we actually test Ironic.
Depends-On: I93fd4740d09b0c7e926c4dba7a7602f4d295d2ea
Depends-On: I01c83a6daa3909d4d9b1cb559836b7b5e54c7c7e
Change-Id: Ice03be261e687af43e677a9f60a1cc3c79acdf8b
Create manifests for each project and include them in the right
fixtures manifests, so we can reduce the code and avoid dupplicated
puppet manifests.
Change-Id: I66a98691b3014998f4c2529d2e3389ef1cbcc5f4
