From: Anthony PERARD <anthony.perard@citrix.com>
To: xen-devel@lists.xen.org
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH OSSTEST 0/4] Have OpenStack tested on top of xen's master and libvirt's master.
Date: Thu, 16 Jul 2015 12:18:35 +0100 [thread overview]
Message-ID: <1437045519-13914-1-git-send-email-anthony.perard@citrix.com> (raw)
Hi,
I have looked into getting OpenStack been tested on the latest Xen via
osstest. There is an adjustement in common code to accomodate OpenStack,
this is an extra Linux config option. Otherwise anything else should be
done only if a Toolstack named "openstack" is to be used for testing.
I've introduce an extra Osstest::Toolstack which help to install extra
package, and use ballonning for Dom0, 500MB for Dom0 is definetly not
enough.
The ts-devstack script does prepare a bit more the host, clone devstack,
then run ./stack.sh, which is a bit like raisin. Once the machine ready,
the integration test suite from OpenStack, Tempest, is started. Do you
think those two step should be in separate test, one for devstack, and one
for Tempest? I have not done it, but we could have some smoke test before
Tempest where osstest tryied to start a guest.
For the last patch, I've tried to have ./standalone make-flight have only
the necessary jobs to run test-amd64-amd64-devstack, but there is still
build-xsm in the list.
Then later, there will be the question of which tree to track, devstack?
nova? Or don't track any and just test with the master branch from time to
time.
Thanks,
Anthony PERARD (4):
ts-kernel-build: Enable CONFIG_NETFILTER_XT_TARGET_CHECKSUM
Toolstack: Add OpenStack as a toolstack.
ts-devstack: Deploy OpenStack then test it with Tempest
Create a flight to test OpenStack with xen-unstable and libvirt.
Osstest/Toolstack/openstack.pm | 81 +++++++++++
ap-common | 4 +
ap-fetch-version | 4 +
ap-fetch-version-old | 5 +
ap-print-url | 3 +
cri-common | 1 +
make-flight | 17 +++
mfi-common | 7 +
sg-run-job | 5 +
ts-devstack | 305 +++++++++++++++++++++++++++++++++++++++++
ts-kernel-build | 5 +
ts-xen-install | 1 +
12 files changed, 438 insertions(+)
create mode 100644 Osstest/Toolstack/openstack.pm
create mode 100755 ts-devstack
--
Anthony PERARD
next reply other threads:[~2015-07-16 11:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 11:18 Anthony PERARD [this message]
2015-07-16 11:18 ` [PATCH OSSTEST 1/4] ts-kernel-build: Enable CONFIG_NETFILTER_XT_TARGET_CHECKSUM Anthony PERARD
2015-07-17 15:48 ` Ian Campbell
2015-07-16 11:18 ` [PATCH OSSTEST 2/4] Toolstack: Add OpenStack as a toolstack Anthony PERARD
2015-07-17 15:58 ` Ian Campbell
2015-07-17 16:32 ` Anthony PERARD
2015-07-17 16:45 ` Ian Campbell
2015-07-16 11:18 ` [PATCH OSSTEST 3/4] ts-devstack: Deploy OpenStack then test it with Tempest Anthony PERARD
2015-07-17 16:04 ` Ian Campbell
2015-07-20 14:12 ` Anthony PERARD
2015-07-20 14:31 ` Ian Campbell
2015-07-17 16:10 ` Ian Campbell
2015-07-20 14:16 ` Anthony PERARD
2015-07-16 11:18 ` [PATCH OSSTEST 4/4] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2015-07-17 16:08 ` Ian Campbell
2015-07-17 15:51 ` [PATCH OSSTEST 0/4] Have OpenStack tested on top of xen's master and libvirt's master Ian Campbell
2015-07-17 16:22 ` Ian Campbell
2015-07-20 15:07 ` Anthony PERARD
2015-07-20 15:27 ` Ian Jackson
2015-07-20 15:35 ` Ian Campbell
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=1437045519-13914-1-git-send-email-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@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 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).