Open Stack

Hi,

Before switching Fuel from ostf to rally, I would like to see feature
parity comparison. It's very necessary to understand how much work we need
to spend to rewrite all our tests in rally way.



--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Mon, Jun 27, 2016 at 4:32 PM, Alexander Kostrikov <
akostrikov at mirantis.com> wrote:

> Hello, everybody!
> Hello, Alex!
> >I thought Rally was more for benchmarking.  Wouldn't Tempest make more
> sense?
> Rally is a good tool with nice api/usage/extensibility.
> I really liked "up and running tests in 5 minutes" in Rally with clear
> picture of what I am doing.
> So, I 100% for a Rally as a QA.
>
> Another note:
> We will need to implement some HA tests, probably not in Rally.
>
> On Mon, Jun 27, 2016 at 4:57 PM, Andrey Kurilin <akurilin at mirantis.com>
> wrote:
>
>>
>>
>> On Mon, Jun 27, 2016 at 4:46 PM, Igor Kalnitsky <ikalnitsky at mirantis.com>
>> wrote:
>>
>>>
>>> > On Jun 27, 2016, at 16:23, Alex Schultz <aschultz at mirantis.com> wrote:
>>> >
>>> > I thought Rally was more for benchmarking.  Wouldn't Tempest make more
>>> sense?
>>>
>>> According to Rally wiki page [1], it seems they have a verification
>>> layer (Tempest so far). Hm, I wonder does it mean we will need to rewrite
>>> our scenarios for Tempest?
>>>
>>>
>> Rally consists of two main components: Rally Task and Rally Verification.
>> They are totally separated.
>> Task component is fully pluggable and you can run there whatever you want
>> in whatever you want way.
>> Verification component is hardcoded now. It was designed for
>> managing(install, configure) and launching(execute and store results)
>> Tempest. But we have a spec to make this component pluggable too.
>>
>>
>>> - igor
>>>
>>>
>>> [1] https://wiki.openstack.org/wiki/Rally
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>>
>> --
>> Best regards,
>> Andrey Kurilin.
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
>
> Kind Regards,
>
> Alexandr Kostrikov,
>
> Mirantis, Inc.
>
> 35b/3, Vorontsovskaya St., 109147, Moscow, Russia
>
>
> Tel.: +7 (495) 640-49-04
> Tel.: +7 (925) 716-64-52 <%2B7%20%28906%29%20740-64-79>
>
> Skype: akostrikov_mirantis
>
> E-mail: akostrikov at mirantis.com <elogutova at mirantis.com>
>
> *www.mirantis.com <http://www.mirantis.ru/>*
> *www.mirantis.ru <http://www.mirantis.ru/>*
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160627/22918f3c/attachment.html>