To limit usage of resources (mostly memory) in the fullstack job and
to avoid oom killer to kill e.g. mysqld service, this patch:
* Makes number of API workers changeable by tests, as a parameter to
EnvironmentDescription and defaults its value to 1. As neutron server
is spawned separately for each test and is used only to process just
few API requests during that single test so this should be still
enough there, and where more API workers are needed (like some dhcp HA
tests: TestDhcpAgentHARaceCondition) it can be changed,
* reduces number of test run workers from 4 to 3 - job will run slower
but hopefully more stable,
* in the functional and fullstack tests job definition disable etcd3
service - this will not save us a lot of memory but still it's not
needed at all so why to run it there.
Conflicts:
neutron/tests/fullstack/resources/environment.py
neutron/tests/fullstack/test_dhcp_agent.py
zuul.d/base.yaml
Change-Id: If19803ab6db144e2d17d6805d379c1c76d8fa343
Closes-Bug: #1906366
(cherry picked from commit f63dc09206a41c85edc92117c3e9cf3a3d49b820)
It was disabled in previous commit to allow pip resolver fixes for
neutron and networking-ovn to go in. Once the later is merged, we can
get the job back
Change-Id: Iafa68a98861f971f62c373d69e16c4dbaad383e9
Depends-On: https://review.opendev.org/c/openstack/networking-ovn/+/767424
Content provider job builds and shares the artifacts among
consumer jobs. This removes dependency on docker.io pulls.
Conflicts:
zuul.d/project.yaml
Change-Id: Ib2b9f541e6e287c3b0bfd091310e3ce267fc6adb
(cherry picked from commit e0e7f1b64e16a12f57201d316708f44cd3556fc8)
These jobs are used to test neutron against current master branches of
external projects (os-ken).
Stable branches are not expected to run with this setup so we can drop
the jobs there (especially as some of these jobs are periodic ones).
Conflicts:
.zuul.yaml
This is adapted to the older single .zuul.yaml file layout
Change-Id: I2b1f4c4e951b691fb0c66119699b26540b0babd8
(cherry picked from commit 21719a875d63adc9a823de7feacb119e5887f5af)
This commit migrates neutron-grenade multinode jobs.
This is manual backport of this as zuul dir structure is
changed in ussuri and clean backport is not possible.
- https://review.opendev.org/#/c/735948/3
Change-Id: I20533a034d28d5e405b3f7d49855cdc8e0815e90
Master branch now has requirements incompatible with stable branches
constraints [0], so this switches to last tag compatible.
Longer term fix will be to run rally in a virtualenv, but this is lower
priority than other tasks. This can be revisited at the time, though for
older branches we will probably stick with pinned version
[0] 5776e015f1
Change-Id: I24fad07d3a15c62d4de711a957f19d375862c28d
Closes-Bug: #1868691
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.
Fedora jobs also make less sense for stable branches
Change-Id: If0adb7ca4e254f5b19375b471679bcc18e0c7790
(cherry picked from commit a2fdf8aa72859be748918d56c819736b9ae048c2)
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
(cherry picked from commit 0528068a35b8ffecaf69d1cffb325604b97d30ed)
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
This reverts commit 13a2f70024e9a35c0ffc3142a23d9381d7c64d10.
Related bug is fixed so we can switch grenade jobs to be voting again.
Change-Id: I027208171a85ea7f2ce8b61d46121f507e826a34
Related-bug: #1820892
Now that tripleo has shifted to use OVN by default, introducing bugs
that break OVN will have a side-effect of breaking tripleo. Make the
crosscheck job for OVN voting to avoid those kinds of issues.
Change-Id: I190f7272ae468a8f6cd9d68f33103490f0bacf62
The job has been stable, shows failure percentages within a percent or
two of the neutron-tempest-iptables_hybrid job, and is forward looking
for the next version of RHEL/Centos.
Change-Id: Iafccd55269b64d29aee081f096f6352ab5c15430
Until related bug will not be fixed, grenade jobs are failing quite
often. Lets make them non voting to make our life easier.
This can be reverted when related bug will be fixed.
Change-Id: Iefe8d6ab2eea3e04e40cbf4ffaf0c646b51834c4
Related-Bug: #1820892
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: I4c9b513eb65ec4c50bdb9a66dfcc676360bdaa28
