From: Anthony PERARD <anthony.perard@citrix.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [OSSTEST PATCH v7 2/3] ts-openstack-tempest: Run Tempest to check OpenStack
Date: Mon, 21 Nov 2016 17:50:44 +0000 [thread overview]
Message-ID: <20161121175044.GA1847@perard.uk.xensource.com> (raw)
In-Reply-To: <20161115214250.GB29122@x230.dumpdata.com>
On Tue, Nov 15, 2016 at 04:42:50PM -0500, Konrad Rzeszutek Wilk wrote:
> On Mon, Nov 14, 2016 at 12:33:33PM +0000, Anthony PERARD wrote:
> > + # Those tests access a volume through iSCSI. This does not work when both
> > + # the server and client of iSCSI are on the same Xen host, Linux 4.0 is the
> > + # first Linux to have a fix.
>
> What fix? Would it make sense to point this out? Also I am going to
> assume the 'server' and 'client' are guests, and 'server' is not dom0?
It was a patch series, I don't know if I can find it again. I thought
pointing to a release was enough.
I think iSCSI have other terms for 'server' and 'client', maybe 'target'
and something else. But those two sides are running in dom0, in this
test.
> > + push @ignored_tests,
> > + "^\Q${volume_boot_pattern}V2.test_volume_boot_pattern\E";
> > + push @ignored_tests,
> > + "^\Q${volume_boot_pattern}V2.test_create_ebs_image_and_check_boot\E";
> > +
> > + # This regex below select the tests to run and exclude the ones marked as
> > + # slow as well as the explicit tests listed above. It is based on the one
> > + # that can be found in tempest.git/tox.ini in the section [testenv:full].
> > + my $ignored_tests = join("|", @ignored_tests);
> > + my $regex =
> > + "(?!.*\\[.*\\bslow\\b.*\\]|$ignored_tests)(^tempest\\.(api|scenario|thirdparty))";
> > +
> > + target_cmd($ho, <<END, 7200);
> > + $builddir/tempest/run_tempest.sh --virtual-env -- --concurrency=2 '$regex'
>
>
> How come you are hardcoding 2?
By default, this number is equal to the number of cpus. I think it would
be too much, and increase the failure rate of openstack it self, which I
don't think it would be usefull to test.
For their CI loop, I think this is equal to half the number of cpus. We
could do that but I don't know if it's going to be usefull.
We do use 2 on the XenProject OpenStack CI loop, because I don't think
it can do more than that.
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-21 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 12:33 [OSSTEST PATCH v7 0/3] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
2016-11-14 12:33 ` [OSSTEST PATCH v7 1/3] ts-openstack-deploy: Deploy OpenStack on a host with devstack Anthony PERARD
2016-11-15 21:40 ` Konrad Rzeszutek Wilk
2016-11-18 18:51 ` Ian Jackson
2016-11-14 12:33 ` [OSSTEST PATCH v7 2/3] ts-openstack-tempest: Run Tempest to check OpenStack Anthony PERARD
2016-11-15 21:42 ` Konrad Rzeszutek Wilk
2016-11-21 17:50 ` Anthony PERARD [this message]
2016-11-14 12:33 ` [OSSTEST PATCH v7 3/3] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2016-11-18 18:57 ` Ian Jackson
2016-11-18 19:51 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161121175044.GA1847@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=konrad@kernel.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).