All of lore.kernel.org
 help / color / mirror / Atom feed
* Recommended teuthology upgrade test
@ 2014-06-27 15:16 Loic Dachary
  2014-06-27 16:17 ` Yuri Weinstein
  0 siblings, 1 reply; 3+ messages in thread
From: Loic Dachary @ 2014-06-27 15:16 UTC (permalink / raw)
  To: Samuel Just; +Cc: Ceph Development

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

Hi Sam,

TL;DR: what oneliner do you recommend to run upgrade tests for https://github.com/ceph/ceph/pull/1890 ? 

Running the rados suite can be done with :

   ./schedule_suite.sh rados wip-8071 testing loic@dachary.org basic master plana 

or something else since ./schedule_suite.sh was recently obsoleted ( http://tracker.ceph.com/issues/8678 ). Running something similar for upgrade will presumably run all of https://github.com/ceph/ceph-qa-suite/tree/master/suites/upgrade

Is there a way to run minimal tests by limiting the upgrade suite so that it only focuses on a firefly cluster that upgrades to https://github.com/ceph/ceph/pull/1890 so that it checks the behavior when running a mixed cluster (firefly + master with the change) ?

It looks like http://pulpito.ceph.com/?suite=upgrade was never run ( at least that's what appears to cause http://tracker.ceph.com/issues/8681 ) Is http://pulpito.ceph.com/?suite=upgrade-rados a good fit ? If so is there a way to figure out how it was created ?

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Recommended teuthology upgrade test
  2014-06-27 15:16 Recommended teuthology upgrade test Loic Dachary
@ 2014-06-27 16:17 ` Yuri Weinstein
  2014-06-27 17:23   ` Loic Dachary
  0 siblings, 1 reply; 3+ messages in thread
From: Yuri Weinstein @ 2014-06-27 16:17 UTC (permalink / raw)
  To: Loic Dachary; +Cc: Samuel Just, Ceph Development

Loic

I don't intent to answer all questions, but some info, see inline

On Fri, Jun 27, 2014 at 8:16 AM, Loic Dachary <loic@dachary.org> wrote:
> Hi Sam,
>
> TL;DR: what oneliner do you recommend to run upgrade tests for https://github.com/ceph/ceph/pull/1890 ?
>
> Running the rados suite can be done with :
>
>    ./schedule_suite.sh rados wip-8071 testing loic@dachary.org basic master plana
>

It was replaced with teuthology-suite, see --help for more info

> or something else since ./schedule_suite.sh was recently obsoleted ( http://tracker.ceph.com/issues/8678 ). Running something similar for upgrade will presumably run all of https://github.com/ceph/ceph-qa-suite/tree/master/suites/upgrade
>
> Is there a way to run minimal tests by limiting the upgrade suite so that it only focuses on a firefly cluster that upgrades to https://github.com/ceph/ceph/pull/1890 so that it checks the behavior when running a mixed cluster (firefly + master with the change) ?

You can run specifying argument with smaller suite, like this:
dumpling-x/parallel

>
> It looks like http://pulpito.ceph.com/?suite=upgrade was never run ( at least that's what appears to cause http://tracker.ceph.com/issues/8681 ) Is http://pulpito.ceph.com/?suite=upgrade-rados a good fit ? If so is there a way to figure out how it was created ?
>
> Cheers
>
> --
> Loïc Dachary, Artisan Logiciel Libre
>
--
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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Recommended teuthology upgrade test
  2014-06-27 16:17 ` Yuri Weinstein
@ 2014-06-27 17:23   ` Loic Dachary
  0 siblings, 0 replies; 3+ messages in thread
From: Loic Dachary @ 2014-06-27 17:23 UTC (permalink / raw)
  To: Yuri Weinstein; +Cc: Ceph Development

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



On 27/06/2014 18:17, Yuri Weinstein wrote:
> Loic
> 
> I don't intent to answer all questions, but some info, see inline
> 
> On Fri, Jun 27, 2014 at 8:16 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Sam,
>>
>> TL;DR: what oneliner do you recommend to run upgrade tests for https://github.com/ceph/ceph/pull/1890 ?
>>
>> Running the rados suite can be done with :
>>
>>    ./schedule_suite.sh rados wip-8071 testing loic@dachary.org basic master plana
>>
> 
> It was replaced with teuthology-suite, see --help for more info
> 
>> or something else since ./schedule_suite.sh was recently obsoleted ( http://tracker.ceph.com/issues/8678 ). Running something similar for upgrade will presumably run all of https://github.com/ceph/ceph-qa-suite/tree/master/suites/upgrade
>>
>> Is there a way to run minimal tests by limiting the upgrade suite so that it only focuses on a firefly cluster that upgrades to https://github.com/ceph/ceph/pull/1890 so that it checks the behavior when running a mixed cluster (firefly + master with the change) ?
> 
> You can run specifying argument with smaller suite, like this:
> dumpling-x/parallel

Hi Yuri,

Thanks for the hint :-) It is documented https://github.com/ceph/teuthology/commit/7d2388b42c75f4526bc34c6a4b1b16637d967527 but it looks like it should be more generic because any level of subdirectories can be used.

Cheers

> 
>>
>> It looks like http://pulpito.ceph.com/?suite=upgrade was never run ( at least that's what appears to cause http://tracker.ceph.com/issues/8681 ) Is http://pulpito.ceph.com/?suite=upgrade-rados a good fit ? If so is there a way to figure out how it was created ?
>>
>> Cheers
>>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>>

-- 
Loïc Dachary, Artisan Logiciel Libre


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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-06-27 17:24 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-27 15:16 Recommended teuthology upgrade test Loic Dachary
2014-06-27 16:17 ` Yuri Weinstein
2014-06-27 17:23   ` Loic Dachary

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.