All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Mehdi Abaakouk <sileht@sileht.net>
Cc: Mark Nelson <mark.nelson@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: About teuthology
Date: Tue, 31 Jul 2012 15:01:56 -0700	[thread overview]
Message-ID: <501855D4.5070101@inktank.com> (raw)
In-Reply-To: <20120731161633.GB23001@mail.sileht.net>

On 07/31/2012 09:16 AM, Mehdi Abaakouk wrote:
> On Tue, Jul 31, 2012 at 09:27:54AM -0500, Mark Nelson wrote:
>> On 7/31/12 8:59 AM, Mehdi Abaakouk wrote:
>> Hi Mehdi,
>>
>> I think a number of the test related tasks should run fine without
>> strictly requiring the ceph task.  You may have to change binary
>> locations for things like rados, but those should be pretty minor.
>>
>> Best way to find out is to give it a try!
>
> Thanks for your quick answer :)
>
> I have already tried, but the code massively refers to files in
> /tmp/cephtest/, it seems to me that changing the path of the
> binaries isn't enough, some of them are built by the ceph task.
>
> Perhaps a quicker (a bit dirty) way is to create a new task 'cephdist',
> that prepares the required files in /tmp/cephtest.
> ie:
> - link dist binary to /tmp/cephtest/binary/usr/local/bin/...
> - link /etc/ceph/ceph.conf to /tmp/cephtest/ceph.conf
> - ship cephtest tool in /tmp/cephtest (like ceph task)
> - make dummy script for coverage (because distributed ceph doesn't seem
>    to have ceph-coverage)
>
> What do you think about it ?

That's probably the easiest way to get it working right now, if you
want to use the teuthology-specific tests. As Tommi mentioned, the
/tmp/cephtest stuff will go away in the long term.

There may be a few more things needed to run some of the tests (e.g. the 
binaries built when configured --with-debug like test_librbd,
test_rados_api_io, etc.).

Josh

  reply	other threads:[~2012-07-31 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 13:59 About teuthology Mehdi Abaakouk
2012-07-31 14:27 ` Mark Nelson
2012-07-31 16:16   ` Mehdi Abaakouk
2012-07-31 22:01     ` Josh Durgin [this message]
2012-07-31 17:55 ` Tommi Virtanen

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=501855D4.5070101@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@inktank.com \
    --cc=sileht@sileht.net \
    /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.