As it was announced [1] global bindep-fallback.txt was removed and now
projects need to have a local bindep.txt to be able to install binary
dependencies for testing.

In test jobs the script tools/test-setup.sh is called which requires
mysql and postgres servers and clients to be installed.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007272.html

Change-Id: I6b7afd3f6d0b45337f87e13352ab1095d51a23a3
(cherry picked from commit 4655630a)
(cherry picked from commit 29a07f76)
(cherry picked from commit 26f5183f2533ef871ef19631b4a3e2b479ddab7d)

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.

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: I46eb3529be45a2f6c78a06747778a20a9a6fcc60

Non-containerized multinode scenario jobs are no longer supported
and should be removed from zuul config.

Change-Id: I09a064daf50931270fa28a36d5aa1f0c1a067ab4

Stable periodic jobs started to fail [1] [2] with errors that they are
missing required projects as soon as old job settings were removed [3]
from project-config repository. The problem is only present in queens
and pike, on the other stable branches the configurations are OK.

So networking-bagpipe, horizon and neutron added as they were present
in the old settings.

[1] http://logs.openstack.org/periodic-stable/git.openstack.org/openstack/networking-bgpvpn/stable/pike/build-openstack-sphinx-docs/594eeba/job-output.txt.gz#_2018-10-13_06_33_35_696317
[2] http://logs.openstack.org/periodic-stable/git.openstack.org/openstack/networking-bgpvpn/stable/queens/openstack-tox-py27/4af2104/job-output.txt.gz#_2018-10-13_06_24_06_925732
[3] https://review.openstack.org/#/c/597865/

Change-Id: Ia9f5fa177771ead870c13546aa870ee64b3445be

Change-Id: I9d30390952860982fe47ec2ee23f5c988f4c4fae

Source the l2 agent script only in case and in place where functions
from this are going to be used.

Change-Id: If99776166aebf432a6da3b77aa265fec01a64a37
(cherry picked from commit 7bd7f451)

Import legacy jobs from openstack-zuul-jobs and rename them
according to Zuul v3 naming conventions.

Change-Id: I56e23dd4352ee34ed2a129cc853cc33616559dca

Made posible now that bug/1789878 is fixed in networking-bagpipe
stable/queens ( https://review.openstack.org/600377 ).

This reverts commit 036b177a.

Change-Id: I0f5b0837b391fd8030f9cd1aec5a42f67a08c397

This change temporarily disable some tempests tests until
bug 1789878 is fixed.

Note well: this is a cherry-pick with modifications.
On stable/queens, bug 1789878 prevents all scenarios
tests from succeeding, or at least reliably so. This
is why this change skips all scenario tests.

Change-Id: I67e8834c09f475b997edf9bf095fa1ac6595e4e0
Related-Bug: 1789878
(cherry-picked from 4897b5c7)

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: I720e79f653b42b5a78fce84cb34b49f671fd81c2
Story: #2002586
Task: #24314

This was left out from previous commit [1], so now both 'check' and
'gate' jobs work, but the periodic-stable jobs fail: networking-odl is
required for jobs on queens and older stable branches. From rocky,
there is no tox_install.sh any more, so this is not needed there.

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

Change-Id: I1439038c62fac437affef3303946d2438fc26600

build-openstack-sphinx-docs jobs fail on stable branches due to the new
pip version 10 introduces some previously Warning as Error: in case of
calling "pip install" without any package name, the command fails.
tox_install.sh is called during docs job without any package passed to
pip.

Also some tests still needs networking-odl package to be installed, however
it is removed from the required-projects of networking-bgpvpn, so they
fails now. To fix this, the easiest solution is to add networking-odl
to .zuul.yaml on stable/* branch as required project.

Change-Id: I93aea1800b6403482a7e15116610efeed02c28a1

All these release notes are applicable to Queens release.

Change-Id: I708c3b3989e426a99b046d9d5b29ac93ab870634
(cherry picked from commit 378ce00b)

Change I8cef6fc49b95b8a18fcb476da079fbc55fecd802 for bagpipe driver
improves coexistence between BGPVPN and a Neutron router, but requires
using the openvswitch firewall driver for single nodes setups.

Needed-By: I8cef6fc49b95b8a18fcb476da079fbc55fecd802
Change-Id: I9d63ce7343f0eacc0bdc7eda568cc04586bdb4f8
(cherry picked from commit a5598b02)

The new stable upper-constraints file is only available
after the openstack/requirements repository is branched.
This will happen around the RC1 timeframe.

Recheck and merge this change once the requirements
repository has been branched.

The CI system will work with this patch before the requirements
repository is branched because zuul configues the job to run
with a local copy of the file and defaults to the master branch.
However, accepting the patch will break the test configuration
on developers' local systems, so please wait until after the
requirements repository is branched to merge the patch.

Change-Id: Id05936f8063a980daca11d050c7707d9ff75502f

Change-Id: Idca6211d24b55437aa197005beb17fce07c3dca7

Beyond obvious reasons to try to migrate to the new facade, bug
17446996 is leading us into using the new DB facade for BGPVPN
OVObjects used by bagpipe driver.

However, unless we switched all DB operations to the new DB facade,
we have a situation where we mix both old and new facade, which
is a known source of issues.

This change switches all DB operation to use the new DB facade.

Change-Id: I5a395560ea0573c92a3c615d7dbcb343d6983a78
Depends-On: Ie4ad57f6357c59f2a978467099642b08e730133e
Related-Bug: 1746996

'allow_put' for 'local_pref' attribute to BGPVPN resource  is True.
‘local_pref’ can be updated in 'test_bgpvpn_create_update_delete()'

Change-Id: I059c8db61a91b20665feb31f1bc2184727eb1c37

After closing 1732070, we can re-enable the
test_bgpvpn_negative_update_to_empty_rt_list tempest test.

Change-Id: I756700350c9287a532d500ea04631eb200a1986e
Related-Bug: 1732070
Depends-On: I615acd193a90eeea2ab3dd9bd3b41912a6304193

SQLAlchemy lazy loading needs to be enabled for the
BGPVPNPortAssociationRoute to BGPVPN relationship,
or else we have an OVO issue as follows:

Parent instance <BGPVPNPortAssociationRoute at 0x7f83190682d0> is not bound to
a Session; lazy load operation of attribute 'bgpvpn' cannot proceed

This change also changes the lazy joining mode to "joined"
for the BGPVPNPortAssociationRoute to BGPVPNPortAssociation relation,
which should here be a bit more efficient.

Change-Id: Ic4b5bc16d1326a328176f121b3b5c3e93d707fd5

This adds comments in requirements.txt to help packagers
identifies that some of our dependencies are managed
via tools/tox_install.sh .

Change-Id: Ib9f3b6af62c61f45951a91112816ce4f5c436066

There frequent failure of the test_bgpvpn_port_association_create_and_delete
and test_bgpvpn_port_association_create_and_update tests, where the
destination loopback IP seems to remains reachable even after
association or route is removed.

This change modifies the tests to:
- add more information when this happens (try to identify the server
  answering the ping)
- do an initial check that the destination loopback IP is not reachable
  before the tests starts
- correct a misleading message

Change-Id: Iaba153bf01b2a47ebca7d7d6804981f5a77c7142

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

Change-Id: I1d3d92ee5962f0a292718409a5b0cd884a4d4e6d

Change-Id: I14e6429a2d76c260b48591e63c118304560d43d0

Our current logic for ignoring DBs that which shouldn't
check in the DB/model consistency check is:
- incomplete (missing new bagpipe tables), causing
  functional test to break [1]
- not flexible enough

Such issues have arised in the past with ODL tables.

This change makes the mecanism more flexible, removing
the need to list explicit table names, and allowing wildcarding.

[1] http://logs.openstack.org/16/537816/1/check/legacy-networking-bgpvpn-dsvm-functional/01973b2/job-output.txt.gz#_2018-01-26_09_26_39_360246

Change-Id: I0c79536ae2f802a5408e9656a5026147f6730211

Additional tempest test to check local_pref attribute
for L3 BGPVPN port association

Depends-On: I36ac883faceaa4f5d135c6802fd6469213207ff7

Change-Id: Ib6078da15ceda767b50f8d530885b7578e7feb10