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 v2 0/6] Have OpenStack tested on top of xen's master and libvirt's master.
Date: Thu, 6 Aug 2015 18:03:25 +0100 [thread overview]
Message-ID: <1438880611-13244-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 a few extra Linux config option.
The ts-openstack-devstack script does prepare a bit more the host, clone
devstack and other OpenStack trees, then run ./stack.sh, which is a bit
like raisin. Once the machine is ready, the integration test suite from
OpenStack, Tempest, is started by ts-openstack-tempest.
For the last patch that create a flight plan, I've tested only with
`./standalone make-flight openstack` and looked into the database to check
that only the necessary build job and the only test job are there.
Thanks.
Changes in V2:
- no more Osstest::Toolstack::OpenStack.
- osstest now clone every single tree that devstack is going to need.
And ./stack.sh should fail if one tree is missing.
- avoid build-*-xsm for an openstack flight
- rename ts-devstack to ts-openstack-devstack
- New test script ts-openstack-tempest
- Add CONFIG_CRYPTO_XTS=m to the kernel build.
- new possible runvar $dom0_mem to control dom0 memory
- several fix to have volume tests working.
- have OpenStack deploy from it's builddir instead of /opt/stack
- have 4GB for dom0 instead of relying on balloning.
Anthony PERARD (6):
ts-kernel-build: Enable CONFIG_NETFILTER_XT_TARGET_CHECKSUM
ts-kernel-build: Compile CONFIG_CRYPTO_XTS in
ts-xen-install: Add dom0_mem runvar to control dom0 memory
ts-openstack-devstack: Deploy OpenStack on a host
ts-openstack-tempest: Run Tempest to check OpenStack
Create a flight to test OpenStack with xen-unstable and libvirt
ap-common | 9 ++
ap-fetch-version | 4 +
ap-fetch-version-old | 5 +
ap-print-url | 3 +
cri-common | 1 +
make-flight | 42 ++++++-
mfi-common | 5 +
sg-run-job | 6 +
ts-kernel-build | 8 ++
ts-openstack-devstack | 304 ++++++++++++++++++++++++++++++++++++++++++++++++++
ts-openstack-tempest | 35 ++++++
ts-xen-install | 3 +-
12 files changed, 423 insertions(+), 2 deletions(-)
create mode 100755 ts-openstack-devstack
create mode 100755 ts-openstack-tempest
--
Anthony PERARD
next reply other threads:[~2015-08-06 17:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 17:03 Anthony PERARD [this message]
2015-08-06 17:03 ` [PATCH OSSTEST v2 1/6] ts-kernel-build: Enable CONFIG_NETFILTER_XT_TARGET_CHECKSUM Anthony PERARD
2015-08-06 17:03 ` [PATCH OSSTEST v2 2/6] ts-kernel-build: Compile CONFIG_CRYPTO_XTS in Anthony PERARD
2015-09-08 11:45 ` Ian Campbell
2015-08-06 17:03 ` [PATCH OSSTEST v2 3/6] ts-xen-install: Add dom0_mem runvar to control dom0 memory Anthony PERARD
2015-09-08 11:48 ` Ian Campbell
2015-09-08 12:52 ` Ian Campbell
2015-08-06 17:03 ` [PATCH OSSTEST v2 4/6] ts-openstack-devstack: Deploy OpenStack on a host Anthony PERARD
2015-09-08 13:03 ` Ian Campbell
2015-09-08 14:36 ` Ian Jackson
2015-09-25 12:36 ` Anthony PERARD
2015-09-25 12:35 ` Anthony PERARD
2015-09-25 12:45 ` Ian Campbell
2015-08-06 17:03 ` [PATCH OSSTEST v2 5/6] ts-openstack-tempest: Run Tempest to check OpenStack Anthony PERARD
2015-09-08 13:06 ` Ian Campbell
2015-09-25 13:04 ` Anthony PERARD
2015-09-25 13:17 ` Ian Campbell
2015-09-25 13:54 ` Ian Jackson
2015-08-06 17:03 ` [PATCH OSSTEST v2 6/6] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2015-09-08 13:14 ` Ian Campbell
2015-09-25 13:10 ` Anthony PERARD
2015-09-09 16:13 ` [PATCH OSSTEST v2 0/6] Have OpenStack tested on top of xen's master and libvirt's master 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=1438880611-13244-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).