1. Do not run tempest with own functional tests jobs.
It takes more time and don't allow to run fake-virt-rally job.
because scenarios' tests can't be passed with fake virt.
This fix sets to DEVSTACK_GATE_TEMPEST_NOTESTS 1,
in conjunction with DEVSTACK_GATE_TEMPEST. It will allow Tempest to be
installed and configured, but the tests will be skipped
2. Temporary switch off voting for tempest against ec2-api backend.
Current tempest has two incompatible tests -
diassociate_not_associated_address
and run instance by image/kernel/ramdisk(This feature
is broken in current nova code as I understood)
Change-Id: I7bad03ffb5e4fa3bc13457dc18bde7040458aa78
1. Enable tempest for rally gate. Only tempest preparation code has needed falvors creation -
flavors without disk(m1.nano for example). We need flavor without disk because only this can be
run with fakevirt driver due to bug https://bugs.launchpad.net/nova/+bug/1433994
2. Add calling hook script before running rally to setup specific things of third-party project.
For example - botocore. This library is absent in global requirements and can not be add to ec2-api
project. And global requirements is frozen now for adding new.
Change-Id: I9993c97ecb6900efefc8ae73107d8a06a9e6dcf6
Zuul expects the job to run on "devstack" workers because of the
"dsvm" in the job name (there's a zuul parameter function which
matches those up for convenience), but in this job definition I
have specified "bare" workers so that's all Jenkins registered for
it. As a result, zuul doesn't see any of the worker types it expects
registering that job name. I must correct the "node" parameter for
the gate-rally-dsvm-ec2-api-fakevirt job definition in
openstack-infra/project-config:jenkins/jobs/ec2-api.yaml then it
should work.
Change-Id: If5740498cb059e8219b2b9db4a4c565d2bc1b04e
In previous review
https://review.openstack.org/#/c/159138/
I tried to use existing rally job. But I skipped fact that in this job
ec2-api wouldn't loaded. Now I was trying to think up how this existing
job can be adapted to load ec2-api plugin. And simple way to do it -
is to create another job-template with needed shell script and needed params.
Change-Id: I3a95b298a70795601ef4002fc413e91960af0f2b
I made a typo in previous review with unbalanced parenthesis
https://review.openstack.org/#/c/154640/
Here is a fix with simplified regex
Change-Id: I918d53f5d911e29c08ebba29385962364dcbfe5f
Since most of api tests committed and worked -
https://review.openstack.org/#/c/154604/
I suggest to make ec2 gating jobs as 'voting'
and reduce tests scope of simple tempest job.
Change-Id: I933ee62ee58431a277c719fea9ef2732b4a04582
adding jobs that deploy devstack with neutron or without
next these jobs calls post script that runs functional tests
from EC2 project against deployed cloud.
Related change in EC2API project is here -
https://review.openstack.org/#/c/153827/
Change-Id: I95c2500f0a087c0a70d80322f40d3b85b266d1ad
This creates a non voting check job for ec2api changes that includes
setting up a devstack environment using an external devstack plugin in
a zuul compatible way. This is also a good reference for other teams
that would like test jobs which include devstack external plugins.
Change-Id: I8e31fd4f771e498efd5d8671acee0a3c3c8a184e