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 3/4] ts-devstack: Deploy OpenStack then test it with Tempest
Date: Fri, 17 Jul 2015 17:04:03 +0100	[thread overview]
Message-ID: <1437149043.22698.11.camel@citrix.com> (raw)
In-Reply-To: <1437045519-13914-4-git-send-email-anthony.perard@citrix.com>

On Thu, 2015-07-16 at 12:18 +0100, Anthony PERARD wrote:
> +    cd $builddir/devstack
> +    >local.conf
> +    echo >>local.conf '[[local|localrc]]'
> +    echo >>local.conf ADMIN_PASSWORD=`pwgen 20 1`
> +    echo >>local.conf DATABASE_PASSWORD=`pwgen 20 1`
> +    echo >>local.conf RABBIT_PASSWORD=`pwgen 20 1`
> +    echo >>local.conf SERVICE_PASSWORD=`pwgen 20 1`
> +    echo >>local.conf SERVICE_TOKEN=`pwgen 20 1`
> +    echo >>local.conf \\\# make it small because there is no way to not
> +    echo >>local.conf \\\# have this lvm volume created
> +    echo >>local.conf VOLUME_BACKING_FILE_SIZE=500M
> +    echo >>local.conf DEST=/opt/stack
> +    echo >>local.conf LOGFILE=\\\$DEST/logs/stack.sh.log
> +    echo >>local.conf LOG_COLOR=False
> +    echo >>local.conf LIBVIRT_TYPE=xen
> +    echo >>local.conf GIT_BASE="$openstack_git_base"
> +    echo >>local.conf disable_service horizon
> +    echo >>local.conf disable_service n-novnc
> +    echo >>local.conf enable_service n-obj
> +    echo >>local.conf '[[post-config|\$CINDER_CONF]]'
> +    echo >>local.conf '[lvmdriver-1]'
> +    echo >>local.conf volume_group = $vg

target_putfilecontents_root_stash with a Perl here doc would be  better
I think?

> +[...]+
> +  # OpenStack needs access to libvirt from a user.
> +  target_cmd_root($ho, <<END
> +    echo >>/etc/libvirt/libvirtd.conf 'unix_sock_group = "libvirt"'
> +    echo >>/etc/libvirt/libvirtd.conf 'unix_sock_ro_perms = "0777"'
> +    echo >>/etc/libvirt/libvirtd.conf 'unix_sock_rw_perms = "0770"'

This one should be a bash heredoc, I think (can't be a Perl one because
this is an append?).

> +sub cleanup() {
> +  # Try to have less leaked stuff.

Leaked as in "discovered by ts-leak-check" or just a general tidy up?

If the latter I wouldn't bother.

If the former then won't this hide real issues?

Ian.

  reply	other threads:[~2015-07-17 16:04 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
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 [this message]
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=1437149043.22698.11.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.