Commit Graph

18 Commits

Author SHA1 Message Date
Natal Ngétal dbc129238e [Core] Remove mitaka.
The mitaka release is no longer supported by the community.

Change-Id: Iba4ed16f5d91973e43d3be040ce7e0eaf7396c73
Closes-Bug: #1722602
2018-11-14 11:14:06 +01:00
Emilien Macchi e8ce6e4e03 Move Multinode environments to THT
Scenarios already live in THT because they contain some data (like
TripleO services or data binding) that are specific to TripleO releases.
Example: NovaPlacement has been introduced in TriplO Ocata but not
support in Newton. That's the reason we moved scenarios templates and
pingtests in THT, so they can be branched.
This patch does the same for multinode and multinode-3nodes. It moves
the roles-data and pingtest to THT.

Change-Id: I689d85918d78f51951e0c142f5cfb51b5c1f78f5
2017-01-25 22:15:05 +00:00
Emilien Macchi a5dfb7ab22 cleanup: remove scenario004 bits
scenario004 bits are not used anymore.
We'll add scenario004 again, but in THT, not here.

Change-Id: I067b86aa2a7773a6afefe3c1b8af48602949b155
2016-12-01 08:22:30 -05:00
Emilien Macchi 213ec15d3e Consume TripleO CI scenarios envs from THT
Use TripleO CI scenarios environments from TripleO Heat Templates.

Note: Newton jobs will fail once we merge this patch, and will pass
again once we merge and backport:
https://review.openstack.org/#/c/402119/ into stable/newton.

Change-Id: I8235fa0648a05c2420c536e388b05e9c2f8fecc1
Depends-On: I3527a64c0c8f56ca77115d32849fa23fe710112d
2016-11-25 10:27:42 -05:00
Juan Antonio Osorio Robles b11e532b74 Introduce scenario004
This scenario will only be ran for releases from Ocata and above;
Currently the extra service it deploys is Barbican, and is only
doing a key order from it, however, in the future we will test
encrypted volumes once we configure that in t-h-t.

Change-Id: I19ed2dddd88ae1752c6b7500c1790f801f6bfcd9
2016-11-10 12:08:51 +02:00
James Slagle b93d339c8a Revert "Add Barbican key order to scenario002"
This reverts commit aa577a6e5c.

Since barbican is only in the overcloud in ocata, this has broken stable CI jobs for scenario002.

Change-Id: I452b5c9b0d87753cdb1b6a6cabe72e89000d11fe
Partial-Bug: #1640311
2016-11-08 22:12:46 +00:00
Juan Antonio Osorio Robles aa577a6e5c Add Barbican key order to scenario002
Depends-On: Iacc504fc4fa2d06893917024ce2340d3fb80b626
Change-Id: I196c59131981607ab9ebd35aca38374a5776987c
2016-10-20 13:44:33 +03:00
Emilien Macchi 3956f6dbf7 Implement scenari001, 002 and 003
* scenario001 will test Telemetry with Aodh, Ceilometer, Gnocchi with file
  backend, MongoDB and Redis.

* scenario002 will test Cinder with iscsi backend.

* scenario003 will test Sahara.

All jobs are experimental and non voting.

Change-Id: I8b1a3cfd44ed25eb121f9f2a0a8bc7316f681324
2016-08-31 15:43:06 +00:00
Emilien Macchi 4037fdd9e6 Implement scenario001 CI job
scenario001 is a proof-of-concept of how we can scale-up our CI by
spliting services on multiple CI jobs.

In the case of scenario001:
- Sahara is deployed.
- Cinder and Swift are not deployed.
- Glance uses file backend.
- Test to register an image in Sahara with the pingtest Heat template.

Also adds the testing matrix in README. The matrix will grow with more
documentation in the future.

Note for reviewers: we will have a pingtest per scenario. After some
testing I figured it was too much complex to try to maintain common bits
in a template and do nested stacks.

Change-Id: I25521a8bf8b91f7df4020de6599c4e8420e81fef
2016-08-29 09:52:43 -04:00
Emilien Macchi c33dccad0f pingtest/tenantvm_floatingip.yaml: connect vrouter before creating fip
This patch fix a race condition in templates/tenantvm_floatingip.yaml
template, used by pingtest.
It makes sure that the vrouter that make the connection between private
& public network will be created before trying to create a floating-ip.
Otherwise, the heat stack will fail to complete because a floating-ip
needs the vrouter in place.

Change-Id: I81641be2b4bf0bd15b10fab1e9725062f52a1bf8
Closes-Bug: #1597265
2016-06-30 08:13:27 -04:00
Mathieu Bultel 6138f8c776 Let heat creates and manages the keypair for the pingtest instance
Change-Id: I383bd58dc6b568afe8bdf695a3218d873ab38cfd
2016-04-28 21:48:31 +02:00
Giulio Fidente 056c167aac Create a test flavor for the pingtest VM
The m1.demo flavor is created arbitrarily by the client but we
want to remove the post-deployment initialization so we switch
the pingtest VM flavor to one we create from the template itself.

Change-Id: Iec0a64b24813536dd591362f1aefe46135a5a16e
2016-04-07 15:49:42 +01:00
Ben Nemec 7286784100 Use split cirros image for ping test
Since cirros is so much lighter weight in a nested virt environment,
this should help with the load on our CI systems.

Note that we switched away from Cirros originally due to the
no_timer_check bug that is present in it, but when the split image
with a separate kernel and initrd is used Nova has some magic that
adds the necessary kernel param automatically[1].  That should make
this safe to use again.

It also allows us to move back to the m1.tiny flavor and use a much
smaller volume, which should make the ping test even faster.
Deleting a 10 GB volume in particular is painful because Cinder
zeros out the storage space before it reports the deletion as
complete.

Change-Id: I5081c00a1cc9a191172e6c32b68c66c110d18c15
1: ce5f9c609f/nova/virt/libvirt/driver.py (L4090)
2016-04-06 15:50:08 +00:00
Ben Nemec 5fc32bd573 Boot from volume in ping test
Right now we aren't verifying that Cinder is functional.  This
provides a sanity check for it too.

Change-Id: I6daec26b9a18231778eb59962e4b69a2a7fb0c76
2016-03-16 15:31:00 +00:00
Ben Nemec 7952370da1 Use m1.small for ping test
m1.tiny does not have a large enough disk for the fedora image, but
m1.small does.  The only downside is that it is a 2 GB ram image.
However, our compute nodes now have 5 GB of RAM so there's plenty
available, and with such a short-lived VM it's likely that the
actual difference in memory used between the two is minimal.

This will allow us to remove the m1.demo flavor creation from the
overcloud deploy since it was only ever there for test purposes.

Note that this is essentially a cherry-pick of change
I6b1e35c00e51ae9da1830a1e6d714e5f0858bcdb from tripleo-common,
which unfortunately merged after tripleo.sh had been moved to this
repo.

Change-Id: Id4bf6af82c28eb5ec4f93df1a3e8ddef26be1d66
2016-03-16 15:25:21 +00:00
Steven Hardy 118ee50747 Move tripleo.sh into tripleo-ci repo
We're discovering that everything needs backporting into both branches
despite the script handling both branches anyway.  Given that this
is designed only for developer and CI usage, we may as well save this
effort and move the script here instead.

When this is all working, we can remove the script from tripleo-common
and add a README instead pointing developers to the new location.

This is based on the content of tripleo-common at 6031198 - tripleo.sh
is unchanged except for adjusting the TENANT_PINGTEST_TEMPLATE path.

Change-Id: I9f3df108514a9d5f456e1c467993b778a2f91d89
2016-03-15 12:02:45 +00:00
Derek Higgins 4613321b3d Startup a overcloud
Use heat to start an overcloud
2013-06-14 16:03:32 +01:00
Derek Higgins 185b4d6801 Start bm node with heat
Adding Heat to the stack of tested elements
2013-05-21 22:56:54 +01:00