xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [OSSTEST PATCH v11 18/20] ts-logs-capture: Capture OpenStack logs
Date: Fri, 23 Jun 2017 16:31:30 +0100	[thread overview]
Message-ID: <20170623153130.GH1702@perard.uk.xensource.com> (raw)
In-Reply-To: <22861.7255.364739.487419@mariner.uk.xensource.com>

On Fri, Jun 23, 2017 at 02:49:11PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("[OSSTEST PATCH v11 18/20] ts-logs-capture: Capture OpenStack logs"):
> > +                  /var/log/openstack/*.log
> > +                  /etc/nova/*
> > +                  /etc/neutron/*
> > +                  /etc/cinder/*
> 
> This is fine:
> 
> > +                  /home/osstest/build.*.test-*-devstack/tempest/etc/tempest.conf
> 
> This is not fine.  If a build host is shared, it will collect all the
> logs from all of the builds.

This file should not exist on a build host, as it would be created by
ts-openstack-deploy which I hope is not run on a build host.

We are only using using target_jobdir() to have a directory to clone all
the OpenStack repo and run ./devstack.

But I can find a way to copy this file somewhere else.

> I think build ts-* scripts ought to collect their own logs.

Do you mean I can capture logs like ts-logs-capture would do, but before
it is been run?

ts-openstack-deploy could collect all the configuration file then, like
/etc/nova/*.

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-06-23 15:32 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16 17:56 [OSSTEST PATCH v11 00/20] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 01/20] ts-openstack-deploy: Deploy OpenStack on a host with devstack Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 02/20] ts-openstack-tempest: Run Tempest to check OpenStack Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 03/20] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 04/20] ts-openstack-deploy: Set http proxy Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 05/20] TestSupport: provide target_https_mitm_proxy_cert_path Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 06/20] ts-openstack-deploy: set CURL_CA_BUNDLE Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 07/20] ts-openstack-deploy: Keep CURL_CA_BUNDLE when sudo is called Anthony PERARD
2017-06-23 13:37   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 08/20] ts-openstack-deploy: Try to disable use of SYSTEMD Anthony PERARD
2017-06-23 13:38   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 09/20] ts-kernel-build: Enable network related modules for Neutron Anthony PERARD
2017-06-23 13:39   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 10/20] ts-openstack-deploy: Switch to Neutron for network Anthony PERARD
2017-06-23 13:41   ` Ian Jackson
2017-06-23 14:10     ` Anthony PERARD
2017-06-23 14:18       ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 11/20] ts-openstack-deploy: Increase fd and memory limits for rabbitmq Anthony PERARD
2017-06-23 13:41   ` Ian Jackson
2017-06-23 14:35     ` Anthony PERARD
2017-06-23 15:34       ` Ian Jackson
2017-06-23 16:50         ` Anthony PERARD
2017-06-23 17:16           ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 12/20] make-flight: Increase dom0_mem for openstack flight Anthony PERARD
2017-06-23 13:42   ` Ian Jackson
2017-06-23 14:40     ` Anthony PERARD
2017-06-23 15:35       ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 13/20] ts-openstack-deploy: Apply a Tempest patch Anthony PERARD
2017-06-23 13:43   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 14/20] ts-openstack-deploy: Ignore libvirt-python version and use latest Anthony PERARD
2017-06-23 13:44   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 15/20] ts-openstack-tempest: Fix tempest invocation Anthony PERARD
2017-06-23 13:45   ` Ian Jackson
2017-06-23 14:49     ` Anthony PERARD
2017-06-16 17:57 ` [OSSTEST PATCH v11 16/20] ts-openstack-tempest: Update list of skipped tests Anthony PERARD
2017-06-23 13:47   ` Ian Jackson
2017-06-23 15:16     ` Anthony PERARD
2017-06-23 15:38       ` Ian Jackson
2017-06-30 16:11         ` Anthony PERARD
2017-06-30 16:32           ` Ian Jackson
2017-06-30 17:58             ` Anthony PERARD
2017-07-05 14:33               ` Anthony PERARD
2017-06-16 17:57 ` [OSSTEST PATCH v11 17/20] ts-openstack-deploy: Move logs to /var/log/openstack Anthony PERARD
2017-06-23 13:48   ` Ian Jackson
2017-06-16 17:57 ` [OSSTEST PATCH v11 18/20] ts-logs-capture: Capture OpenStack logs Anthony PERARD
2017-06-23 13:49   ` Ian Jackson
2017-06-23 15:31     ` Anthony PERARD [this message]
2017-06-23 15:42       ` Ian Jackson
2017-06-16 17:57 ` [OSSTEST PATCH v11 19/20] ts-openstack-deploy: Increase devstack timeout Anthony PERARD
2017-06-23 13:49   ` Ian Jackson
2017-06-16 17:57 ` [OSSTEST PATCH v11 20/20] Introduce flight for stable branches of OpenStack Anthony PERARD
2017-06-23 13:58   ` Ian Jackson
2017-06-23 16:26     ` Anthony PERARD
2017-06-23 16:47       ` Ian Jackson
2017-06-23 17:00   ` Ian Jackson
2017-06-30 16:51     ` Anthony PERARD
2017-07-03 11:00       ` Ian Jackson
2017-06-19 11:02 ` [OSSTEST PATCH v11 00/20] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD

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=20170623153130.GH1702@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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).