This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.

This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.

This update should result in no functional change.

For more information see the thread at

 http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html

Change-Id: I59312b9ee70b4a3a7e9912a011de770d8df0f5a4

We are in Stein-3 milestone week[1] and as per
the release process[2], this commit adds the setup
fo stable/stein.

[1] https://releases.openstack.org/stein/schedule.html#s-3
[2] https://releases.openstack.org/reference/process.html#final-library-release-week-before-milestone-3

Change-Id: I6eff057878b30d5fc77e74ebde4bda0f4c7e603c

Solves annoying warnings and prevents code from breaking on newer
ansible which dropped --sudo.

The sudo command line option has been deprecated in
favor of the "become" command line arguments. This feature will be removed in
version 2.6. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.

Change-Id: I0ec17d6bd6a1e3ada366c323ad67e864a7f1b5ed

This patch keeps the proccess_stackviz function default to true, but
allow it to be optional called, if you set PROCESS_STACKVIZ to 0.
This is required because not all the projects run tempest in the same
way.
One of the examples is the tripleo project, that has a particular way
to run tempest (in undercloud) and it's being impossible to have the
stackviz results in the logs/stackviz because the cleanup process
overwrite the stackviz data there.

Change-Id: Idf4f360ecba618900ef939d94db2ffb73e16b11a

The openstack/placement repo is required for devstack/grenade
runs starting in Stein so this adds a conditional based on the
branch to include the openstack/placement repo in the default
PROJECTS list.

Needed by https://review.openstack.org/604454/

Depends-On: https://review.openstack.org/608266/

Change-Id: I71cffffc88c329052c4067d6a9406f42856c69c6

Depends-On: https://review.openstack.org/600196/

Change-Id: I940a705d4b8269fbf3bec9f107f179e9191b5a42

This is the same version run by zuul.

Update devstack callback for ansible 2.5.

Change-Id: Ic0d2559346570e60025838166b9bd0081eee331a
Signed-off-by: Paul Belanger <pabelanger@redhat.com>

This job is used only by devstack-gate, import it.

Rename it to devstack-gate-hooks following our naming policy.

Change-Id: Id01d7cda5cb28b6371bdcf8b85208135caa9e9b1

Now we have stable/rocky branch ready for devstack
and so does for all service projects.

This commit adds the stable/rocky job running for
d-g gate.
Depends-On: https://review.openstack.org/#/c/596279/

Change-Id: I7ab1b7042808cce0d89cb2bcfc87c718543718b4

Fixes case where a succesfull creation of the
virtualenv but failure to install zuul would
make the function useless as it would always
miss installing zull.

Change-Id: Ie5ef82765120094e8147b05443626e2012273fba

This patch adds the rocky branch to features.yaml so that rocky branch
patches can land, for example [1] that currently fails with:
ERROR: branch not allowed by features matrix: rocky

[1] https://review.openstack.org/#/c/584078/

Change-Id: I235c6c3ad81dff916a65cf8b97152621812fa102

These seem to be not run for quite some time and they don't
succeed anymore - drop the code to avoid somebody accidentally
running it and wondering. A good example of "if it isn't tested
its broken".

Needed-By: https://review.openstack.org/#/c/581377/

Change-Id: I68d7099e6f5be502f8a578818b5e2e4c82889c15

Some clouds we run on no longer have MTUs of 1500 on their interfaces
and are smaller. We dynamically determine the MTU we should use on the
overlay networks. List all "real" interfaces with a permament mac addr
then use the smallest MTU less 50 bytes for vxlan overhead.

We only consider "real" interfaces so that we can run this multiple
times for separate overlays without perpetually decreasing the MTU due
to finding the lower MTU we just configured.

Change-Id: If163bf211570e690e255cc3ef6888d9e0cba19b5

cmd2>=0.9.0 now require python3.4 or greater. We install ansible under
python2 (for now) so we need to cap the cmd2 install to make the ansible
installation function.

Upstream bug at https://github.com/python-cmd2/cmd2/issues/421

Change-Id: I5ec830e092646a3626cacea264de9ad81fcdd124

tripleo-incubator has been retired so we don't cache it on our images
but if it is in the PROJECTS list we will attempt to rsync it. Just
remove it as it is no longer used.

Change-Id: I3ad57d247a02881ba8a6757f2a058d03884eaf35

Adding ETC binaries was a stop gap measure until packages were
available.  With the impending release of bionic that'll be soon :)

Also using the mirror on tarballs.o.o was unreliable so these binaries
are cached in the nodepool images as described in[1].  Having this
setting in d-g makes more work than is needed in the near term.
Removing it does introduce a new failure mode if an etcd version is
used in devstack but not yet cacched in the image.

[1] http://lists.openstack.org/pipermail/openstack-infra/2018-March/005871.html

Change-Id: I2a6649ae3094ca65aa31798ee9bddf2fcdd49260

Promote "local hides exit status" (E042) to error and fix issues found
(this is inline with what we do in devstack).

Change-Id: Idd784af066db80bb67792da3dd0aa0ae4c8475db

Replace the legacy stable/pike tempest bitrot job with the new
zuulv3 one. The removal part will be done in a separate patch
since it's in a different project.

Change-Id: I180cd65e934c15b33975e65a9ece1d1f48fd851c

The old tempest tests have been removed from the neutron repo, so
legacy-neutron-dsvm-api doesn't run anything at all anymore. Use the new
api job from the neutron-tempest-plugin repo instead.

Change-Id: I2d1854109474cee1923b9bffd75c3224a6f2b4bf

The type here is important, returning anything other than a boolean
has unintended consequences such as breaking Ansible callbacks because
they are expecting the "changed" field to be nothing other than a bool
by contract.

Change-Id: Ia9b4a749f64adae8969fd9ad66304d013013e056

New jobs for d-g can be defined in the local .zuul.yaml as opposed
to project-config. These jobs prevent ensure changes to d-g to not
break stable/queens.

Depends-on: https://review.openstack.org/521888/
Change-Id: I547591607a7726bdef3c3953df9e0bd1c67f3423

Change-Id: I2709f5527552fd4fc406f870ef35c4b6e4b9dae9

The current check looks for a virtualenv package; but this isn't
portable to other platforms.  In the gate we also have installed from
upstream (to ensure latest) and the package might be on hold, etc
which might mess up the detection.

I think the KISS thing to do is to check for virtualenv and fail with
a useful message.

Change-Id: Icf15ddd18ca52885f5c4a89a7d83622a70c811d5

Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.

Change-Id: Ifd621431bfb925e8a6f0df013ddbe7cd7ed5c1e7

tempest-lib was reintegrated into tempest in 2016, there's no need to
check it out anymore. Remove it from PROJECTS list.

See also
https://specs.openstack.org/openstack/qa-specs/specs/tempest/implemented/reintegrate-tempest-lib.html

Change-Id: I3ed33ad9cf4097bc48ab71a666c2ce95b26c3329

Change-Id: I505bb7f7d226845e96a815a34a548ceacee65517

This commit makes to handle a stestr execution for stackviz process.
Tempest is now in the process of switching the tempest run command to
use stestr internally instead of testrepository. This means that results
will be stored in .stestr instead of .testrepository. So, this commit
makes to handle a stestr or testrepository execution with checking which
directory exists before attempting to process the subunit results.

Change-Id: Ib19d3779deb89142e95762794dd1ce3fe3236b55

Tempest is in the process of switching the tempest run command to use
stestr internally instead of testrepository. This means that results
will be stored in .stestr instead of .testrepository now. This commit
updates the post-processing function to check which directory exists
before attempting to copy the subunit results.

Change-Id: I3855aad5ce129ec8ccb87c05f7aa709b74070efe

We have standard jobs for doing unittests under python2 and python3 -
namely, the builtin tox environments py27 and py35. Just use those and
remove the locally defined jobs.

Depends-On: I6d7a96adf5cfb075f5a2ffbd089ccbb883a1c1b4
Change-Id: I0cc0c07daafba331a64861c134029e443ba2aa8d

This should allow py27 and py35 to both work in parallel while we remove
the run-tests versions.

Add the new jobs here, even though the next patch will remove them,
since we can't verify the new jobs work with depends-on to
project-config.

Change-Id: I78cfadf5a3b9822ce32f5a1d9b76321d573618ab

Import the tox jobs and convert them to Zuul v3.

Change-Id: Idcdc8d4508fa8d7746b3ba094d0bd96410007ef1
Needed-By: I6d7a96adf5cfb075f5a2ffbd089ccbb883a1c1b4

Modify test-matrix.py so that is can be used as an ansible module.
Add a role in d-g that runs test matrix for the given branch,
role and features file.

Change-Id: Ie36ba0cd7cfcd450b75000a76a64d856f2a83eba

A recent change to devstack-gate to enable falling back to EOL tags for
zuulv2 has a bug in it where it will try to checkout the stable/branch
instead of the converted eol tag. This patch addresses that issue.

Change-Id: I23330884da09befc3bca10973cbfd2ea9b666430

In order to support continued testing against EOL version of projects,
the setup_project function needs to be able to understand checking out
to an eol tag.

Change-Id: I1b2d030df8cb2a850bf9248595171d96a813d381