Re: Running a teuthology workload depending on the distribution

[Loic Dachary <loic@dachary.org>]

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

Hi Zack,

It's great that it's scheduled for this sprint, if I'm reading http://tracker.ceph.com/versions/378 correctly ;-) In the meantime it is not a blocker, I can work around it.

Thanks !

On 03/09/2014 23:44, Zack Cerza wrote:
> Hi Loic,
> 
> Sage recently filed these, which seem like they might help with what
> you're asking.
> 
> http://tracker.ceph.com/issues/9256
> http://tracker.ceph.com/issues/9255
> 
> I'll be getting to work on them relatively soon, just not quite yet.
> In the meantime, would it be feasible to, say, make the relevant task
> in the workload check for the presence of the plugin, and immediately
> fail if it's not found? That way we can waive those failures, and have
> them not use many more resources than necessary.
> 
> Zack
> 
> On Sun, Aug 31, 2014 at 4:33 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Zack,
>>
>> The isa erasure code plugin is only built on some architectures. The workload described at
>>
>> https://github.com/ceph/ceph-qa-suite/blob/master/erasure-code/ec-rados-plugin%3Disa-k%3D2-m%3D1.yaml
>>
>> can therefore only be run on those architectures. How would you recommend that it is integrated in the upgrade suites ? Adding it to
>>
>> https://github.com/ceph/ceph-qa-suite/tree/master/suites/upgrade/firefly-x/stress-split/9-workload
>>
>> for instance, at the same level as
>>
>> https://github.com/ceph/ceph-qa-suite/blob/master/suites/upgrade/firefly-x/stress-split/9-workload/ec-rados-plugin%3Djerasure-k%3D3-m%3D1.yaml
>>
>> will not work because it will fail when running on precise (for instance).
>>
>> 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 --]