All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 1/3] ts-openstack-deploy: Deploy OpenStack on a host with devstack
Date: Wed, 30 Sep 2015 09:29:51 +0100	[thread overview]
Message-ID: <1443601791.16718.149.camel@citrix.com> (raw)
In-Reply-To: <20150929161956.GK1623@perard.uk.xensource.com>

On Tue, 2015-09-29 at 17:19 +0100, Anthony PERARD wrote:
> On Tue, Sep 29, 2015 at 04:34:44PM +0100, Ian Campbell wrote:
> > On Mon, 2015-09-28 at 16:56 +0100, Anthony PERARD wrote:
> > > This script installs any necessary packages and clones all of the
> > > OpenStack
> > > trees which are used by devstack to deploy OpenStack.
> > > 
> > > Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> > 
> > This mostly looks good to me. A few comments.
> > 
> > > +  # libvirt is already installed, but not as a package, so avoid
> > > installation of
> > > +  # the libvirt package with devstack
> > > +  target_editfile($ho, "$builddir/devstack/files/debs/nova", sub {
> > > +      while (<EI>) {
> > > +        next if m/.*libvirt.*/;
> > > +        print EO or die $!;
> > > +      }
> > > +  });
> > > +  target_editfile($ho,
> > > "$builddir/devstack/lib/nova_plugins/functions
> > > -libvirt", sub {
> > > +      while (<EI>) {
> > > +        next if m/install_package.*libvirt.*/;
> > > +        print EO or die $!;
> > > +      }
> > > +  });
> > 
> > Do these end up causing the built_revision_foo to say "-dirty" or
> > anything
> > like that?
> > 
> > Maybe not because I don't see any calls to store_vcs_revision, which I
> > think we discussed on an earlier revision?
> 
> I'm only using build_clone() from osstest to clone any git tree. devstack
> is not allowed to clone anything (because of ERROR_ON_CLONE=True in its
> config file). So I don't need to call store_vcs_revision, and the tree
> will
> not be seen as -dirty from osstest.

I'd forgotten that build_clone also called store_vcs_clone, sorry.


> > +  # OpenStack needs access to libvirt from a user.
> > > +  target_cmd_root($ho, <<END);
> > 
> > You could use target_putfilecontents_root_stash for this too I think?
> 
> Well, this append things to the config files, and we thought bash HEREDOC
> was
> "the right answer" ( <1437402707.17368.39.camel@citrix.com> ).
> 
> The next line of the patch is:
> > +    cat >> /etc/libvirt/libvirtd.conf <<EOF

Ah yes, I'd forgotten about that, sorry.

So given that I think what I meant to say last time was:

Acked-by: Ian Campbell <ian.campbell@citrix.com>

  parent reply	other threads:[~2015-09-30  8:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 15:56 [PATCH OSSTEST v3 0/3] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
2015-09-28 15:56 ` [PATCH OSSTEST v3 1/3] ts-openstack-deploy: Deploy OpenStack on a host with devstack Anthony PERARD
2015-09-29 15:34   ` Ian Campbell
2015-09-29 16:19     ` Anthony PERARD
2015-09-29 17:04       ` Ian Jackson
2015-09-30  8:29       ` Ian Campbell [this message]
2015-09-29 17:02     ` Ian Jackson
2015-09-30  8:32   ` Ian Campbell
2015-09-30 10:52     ` Ian Jackson
2015-09-28 15:56 ` [PATCH OSSTEST v3 2/3] ts-openstack-tempest: Run Tempest to check OpenStack Anthony PERARD
2015-09-29 15:43   ` Ian Campbell
2015-09-29 17:15     ` Anthony PERARD
2015-09-30  8:38       ` Ian Campbell
2015-09-28 15:56 ` [PATCH OSSTEST v3 3/3] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2015-09-29 15:49   ` Ian Campbell
2015-09-29 17:21     ` Anthony PERARD
2015-09-29 16:52   ` Ian Jackson
2015-10-08 16:08     ` Ian Campbell
2015-10-08 16:42       ` Ian Jackson
2015-10-09 10:54         ` Anthony PERARD
2015-10-13 11:02           ` Ian Jackson
2015-10-13 11:39             ` 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=1443601791.16718.149.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 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.