80 Commits

Author SHA1 Message Date
Brent Eagles
f4460a580d Run octavia-api under httpd
octavia-api's cli app doesn't behave well with haproxy so let's run
under apache and save ourselves some grief. Also adds cleanup for the
octavia-api tls proxy in update and upgrade tasks if it was previously
deployed.

Also updates zuul layout for multinode job to track changes to new
flattened octavia service files.

Closes-Bug: #1815811

Change-Id: Ied7cb31fbf1222694250e4769573bcbb82ba5bea
2019-04-09 18:01:37 -02:30
Wes Hayutin
12637c5aca remove dep job in gate
I don't think gate jobs should
use dependencies.

Change-Id: I8f2584a763c116284eace5030fc8c0d5ed47adc2
2019-04-02 14:10:58 -06:00
Zuul
b842048a3c Merge "turn voting/gating on scen009 master" 2019-04-01 17:14:48 +00:00
Sagi Shnaidman
4d42323849 Add ci/common as trigger to scenarios multinode
Run various multinode jobs on changes in ci/common

Change-Id: I71113b177a12e181e1742c04fe04f461fc8ccd1b
2019-04-01 08:25:28 +00:00
Zuul
a60718072d Merge "[Configuration] Add missing py37 and corrected default envlist." 2019-04-01 07:38:22 +00:00
Wes Hayutin
26e369e0b0 turn voting/gating on scen009 master
scenario009 is passing in master now.
Let's keep it that way w/ voting!

Change-Id: Ica230852d1e4d485fc2ff5f395f6347974240c75
2019-03-29 14:32:26 -06:00
Emilien Macchi
8523a90e16 Update zuul layout for new deployment directory
We now have a deployment directory where we are moving all services.
This is new in Stein and it won't be backported.

Change-Id: I52039deaa8ff459de5afbfeb3e2c54eb8908bb3f
2019-03-28 08:41:19 -04:00
Natal Ngétal
0fb353339a [Configuration] Add missing py37 and corrected default envlist.
Change order of default tox envlist in order of likeliness to fail on a
new change and add py37 and py36.

Change-Id: If72e480c12385463088e2e0962801cd7095a6f12
2019-03-27 10:57:19 +01:00
Dan Prince
5c8456c5cd move ceph-ansible into deployment
Change-Id: I67dc1c2dd7d1e0308db660577f25d74a6305dae6
Related-Blueprint: services-yaml-flattening
2019-03-22 01:01:30 +00:00
Alex Schultz
df403c2cdf Add python36 job
We should be running a python3 job for tripleo-heat-templates and since
we dropped the old 3.5 job, let's add the correct 3.6 job.

Change-Id: I93bd7bf988c881496ecee0c5d4e2bc97a5047571
2019-03-13 17:01:24 -06:00
Alex Schultz
9f0d23c78a Drop the old python35 job
We are running the regular jobs with constraints now so we don't need to
be running this job. Additionally it's not functioning correctly with
the switch to bionic

Change-Id: I41bf5002bd40654d55456a5cdafcef6b76b1f62e
2019-03-13 16:56:56 -06:00
Zuul
eee89fb2f0 Merge "Delay check CI jobs until the pep8 passes.." 2019-03-12 19:55:37 +00:00
Bogdan Dobrelya
fc612b86b2 Delay check CI jobs until the pep8 passes..
..for Greater Good.

NOTE: for example, standalone jobs are defined as a template in
tripleo-ci, and here we are adding and override the listed jobs for the
dependencies/files options. If a job is added to the standlone template
in tripleo-ci, we need to add the job and dependency here manually.
If we won't, that job will be consumed as is and run w/o dependencies.
That is the price to pay for not having overrides managed centrally in
tripleo-ci. The latter wouldn't work neither as a single template
cannot fit all the specific needs of numerous tripleo repos. So the
final call was made to manage overrides via local overrides for tripleo
repos.

Save CI resources and shorten wait-in-zuul-queue times
for other patches, when pep8 checks failed (that is YAML validation
for this t-h-t repo).

For core openstack python projects it might make sense to
not split them apart and run them all together. For things like
TripleO/Kolla/Puppet/etc where we have layers of interactions that can
be affected by the results from the linters/unit jobs it makes
sense to split them out.

For example, in tripleo since we use packages, if the unit test fails
the integration test may fail because when we go to built the package
with the new source, the unit test int he package build fails.  Thus
we know that'll be a wasted execution and you won't actually get any
results.

An alternative Today:
  patchset one:
    pep8 SUCCESS
    integration FAILURE
  patchset two:
    pep8 SUCCESS
    integration FAILURE
  patchset three:
    pep8 SUCCESS
    integration SUCCESS

Future:
  patchset one:
    pep8 FAILURE
    integration SKIPPED
  patchset two:
    pep8 SUCCESS
    integration FAILURE
  patchset three:
    pep8 SUCCESS
    integration SUCCESS

This may not be true for devstack but if the unit
tests are failing, then the code is likely bad (backwards
compatibility/wrong assumptions about change/etc) and we shouldn't be
running an actual deployment.

Related upstream ML threads:
* http://lists.openstack.org/pipermail/openstack-dev/2018-March/
127869.html
* http://lists.openstack.org/pipermail/openstack-discuss/
2019-February/003142.html

Change-Id: I2216773113f8d4e4a2bdff35709ff739f5164a32
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
2019-03-05 16:12:57 +01:00
Emilien Macchi
f3b85e4ba5 Remove Congress
Congress doesn't seem to be used anywhere, we never had a bug report or
any sign of somebody out there actually using it.

Let's remove its support in TripleO, to reduce the codebase.

Change-Id: Idca6b12f1c0ca3bc15bedf6469d4063a4dac31fa
2019-02-28 16:29:03 -05:00
Steve Baker
5ceb3c5ec7 Make ceph-ansible working dir owned by tripleo-admin
The ceph-ansible tasks are now invoked with the tripleo-admin user,
which doesn't by default have write access to /var/lib/mistral, but it
does have sudo access.

This change makes /var/lib/mistral/overcloud/ceph-ansible be owned by
the tripleo-admin user so that subsequent tasks can write to that
directory.

Related-Bug: #1813832
Change-Id: I98bb38078be84cbda3e9a9e338af0d054dc53420
2019-02-12 09:13:15 +05:30
Steve Baker
2e899f3943 Move container-image-prepare.j2.yaml to deployment dir
Change-Id: Idf8eab2c0290c02908ffd3284543046cdf8aa5ba
2019-02-07 10:26:20 +13:00
Zuul
a857fe1ad6 Merge "Fix files conditions for scenario 007 and 008" 2019-02-06 19:40:24 +00:00
Marios Andreou
f6b934bd6f Remove the scenario standalones from tht zuul layout - just use template
In I7cf36baa80e91d87b1b41c45204c61cf87846d34 we started using the
tripleo-standalone-scenarios-full instead of carrying custom
layout for the standalone jobs in projects. Looks like we forgot
to remove the gate definitions here.

Change-Id: I2c3940c7903f9fd4b9d0ec1aca8741182b9c76cd
2019-01-24 09:52:41 +00:00
Marios Andreou
beb7aa1124 Use the tripleo-standalone-scenarios-full template
Instead of carrying a distinct files: and check/gate layout use
the one defined in Depends-On below

Depends-On: https://review.openstack.org/630239
Change-Id: I7cf36baa80e91d87b1b41c45204c61cf87846d34
Story: https://tree.taiga.io/project/tripleo-ci-board/us/585
2019-01-17 09:02:31 +05:30
Sorin Sbarnea
dc46a8684c Assure that updates job is listed in both check and gate
Fixes reported problem of job running only in check and not in gate:
tripleo-ci-centos-7-scenario000-multinode-oooq-container-updates

Change-Id: I7df8d811287c7605b1b406420de1eb17ae555346
2019-01-14 18:58:38 +00:00
Zuul
618a6abf93 Merge "Fix files: for scenario003 standalone - pointing to wrong env" 2019-01-11 23:46:02 +00:00
Marios Andreou
f86c89e08c Add scenario002-standalone to gates as we make it voting
Adds scen2 to the gate jobs as well as check.

Change-Id: Ida84c67ba6426c0498fcc99c39a0857a772728a4
2019-01-10 14:53:27 +02:00
Marios Andreou
d59e016cda Fix files: for scenario003 standalone - pointing to wrong env
It was pointing to the old multinode env file instead of the new
standalone one

Change-Id: Ic093d11d717a6022b100972211d1d92b769248e6
2019-01-10 08:59:39 +02:00
Marios Andreou
1bd0bf02a3 Add standalone scenario jobs into the gate as well as check
Since they are voting we need to add them in gate too

Change-Id: If43962653ff7474ac2617bde6992ccbcd09e2153
2019-01-08 22:00:45 +00:00
Rafael Folco
340afe288a Replace tripleo-scenario002-multinode with scenario002-standalone
Change-Id: I68b72cf736bc6c3597e2417c6c0b5afe9ff79d30
Story: https://tree.taiga.io/project/tripleo-ci-board/us/532
2019-01-03 16:54:05 -02:00
Giulio Fidente
d8b2e9b3e2 Replace scenario004 multinode with standalone
Following addition of [1], replace use of multinode with
standalone job for scenario004

1. https://review.openstack.org/#/c/619520/

Change-Id: Iff1e83dd227fc2e03924f41592f82a555053425d
2018-12-21 14:46:38 +00:00
Zuul
fb369eb57f Merge "Replace scenario001-multinode with scenario001-standalone" 2018-12-21 14:41:20 +00:00
Rafael Folco
e7691b7415 Rename tripleo-ci-centos-7-scenario00{6,9}-multinode-oooq
These are containerized scenario multinode jobs that were
wrongly named.

Depends-On: https://review.openstack.org/#/c/619337
Change-Id: I804b7a39159445cb75ecc8e93897fd7f0f24b630
2018-12-17 16:50:11 -02:00
Marios Andreou
3b275727ec Replace scenario001-multinode with scenario001-standalone
The scenario001-standalone job is added in the depends-on below.
Tracked by tripleo ci squad at [1]

[1] https://tree.taiga.io/project/tripleo-ci-board/us/191
Depends-On: https://review.openstack.org/619508

Change-Id: I785ebec7671515c045571ebea0240349fc48a573
2018-12-17 18:15:08 +02:00
Zuul
29d37c1c31 Merge "Drop baremetal job template" 2018-12-15 09:53:47 +00:00
Harald Jensås
974c68e4b6 Add tripleo-ci-centos-7-scenario003-standalone job
This job is required to cover designate.

UPDATE:
  - Also ensure we run all jobs if zuul.d/* are changed.
  - Removed:
      tripleo-ci-centos-7-scenario003-multinode-oooq-container

Change-Id: I31ae7f873617b69bfd8fee7010bab133e384795b
Story: https://tree.taiga.io/project/tripleo-ci-board/us/338
2018-12-14 13:44:05 +01:00
Alex Schultz
b390ddd53c Drop baremetal job template
https://review.openstack.org/#/c/619337/ switched the jobs to a noop for
master and since this file is branched we no longer need to keep this
template definition in THT.

Change-Id: I305c175392089e103dec85461f289ab38127398d
2018-12-13 13:46:19 -07:00
Alex Schultz
a7114a98ce Remove non-voting scenarios from gate
Change-Id: I3e894ae631158c45128bb9cd07f20674ba56877d
Depends-On: https://review.openstack.org/#/c/614566/
2018-11-01 12:01:49 +00:00
Jiri Stransky
ab1fb06b86 Run update jobs for fuller set of services
Normally the listed services are omitted from the scenario jobs
because they are often covered by many other "default" jobs. However,
in the case of the update job, this is our only update job, so we need
to try to run it on a full set of services which are deployed by the
job. Otherwise we risk breaking the gate by merging something that
affects update job without testing it by the update job.

Change-Id: I8115333bb3be27a461f7dab9aba20749ed695a49
2018-10-16 19:21:28 +02:00
Alex Schultz
7d35d24164 Remove 3node from CI
This job is continually broken and just eats up resources. Let's remove
this for now.

Change-Id: I0f734a27c62e0ee0801001c522b1903354b1de4e
2018-10-05 10:55:31 -06:00
Gabriele Cerami
54b78df003 Fix files conditions for scenario 007 and 008
An incorrectly indented regexp was causing jobs not to be triggered
correctly.
fixing indentation make the jobs trigger correctly

Change-Id: Ic665dd273aab37dbd689c0a51cb0c3e4f0bc1e56
2018-09-19 15:34:02 +05:30
Zuul
5e84e4ce3a Merge "Add scenario010 to check job list" 2018-09-19 07:54:25 +00:00
Carlos Goncalves
b7e124bad9 Add scenario010 to check job list
Change-Id: Ifdbedd3e0f30dca689a2f8ec01d70ffb0b1f5514
2018-08-31 19:13:27 +02:00
qingszhao
09f1993a54 switch documentation job to new PTI
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: I9e6048085bbd8b1451166f36565f95d556cb8d90
Story: #2002586
Task: #24341
2018-08-31 16:57:54 +00:00
qingszhao
81b065a157 import zuul job settings from project-config
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: Idb328be9749bb0aa1d8e8ac748fefce962829928
Story: #2002586
Task: #24341
2018-08-24 04:59:29 +00:00
Wes Hayutin
84f395f034 remove scen000 update job from gate as it's non-voting
Non-voting jobs should not be executed in the gate.

Change-Id: Ib1fa0f08b77f7806e0ece9caf95922256fdaf0de
2018-08-21 00:14:46 -04:00
Wes Hayutin
aeb559ef4c remove scen007 from gate jobs
reference https://review.openstack.org/#/c/593170/1/zuul.d/multinode-jobs.yaml

Change-Id: I778033bef93dc2a318906fc697c26fbcf6878bf7
2018-08-20 15:16:33 -04:00
Quique Llorente
6978fa1743 Exercise scenarios with changes at common
Some stuff like the new health check were not exercising the
scenarios, the core part of THT need more covarage.

Change-Id: I34da92f57ef96dd3c1f6c3c525a366a578f720aa
2018-07-30 14:53:47 +02:00
Brent Eagles
ad7d6cf74a Add scenario010 for testing Octavia
This patch adds the scenario010, initially for testing Octavia.

Change-Id: I125c75e0a3389bfe8bf600fba5aa9c345ddcdeaa
2018-07-20 10:52:52 +02:00
Flavio Percoco
3ebcfd13fd Run scenario009 for more services
We should test scenario009 when services like mistral, haproxy and
keepalived are modified as these have a direct impact either in the
deployment or openshift's architecture.

Change-Id: I40313aa79c22fca0e53ae398807b8d2b0ac7269b
2018-07-19 08:49:57 +00:00
Wes Hayutin
5ac5aa636b remove scenario005 from experimental
See: https://review.openstack.org/#/c/581376/

Change-Id: Id693768fc1f0e148b271c4ed270053ca0ecca84e
2018-07-18 13:57:52 -04:00
Martin André
52fea6d6ac Move scenario009 to the check queue
This scenario tests OpenShift deployment managed by TripleO on BM
nodes. We got the job working last week and it's been working fine
since then.

 Let's move it to the check queue as a non-voting job for now and,
eventually, make it voting.

Change-Id: Ief28df449e1e37fb9c73ecaf839d3e335abb3ed8
2018-07-13 21:56:35 +02:00
Derek Higgins
683de3683b Add scenario011 to install ironic in the overcloud
Depends-On: Ib3f183980ce3e383c0e6319ee373bd8438e8e6b8
Change-Id: Ice806c363950c7868f464c856c0594e5fc41b554
2018-06-25 12:09:38 +00:00
Emilien Macchi
a9c2235a7f Revert "scen007 is failing in the gate"
Fixed by https://review.rdoproject.org/r/#/c/14155/

This reverts commit 441303792a7161fe303685dc7310bbb82e4ce523.

Change-Id: I62c8f2b30a9481284a587919778e504bfc54f48f
2018-06-16 15:51:50 +00:00
Wes Hayutin
441303792a scen007 is failing in the gate
Moving to non-voting until the gate is green
RDO-Cloud is down and we can not fix the
dist-git.

Related-Bug: #1777168
Change-Id: Ia2c18ff554dc8b980528f1905bbad98dced2c336
2018-06-15 13:17:11 -04:00