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>
Subject: [OSSTEST PATCH v7 0/3] Have OpenStack tested on top of xen's master and libvirt's master.
Date: Mon, 14 Nov 2016 12:33:31 +0000 [thread overview]
Message-ID: <20161114123334.5585-1-anthony.perard@citrix.com> (raw)
Hi,
I have looked into getting OpenStack been tested on the latest Xen via
osstest.
The ts-openstack-deploy script does prepare a bit more the host, clone
devstack and other OpenStack trees, then run ./stack.sh, which is a bit
like raisin and deploy OpenStack on the host. Once the machine is ready,
the integration test suite from OpenStack, Tempest, is started by
ts-openstack-tempest.
Thanks.
Changes in V7:
- few changes detailed in patches
Changes in V6:
- rebased
- fix ts-openstack-deploy script to work with newer devstach and new debian.
Change in V5:
- on small change in patch 1, but I keeped the acked-by
- few changes in the way the flight is created (in the last patch)
Change in V4:
few changes listed in second and third patch, mostly cleanup.
Change in V3:
- Track Nova tree instead of devstack.
Nova is the service we care about from a Xen point of view.
Also it is updated much more often than devstack.
- Cleanups, see change log in patches.
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 (3):
ts-openstack-deploy: Deploy OpenStack on a host with devstack
ts-openstack-tempest: Run Tempest to check OpenStack
Create a flight to test OpenStack with xen-unstable and libvirt
ap-common | 18 +++++++
ap-fetch-version | 4 ++
ap-fetch-version-old | 5 ++
ap-print-url | 3 ++
ap-push | 5 ++
cr-daily-branch | 8 ++++
cr-for-branches | 2 +-
cri-common | 1 +
make-flight | 48 +++++++++++++++++++
sg-run-job | 6 +++
ts-openstack-deploy | 132 +++++++++++++++++++++++++++++++++++++++++++++++++++
ts-openstack-tempest | 64 +++++++++++++++++++++++++
12 files changed, 295 insertions(+), 1 deletion(-)
create mode 100755 ts-openstack-deploy
create mode 100755 ts-openstack-tempest
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-11-14 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 12:33 Anthony PERARD [this message]
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
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=20161114123334.5585-1-anthony.perard@citrix.com \
--to=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 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).