openstack/networking-bgpvpn - networking-bgpvpn - OpenDev: Free Software Needs Free Tools

This patch switches from legacy jobs to standard jobs
(neutron-functional for functional jobs)
Clean up relevant files from legacy jobs
Remove hook calls in install jobs as they did nothing
TODO: not sure what to do about the install jobs, should we keep them?
Change-Id: If27b989195999d202fb819b01fe085c143b920f4

Update to new PTI:
https://governance.openstack.org/tc/reference/pti/python.html#python-test-running
This change also wraps in a change to requirements.txt that
point pre-rocky neutron pypi release, which is the only
way I found to have the functional job get a fresh-enough
neutron (it's not a tox job and hence does not benefit
from the tox-siblings magic). This also reflects better what
is the real dependency we have (when rocky will ship we will
have neutron>=13.0.0.0).
Change-Id: I868cf65aa5ff0e55d0d45f36808c76286e4e7fd3

Instead of using tox-install.sh, we can install horizon and neutron
etc. now directly from pypi - or use the current branch in CI system using
tox-siblings.
Create doc/requirements.txt for doc requirements as well.
Update tox.ini for this change and add projects to test-requirements
file.
Note this is one step in fixing publishing of docs for this repository.
Depends-On: https://review.openstack.org/552865
Depends-On: https://review.openstack.org/554297
Change-Id: I13e61fffca48b6c004e028f0da8a1d84a2337e10

With recent changes, these need to be moved to requirements to install
correctly.
Note that neutron is still installed from git thanks to tox-siblings in
OpenStack CI.
Change-Id: Icec5980b12d23b7e414750a3eabbb35a88068fe8

Auto-generation of configuration files is part of the community-wide
doc-migration effort in Pike. networking-bgpvpn does not support it,
so this commit sets up the config file autogeneration.
Change-Id: I9c7bc3097bbaef1990b1b9e5f23771cef99fd016

* When installing git repos into tox venv, there is no need to
 use full clone. Shallow clone like --depth 1 is sufficient.
 It speeds up tox venv creation.
* Fix import check for networking-bagpipe and networking-odl.
 Python module names use underscores instead of hyphens,
 so the current iport check always returns false.
 As a result, installation of these projects are run multiple times.
* Allow to specify GIT_BASE for local testing.
 Previously PIP_LOCATION exists, but the tox_install.sh installs
 four repositories so PIP_LOCATION actually cannot be used.
In my local env, the time to prepare tox env was reduced from 4m52s
to 2m39s for the first run and from 42s to 19s for the second run
or later (after applying the first two points above).
Change-Id: I8b4a7340c01182174f6a6af063174c57f28015cc

Two reasons:
- no point in tracking master, now that development is done
 on odl bgpvpn v2 driver, which does not sit in n8g-bgpvpn tree
- odl master is sometimes broken [1], which impacts our CI
[1] http://logs.openstack.org/70/470470/2/check/gate-networking-bgpvpn-dsvm-functional-ubuntu-xenial/febf152/console.html#_2017年06月05日_12_56_21_302481
Change-Id: I239175e50fb5412999f8d26a605b0071562ffea6

Provide a 'bgpvpn' entrypoint definition, to allow the activation
of the service plugins in a less verbose way.
Change-Id: I751861c25e2e301011d2c1738288660e1286a9a1

Add simple script to setup mysql and postgresql databases, this script
can be run by users during testing and will be run by CI systems for
specific setup before running unit tests. This is exactly what is
currently done by OpenStack CI in project-config.
This allows to change in project-config the python-db jobs to
python-jobs since python-jobs will call this script initially.
See also
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html
Needed-By: I0a87f7db0d1d78e7419a8706683aaa540c3dc399
Change-Id: I557202e2be6df2c1cb8efc0f42ac74cd0c458559

Following the discussion in I948d2e967f62f690f412a7e50d76f54cf4fe262e,
it seems that what we should do is rely on tox_install/zuul-cloner to
acquire networking-bagpipe test dependency.
Change-Id: Ib0600040470382bb7f113cb09aa5d1519ea6c9dd

This change applies to tools/tox_install.sh equivalent
fixes that the ones applied in I54d400dea4efdf9ac9b580ff7f0a2bbcceb4df5e
for neutron-lbaas, in particular to use a temporary directory for
zuul-cloner installs.
More details are in the commit message for
I54d400dea4efdf9ac9b580ff7f0a2bbcceb4df5e.
Change-Id: I0c700511e5a63cd66144ad334eb18aa60afb544a
Co-Authored-By: Andreas Jaeger <aj@suse.com>

Most of the changes in d088925891 should
have been made on the branch after it was created. The update to
requirements was the only one that should have been made in master
before the branch.
The change to .gitreview and tox.ini will be made automatically by the
branch script. The other changes should be done by hand in
stable/newton.
Change-Id: Ief5c73ab4d1cd5fd032dede21f6a244bfa5777c2
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

This change updates our tree for Newton:
- tell "git review" to push in the stable/newton branch.
- configure tox to use the stable/newton upper constraints file
- let tox test UTs with newton release of networking-bagpipe
- let devstack jobs to use newton branch of networking-bagpipe
Change-Id: I67a1103eae0219e5cefa91fd5848aa0b8986c542
Depends-on: I719a9912ba8e7fe87620850017bdda83431e22da

This commit switches the use of plain testr for os-testr in the tox
venvs.
Change-Id: I285f820b7de3109665dd7a38da389b7fd42acf80

Similarly as in I02b28d3b354c3b175147c5be36eea4dc7e05f2a3 .
Change-Id: Ia8fd880e6a4dda080befedc4a85a9fa7b55f7772

Not sure why pep8 didn't complain at merge time, but it is
complaining now in my setup.
Change-Id: I5fe65c47a4ace13e21741804730c5815b4e2b32d

Add a new panel BGPVPN in Admin section to display BGPVPN created. The
page allow actions as create, delete or modify BGPVPN resources.
Add an API file bgpvpn to handle the bgpvpn Python API via
neutronclient.
Change-Id: Iee2de53c8cb9d61f80033ab63485bdcf0e742abb
Implements: blueprint horizon-admin-workflow

This change updates tox.ini and tools/tox_install.sh so that
we impose upper constraints on dependencies.
This is done by reusing what was done in neutron-lbaas.
(we also update our tools/tox_install to benefit from
a few improvements that have been brought to the one in
neutron-lbaas)
This change also declare our test dependency on pylint
in test-requirements.txt, rather than in tox.ini, so that
we don't endup with a pylint version that is inconsistent
with the one global-requirements would draw.
Change-Id: I904286860a5b8471f5da9312ee23bdf49004f1b0
Suggested-By: Ihar Hrachyshka <ihrachys@redhat.com>

Update requirements (tools/tox_install.sh): our master
branch now needs to follow Neutron's master.
Update unit tests.
Bagpipe driver: follow changes in OVS agent main in Neutron master.
Change-Id: I310ea955329b6f523b417b6bf8c25f6d2db08eba

Update tools/tox_install.sh so that the right neutron
branch is also used when the zuul cloner is in place.
Change-Id: I6c87713f85d8153f53b89484116f2755d0098d40

The branch specification was misplaced.
This only impacted test run locally by a developer.
Change-Id: I55671d7a9c7df501048febe24a15ba5f55a33024

We need tox to use the right Neutron branch.
Change-Id: I9c3e9d43893cb79e1f21de35896ba33055856c66

Mimic what neutron-lbaas is doing to avoid cloning
neutron repo on each test job, following guidance by
fungi.
Change-Id: I4c3bbaf568ba7ac96caf7534ec4294e18d6c7cee