We already have many different jobs defined for Zuul in Neutron repo.
Up to now all those jobs were in .zuul.yaml file but this file growth
really big and it was hard to read and navigate in it.
So this patch proposes to move jobs definitions to zuul.d directory to
separate yaml files per "job types". So there will be now separate files
with definitions for:
* grenade jobs,
* base jobs like functional and fullstack,
* rally jobs,
* tempest multi node jobs,
* tempest single node jobs,
* tripleo jobs.
And maybe others in the future.
Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7
We have run neutron-grenade-multinode in both check and gate queues
already. This job is almost the same as grenade-py3. The only difference
from Neutron pov is that neutron-grenade-multinode is multinode job and
grenade-py3 is single node job.
So we agreed on last Neutron CI meeting [1], that there is no need to
run both of those jobs.
As grenade-py3 is part of integrated-gate-networking template together
with tempest-integrated-networking job this patch removes also
integrated-gate-networking template from neutron's zuul config and adds
only tempest-integrated-networking to both check and gate queues.
[1] http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-11-19-16.00.log.html#l-179
Change-Id: Ic2e7ca04929dc89a2e408465eb34ef3feec2e328
During the OVN repository migration, the zuul jobs relaset to ovn
cannot be executed due to the DB redefinition. Once the OVN plugin is
totally migrated to Neutron, this job can be integrated as a in-tree
backend tempest job.
Change-Id: If1f0b0453d90eed27051fd516b95da32d4aa2afe
Partially-Implements: blueprint neutron-ovn-merge
As networking-ovn driver is going to be in neutron tree now, lets move
also networking-ovn jobs definitions to the neutron repo.
Change-Id: Ie1c66c773ee2d217b25bd915189e56254744a3d4
Related-Blueprint: neutron-ovn-merge
This job is running on python 2.7. We already removed all other jobs
which runs on python 2.7 and this was last one leftover.
There is other job "grenade-py3" which is basically the same but runs
using python 3 and this is still running on neutron's check and gate
queues.
This patch don't remove definition of neutron-grenade job as this job
is used by various different projects. So we need first to switch all
those projects to use grenade-py3 and than remove definition of
neutron-grenade.
Change-Id: I873bb63fa0456fd9c0fb9b037280fe8d2c0541d5
This patch switches neutron-tempest-with-os-ken-master to zuul v3
syntax.
It also switches this job to only run networking related tests instead
of full tempest test suite.
Change-Id: I4e9aa4bbafed4de0e3c13ece44f8e700952da568
In check queue there were 2 iptables_hybrid jobs. One was run on Ubuntu
and one on Fedora.
During the Shanghai PTG we agreed to remove one of those jobs and left
only one of them to be run in both check and gate queues.
This commit removes iptables_hybrid job based on Fedora image.
Change-Id: If0adb7ca4e254f5b19375b471679bcc18e0c7790
As we agreed on last PTG in Shanghai, we should clean jobs
from Neutron's experimental queue as those jobs are still legacy jobs
and in fact are not run in Neutron at all.
Change-Id: I703622d9d5ecc59bd85b5a8495924df32a1773a0
This patch proposes a decorator to be used to profile code with
cProfile. Config options are added to control whether the code is
profiled or not. The default is no profiling performed.
The decorator is then used in the Neutron API base and Pecan controllers
for the index, show, create, delete and update operations. The rpc_loop
method of the OVS agent is also decorated.
Finally, profiling is enabled for neutron-rally-task.
Change-Id: I5c847a255b4b973add7fce5a38a2594912c491ac
Since it's no longer supported past Train, lets stop
running the tests.
Updated docs and made some pep8 code tweaks as well.
Change-Id: I1c171ab906a3b4c66558163ad26947ebf710a276
Neutron was using train jobs template: openstack-python3-train-jobs
but now we are in Ussuri cycle so let's switch to new template.
Change-Id: I99d9a048cab9d101740d96aa422f6fe596357c26
And also switch it to be inheriting from tempest-integrated-networking
to run only neutron and nova related tests on it and make it faster.
Change-Id: Ie7e03848fc5f1bb1425987d4413dd6c02045a879
This job runs nearly three hours, let's add the same irreleant-files
list as to all other tempest tests so that this does not run for doc
changes and translation imports.
Change-Id: I26a8c677f04ae8cffdeb0983cde072111693d0dc
opensuse-150 nodeset is referring to openSUSE 15.0, which is still in
maintenance but openSUSE 15.1 has been released already. "opensuse-15"
is going to refer to the "latest openSUSE 15.x" build released and
working for OpenStack going forward, so add this nodeset and use
it by default going forward.
This is the remaining work to be done after https://review.opendev.org/#/c/667539
got merged earlier
Change-Id: I6b3881a77de0419e0c3612661bf60cc2e55da0a7
Depends-On: https://review.opendev.org/#/c/682843
This patch sets UPPER_CONSTRAINTS_FILE that it points to file created by
zuul.
Due to this change requirements with "speculative future changes" can be
used in gate. So zuul will be now able to use requirements file from
patch which is also in gate but is not merged yet.
Change-Id: Ib3cc25460bea7030b4352fdc36147a0a16c7e422
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1],
Tempest has defined the new job 'tempest-ipv6-only'(adding
in Depends-On patch) which will deploy services on IPv6 and run smoke
tests and IPv6 related tests present in Tempest.
This job will be part of Nova, Neutron, Cinder, Keystone, Glance, Swift
gate.
Verification structure will be:
- 'devstack-IPv6' deploy the service on IPv6
- 'devstack-tempest-ipv6' run will verify the IPv6-only setting and listen address
- 'tempest-ipv6-only' will run the smoke + IPv6 related test case.
This commit adds the new job 'tempest-ipv6-only' run on gate.
Story: #2005477
Task: #35908
Depends-On: https://review.opendev.org/#/c/671231/
[1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
Change-Id: I6a1d8e40a8cb606b60ebede99bac7e570f761a5a
We need to change name of "tripleo-ci-centos-7-scenario007-standalone"
to not conflict with job defined in tripleo-ci.
Change-Id: Idb2272e8b17a0efc343cb68323a96f114d0c6f64
In commit [1] neutron replaced using "integrated-gate" template with
new "integrated-gate-networking" tempate to run only tests related
to Neutron and Nova in Neutron CI.
This patch switches tempest jobs defined in neutron directly:
* neutron-tempest-dvr
* neutron-tempest-linuxbridge
* neutron-tempest-iptables_hybrid
* neutron-tempest-with-uwsgi
to inherit from this new "tempest-integrated-networking" job and
run also only tests related to Neutron and Nova.
[1] https://review.opendev.org/#/c/669815/
Change-Id: I2aa60fa1aa98e79f8b2597e490c00f7410f2a93d
In commit [1] neutron replaced using "integrated-gate" template, which
provides tempest-full job with new "integrated-gate-networking" tempate,
which provides "tempest-integrated-networking" job to run only tests related
to Neutron and Nova in Neutron CI.
Unfortunatelly tempest-full and tempest-full-py3 jobs were also
configured in Neutron's zuul file separately so we ended up with running
all 3 of those jobs in our check and gate queue.
So this patch removed "tempest-full" and "tempest-full-py3" jobs from
Neutron's check and gate queue and left only new
"tempest-integrated-networking" job to be run there.
[1] https://review.opendev.org/#/c/669815/
Change-Id: Ia74454c0986d0ef24b9a42ab1e2e0f296511cd3f
This patch adds non-voting tripleo-ci-centos-7-scenario007-standalone
job which will use TripleO to deploy Neutron in containers.
Change-Id: I9593122c961002bc209a89a7fee129e49e6952a4
DVR does the ARP table update through the control plane, and does not
allow any ARP requests to get out of the node.
In order to address the allowed address pair VRRP IP issue with DVR,
we need to add an ARP entry into the ARP Responder table for the
allowed address pair IP ( which is taken care by the patch in [1])
This patch adds a rule in the br-int to redirect the packet
destinated to the router to the actual router-port and also moves
the arp filtering rule to the tunnel or the physical port based on the
configuration.
By adding the above rule it allows the ARP requests to reach the
ARP Responder table and filters the ARP requests before it reaches
the physical network or the tunnel.
[1] https://review.opendev.org/#/c/601336/
Related-Bug: #1774459
Change-Id: I3905ea56ca0ff35bdd96c818719e6d63a3eb5a72
This patch adds summary of Tempest and Grenade jobs which we
have run in Neutron's check and gate queues.
Change-Id: I8b96413b33f037b601747ebaa0ff4f0791cad628
This patch adds integration of osprofiler with rally.
Rally provides possibility for such integration and when
osprofiler is configured in rally it will now place
osprofiler's report for each rally test iteration in
"Scenario Data" tab.
Change-Id: I730de963ef6fd0485be6ea947d085067057a500c
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and
dropping unit tests for Python 3.5.
For Neutron, which already runs py36 and py37 unit tests it generally
means switch to use the Zuul template openstack-python3-train-jobs
for Train.
Using this template will ensure that all projects that support Python3
will be tested against the agreed runtime versions, and make it easier
to update them in future.
[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: I41d232a10a40d97347566e189457d8044e3639db
Depends-On: https://review.opendev.org/#/c/641878/
Since WSGI is more important, we should be collecting data on
compatibility more consistently. So we shall move the WSGI jobs from
the experimental queue to the check queue, while maintaining their
nonvoting status.
Change-Id: I24aa7a0c2245973327e4d74039f96a7efb2a8988
Slawek Kaplonski