From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [OSSTEST PATCH v7 3/3] Create a flight to test OpenStack with xen-unstable and libvirt
Date: Fri, 18 Nov 2016 14:51:48 -0500 [thread overview]
Message-ID: <20161118195148.GB8933@char.us.oracle.com> (raw)
In-Reply-To: <22575.20272.425798.591489@mariner.uk.xensource.com>
On Fri, Nov 18, 2016 at 06:57:52PM +0000, Ian Jackson wrote:
> Anthony PERARD writes ("[Xen-devel] [OSSTEST PATCH v7 3/3] Create a flight to test OpenStack with xen-unstable and libvirt"):
> > This patch should create a flight "openstack-nova", with those jobs:
>
> Did I already ask for a diff of the output of
> standalone-generate-dump-flight-runvars
> before and after ?
You asked that on my patch set :-)
Perhaps it should be part of the README.devel?
>
> You probably want
> AP_FETCH_PLACEHOLDERS=y eatmydata ./standalone-generate-dump-flight-runvars
>
> Your new shell code is mostly good. I have a style comment:
>
> > +define_openstack_trees() {
> > + local openstack_trees=(cinder glance keystone nova requirements tempest)
>
> The use of an array variable here is not necessary since none of these
> contain spaces. I don't object, except that:
>
> > + for tree in ${openstack_trees[@]}; do
>
> This sets off my style alarm because of the lack of "" around a
> ${something[@]} (which off course doesn't matter here.
>
> Can you either add the " ", or switch to a plain (space-separated)
> variable.
>
> > + for tree in ${openstack_trees[@]}; do
>
> Here too.
>
> Aside from that, and assuming the runvars diff is good, this is
> looking good.
I concur. I used his patchset to grok the OSSTest.
>
> Ian.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-11-18 19:51 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
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 [this message]
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=20161118195148.GB8933@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.