Re: Use of YAML for defining complex tests (or Python...?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Loïc Dachary, Artisan Logiciel Libre

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux