From: Ian Campbell <ian.campbell@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST 2/4] Toolstack: Add OpenStack as a toolstack.
Date: Fri, 17 Jul 2015 16:58:16 +0100 [thread overview]
Message-ID: <1437148696.22698.6.camel@citrix.com> (raw)
In-Reply-To: <1437045519-13914-3-git-send-email-anthony.perard@citrix.com>
On Thu, 2015-07-16 at 12:18 +0100, Anthony PERARD wrote:
> Having a separate toolstack help to configure the host specificly for
"specifically"
> OpenStack, and also helps to have a separate flight.
Will any of the die()s here ever become real commands? I think not
because that's not how OpenStack works? i.e. how it is driven doesn't
fit into Osstest::Toolstack's model of the world at all.
Given that and given that you introduce your own recipe to sg-run-job
which doesn't/can't/won't try to do any of the usual stuff, I can't see
any reason not to simply go with toolstack=libvirt for these test cases.
That it is the most accurate reflection of what we want and if some
openstack test case did want to talk to the underlying toolstack for
some reason libvirt would be it.
That would also save duplicating the functionality of libvirt.pm's new
function, which would normally call for a subclass of some sort (e.g.
how xend is a subclass of xl). Please don't do this though ;-)
>
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> ---
> Osstest/Toolstack/openstack.pm | 81 ++++++++++++++++++++++++++++++++++++++++++
> ts-xen-install | 1 +
> 2 files changed, 82 insertions(+)
> create mode 100644 Osstest/Toolstack/openstack.pm
>
> diff --git a/Osstest/Toolstack/openstack.pm b/Osstest/Toolstack/openstack.pm
> new file mode 100644
> index 0000000..4529845
> --- /dev/null
> +++ b/Osstest/Toolstack/openstack.pm
> @@ -0,0 +1,81 @@
> +# This is part of "osstest", an automated testing framework for Xen.
> +# Copyright (C) 2015 Citrix Inc.
> +#
> +# This program is free software: you can redistribute it and/or modify
> +# it under the terms of the GNU Affero General Public License as published by
> +# the Free Software Foundation, either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> +# GNU Affero General Public License for more details.
> +#
> +# You should have received a copy of the GNU Affero General Public License
> +# along with this program. If not, see <http://www.gnu.org/licenses/>.
> +
> +
> +package Osstest::Toolstack::openstack;
> +
> +use strict;
> +use warnings;
> +
> +use Osstest::TestSupport;
> +
> +sub new {
> + my ($class, $ho, $methname,$asset) = @_;
> + my @extra_packages = qw(git pwgen sudo);
> + # package from libvirt
> + push(@extra_packages, qw(libavahi-client3));
> + my $nl_lib = "libnl-3-200";
> + $nl_lib = "libnl1" if ($ho->{Suite} =~ m/wheezy/);
> + push(@extra_packages, $nl_lib);
> + return bless { Name => "openstack",
> + Host => $ho,
> + NewDaemons => [qw(libvirtd)],
> + Dom0MemFixed => 0,
> + ExtraPackages => \@extra_packages,
> + }, $class;
> +}
> +
> +sub destroy ($$) {
> + my ($self,$gho) = @_;
> + die "Guest control not yet supported via OpenStack";
> +}
> +
> +sub create ($$) {
> + my ($self,$gho) = @_;
> + die "Guest control not yet supported via OpenStack";
> +}
> +
> +sub consolecmd ($$) {
> + my ($self,$gho) = @_;
> + die "Guest control not yet supported via OpenStack";
> +}
> +
> +sub shutdown_wait ($$$) {
> + my ($self,$gho,$timeout) = @_;
> + die "Guest control not yet supported via OpenStack";
> +}
> +
> +sub migrate_check ($) {
> + my ($self) = @_;
> + die "Guest control not yet supported via OpenStack";
> +}
> +
> +sub migrate ($) {
> + my ($self,$gho,$dst,$timeout) = @_;
> + die "Guest control not yet supported via OpenStack";
> +}
> +
> +sub save ($$$$) {
> + my ($self,$gho,$f,$timeout) = @_;
> + die "Guest control not yet supported via OpenStack";
> +}
> +
> +sub restore ($$$$) {
> + my ($self,$gho,$f,$timeout) = @_;
> + die "Guest control not yet supported via OpenStack";
> +}
> +
> +1;
> diff --git a/ts-xen-install b/ts-xen-install
> index 0f53382..e7e823d 100755
> --- a/ts-xen-install
> +++ b/ts-xen-install
> @@ -72,6 +72,7 @@ sub packages () {
> sub extract () {
> my @parts = ('', 'kern', 'xen');
> push @parts, 'libvirt' if $r{toolstack} eq "libvirt";
> + push @parts, 'libvirt' if $r{toolstack} eq "openstack";
>
> foreach my $part (@parts) {
> target_extract_jobdistpath($ho, $part, "path_${part}dist",
next prev parent reply other threads:[~2015-07-17 15:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 11:18 [PATCH OSSTEST 0/4] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
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 [this message]
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=1437148696.22698.6.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@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).