All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: John Spray <john.spray@redhat.com>,
	Samuel Just <sjust@redhat.com>, Zack Cerza <zcerza@redhat.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Use of YAML for defining complex tests (or Python...?)
Date: Tue, 05 May 2015 14:15:57 +0200	[thread overview]
Message-ID: <5548B47D.5000706@dachary.org> (raw)
In-Reply-To: <5548AAE9.2000302@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]



On 05/05/2015 13:35, John Spray wrote:> Hi,
> 
> I noted with interest the rather complex .yaml file in this PR:
> https://github.com/ceph/ceph-qa-suite/pull/428/files
> 
> ...with the accompanying addition of loop constructs in this PR:
> https://github.com/ceph/teuthology/pull/481
> 
> Teuthology YAML files appear to be at risk of becoming a fully fledged scripting language.  Why not write python scripts instead, for the more complex tests (e.g. anything that would need the full_sequential or loop constructs)?

I guess we should be careful to not abuse YAML where scripts would be more appropriate. I tend to agree with you: singleton-nomsgr/all/11429.yaml should be a script.

My 2cts

> 
> On the cephfs side, we hit the point where test procedures were complex enough to need their own mini-framework inside tasks/cephfs -- a similar structure could be useful for people working on other subsystems as well.
> 
> Cheers,
> John
> -- 
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2015-05-05 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 11:35 Use of YAML for defining complex tests (or Python...?) John Spray
2015-05-05 12:15 ` Loic Dachary [this message]

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=5548B47D.5000706@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=john.spray@redhat.com \
    --cc=sjust@redhat.com \
    --cc=zcerza@redhat.com \
    /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.