In the Neutron CI meeting on 2018-10-02 [1] we decided on the proper
approach for fullstack testing of Neutron in Zuul. The approach is:
1. There should be only one fullstack CI job, named "neutron-fullstack"
2. The neutron-fullstack job should invoke python3 in tox.ini
This change implements the agreed-upon approach.
Switching the nodeset to newer OS will be handled in a separate step
[1] http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-10-02-16.00.html
Co-Authored-By: Nate Johnston <nate.johnston@redhat.com>
Change-Id: I37c1cb42b3a94532e7b7fea21a929a39fe63f00b
This reverts commit 0014c0c3734e8d344e4a45e127fbd0c86dcfaf3c.
This is handled generically now with this change and its dependency:
https://review.openstack.org/#/c/606853/
Change-Id: I360211cf60afb5611fb9e77fe6332fa59159708f
In order to get openstack/placement installed as part of the
neutron grenade jobs, we have to list it as a required project.
Needed by https://review.openstack.org/604454/
Change-Id: I742660f398b52c62503acf00aaf7faa9a5a8650a
This job is defined in Tempest to replace
neutron-tempest-multinode-full which was job defined
in Neutron's repo.
This job is set as non-voting in Neutron because old
neutron-tempest-multinode-full job was non-voting also.
If stability of this new job will be fine for us, we
can switch it to voting later.
Depends-On: https://review.openstack.org/#/c/598610/
Change-Id: I2dcbf4ade83760797b4e5072f0e05dac877842c9
This patch adds exprimental tempest, functional and fullstack
jobs when neutron-api is served by a webserver as a part of
community goal.
Change-Id: Id88ca1a6997d39bf0d14589c0a2725b4ac109cec
In commit [1] openvswitch firewall driver is switched to be
default one used in devstack.
So various tempest jobs will use this driver and it will be
tested.
We now need separate job to test non-default firewall driver
which currently is iptables-hybrid driver.
[1] https://review.openstack.org/#/c/568297/
Depends-On: https://review.openstack.org/#/c/568297/
Change-Id: I6061a173c95c8a41a61bfa298ae5964cc9b5d2e8
Rally team finally added native Zuul V3 jobs (with a bunch of separate
roles and etc) and for simplification of maintainance, it would be nice
to use them.
Change-Id: I755e776a7c24e1bcdf144d7af071a52633aeb94d
As part of community goal to have services working with Python 3.5, this
patch adds back the exeperimental Python 3.5 functional and fullstack jobs
that got lost somewhere during zuul v3 migration.
Change-Id: I24506b94f3f4e111b3968e57deb683e9c874941c
We already have tempest-full job that is identical and defined elsewhere
(in tempest repo) that is part of our queues.
Change-Id: I788973513ec17bcc0df362dd42783dcc7aa8e452
When at least one service named as q-* is present in ENABLED_SERVICES,
then devstack utilizes lib/neutron-legacy to configure services
regardless of how other services are deployed (e.g. with lib/neutron).
This breaks deployment using lib/neutron.
Switching to new names doesn't change anything substantial because
devstack plugin equally handles both variants. It allows to use new
devstack neutron library though.
Change-Id: Id0d35523651131766a70e78bf130205c1c63acd5