UCA contains a wrong version on glance-store that is not working when
running Swift backend.
Until they update the package to 0.13.0, we can't test Swift backend
anymore on Trusty.
Change-Id: I43f64f757cc28232f367a4a454b6e499f31c5fe8
Both changes need to happen in the same patchset.
1/ centos/workaround: make sure Keystone installed before RabbitMQ
We currently have an issue in Puppet OpenStack CI where DIB image for
centos7 has a modified version of /etc/login.defs that allows RabbitMQ
to steal UID of OpenStack packaging (Keystone most often).
While we are investigating that, this patch is a workaround to make sure
we first install Keystone and then RabbitMQ, on centos7 systems.
2/ disable telemetry tests on Ubuntu.
UCA is currently updating Ceilometer / Aodh and tests are broken now.
Let's skip them.
Change-Id: Ibfc3988a4de47c9d7d97159e7d1c0e57d64979ae
* Configure RabbitMQ to bind on IPv6 (scenario002 only).
* Configure OpenStack service to connect with an IPv6 on
RabbitMQ (scenario002 only).
Change-Id: I0e4ab4b03d7b1c7bb47c55a751bc04f29292a621
Add config.pp file so we can enable common features (ssl, ipv6, ...)
more easily.
Also move the logic into config.pp so we avoid dupplicated code.
Change-Id: Ib7993ad1fbabfc22dc4ee22f72671303190e39e2
* Manage Puppet OpenStack CI CA and create a common certificate,
auto-signed.
* Configure RabbitMQ to activate SSL on scenario002
* Configure OpenStack services that run on scenario002 to connect to
RabbitMQ using SSL protocol.
Change-Id: Ic435078472ba4e0e0eaf04a64e5bcb7aabba7b3d
This commit adds ability to use swift as glance backend for our
scenario002 integration jobs.
Depends-On: I232536d179db92d82f1c7459a0f13e5ca5576f42
Change-Id: Ie187ffb0e80a623ca2837b0bd0c0502e9d7dc9dd
* Fix README to reflect what is actually deployed.
* Fix AIO scenario to test Cinder, since it's deployed.
Change-Id: I1baf74eb363ef042cf84f6befad42f918251aa0b
Create scenario003 that will install and test:
* keystone/nova/neutron/glance
* trove (moved from scenario001)
* horizon/heat/sahara (moved from scenario002)
Change-Id: I39870bbac6f2f9a050f85772d1fb0f6ac839e410
scenario003 is going to be a scenario gated in OpenStack Infra.
It was created to be a AIO scenario, for our testers, so let's rename it
to scenario-aio.
In a further iteration, scenario003 will be a scenario used by our CI.
Change-Id: I53852757d013abfae10e5f4afd41ddbb18da3b03
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
* Allow glance.pp to configure RBD backend.
* Switch scenario001 to run Glance with RBD backend.
* Update README with more documentation about Glance backends.
Change-Id: Ib2dd8a83b5b6a3c39030c44f5e6a0ae7db31c12c
Some services (like Zaqar) require MongoDB in place to be tested.
We plan to test Zaqar soon, when the Puppet module will be finished.
So this patch is a first iteration by deploying MongoDB.
It also bump the version of puppetlabs-mongodb to use latest release
(0.12).
Change-Id: I408049e658e1b7466dfce9dc565480b538656230
* Deploy Gnocchi services
* Create default archive policy and archive policy rule
* Configure Aodh with Gnocchi which is used to evaluate the alarms for threshold
Note: Tempest does not fully support Gnocchi yet.
* test_alarming_api will work (Aodh) with Gnocchi
* test_telemetry_notification_api will not work (Ceilometer) with
Gnocchi. That's why we don't configure Ceilometer to use Gnocchi
dispatcher.
Depends-On: I4ed26d3e294e82c383afc443914b0d7bb1906e46
Depends-On: Ib818b5ae4fa301c6c496fe800ae45c9b0a73222c
Change-Id: I32e5f80e4eb8a5cd8fc07798aaf6d710332fcdda
* 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
By default, repositories will be managed by puppet through
manifests/repos.pp.
If someone wants to set up different repositories outside
of puppet entirely, he can "export MANAGE_REPOS=false" and
run_tests will not run repos.pp.
Change-Id: I3a09a2be1d2a064e784ed24f189fec41476330d9
In 6d26ea258fdfa5677c99f107eace9936a8e168c0 we wanted to do aregulart
clone of tempest and we made sure the path was /tmp/openstack/tempest -
but we missed to update the path in ::tempest Puppet class.
This patch fix it.
Change-Id: Ie0bc6c6ad887898234870d44b77a80d4b65a5419
Aodh is the new service that replaces Ceilometer Alarm.
This patch aims to:
* deploy Aodh in scenario001 (beside Ceilometer).
* drop ceilometer alarm code (replaced by puppet-aodh).
* add TelemetryAlarming testing (to validate Telemetry Alarm with Aodh).
Change-Id: I1acde0fad6c36429562d8576663c4cb9d393a79d
Disable git_clone from scenario003, all-in-one.sh leverages
run_tests which will now properly clone tempest if whether or not
we're in the gate.
Change-Id: I687464f26913bc9ee978e00e5c78efe91b062ec2
This script will help newcomers to run this script and deploy a simple
scenario of an OpenStack Cloud with Puppet OpenStack modules.
Change-Id: I559e5e0a0d21a02d04b3d999b77dee23bb38c341
Bump from UCA RDO Liberty testing to GA repos.
Depends-On: I709ae10101b7156a60efc10e88866abe3e643417
Change-Id: I19a1588c488d56b647703c0267540c7649fdc6d1
Instead of harcoding 'jenkins' user, use $::id fact so we can re-use
this manifest somewhere 'jenkins' user is not present.
Change-Id: I781e21112c3c0dfadd568f4d9436ddbd7d4a28b6
nova_admin_ parameters are deprecated and were replaced with Keystone
authentication plugins related options.
Change-Id: Idb8c4f3348345670c9ec61d885329fd0b16ec687
Bug #1356053 was fixed in upstream and now we don't need specify
another service type for Sahara service.
Change-Id: I2d95f17a27bab3871ca561e6480655696df7557d
* Install & configure Trove (database as a service)
* Configure Tempest to run tests
* Run Trove tests
Change-Id: Ic8a05550cdf30ade95a698a340a52595892e3212
Do not try to use another domain name for default domain.
Let's validate our modules with default features and we will iterate
later with specific use cases.
Change-Id: Iaac6f0feb2ff3f8f35d1ee02309f3b3f01390e97
* Install & Configure Cinder with iSCSI backend
* Enable volume tests in Tempest
* Add default_floating_pool parameter to Nova API configuration
to tempest volume scenario can work, since it uses Nova API to
associate the floating IP.
Change-Id: I8bc007f3182741b2710dc0615261d9bd403f781f
Still hacking on the patch to make it pass trusty systems.
* Create 2 flavors, used by Tempest Compute tests
* Create 'public' network, used by Tempest Compute tests for floating-ip
* Configure Tempest to be aware about the 2 created flavors refs
* Configure Tempest to be aware about the public network
* Add some Puppet Exec code that prepare virtual bridging to reach floating IPs
* Add scenario parameters
* Run Smoke suite that includes 2 scenarios & some important API tests.
* Pin python-netaddr on ubuntu so we can test floating-IP.
Change-Id: Iebb83e110fbb0c072f06b3ca2ad84987e0efe3a6