Boris, can You take a look on HA scenarios [0] to give a quick feedback on
how it should be implemented with Rally in right way? Plugins/templates/how
yaml should look like.
To make correct comparison of ostf and rally-based version.
Thanks!
[0] http://paste.openstack.org/show/523983/
On Tue, Jun
Igor,
I wonder what are the benefits of using Rally then? We can run whatever we
> want by means of MCollective or Ansible. Is there something that could help
> us? I don't know, maybe some dashboard integration with per test results or
> running by tests by tag?
Benefits are in the Rally frame
+1 to initial suggestion, but I guess we need to have a full feature
equality (e.g. HA tests for mysql and rabbitmq replication) before
switching to Rally.
On Mon, Jun 27, 2016 at 6:17 PM, Sergii Golovatiuk wrote:
> Hi,
>
> Before switching Fuel from ostf to rally, I would like to see feature
>
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,
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.
A
> On Jun 27, 2016, at 16:57, Andrey Kurilin wrote:
>
> 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.
Andrey, thanks for explanation!
On Mon, Jun 27, 2016 at 4:46 PM, Igor Kalnitsky
wrote:
>
> > On Jun 27, 2016, at 16:23, Alex Schultz 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
As far as I understand, Rally is pluggable and one can implement any
scenario we need in pure Python (totally out of Tempest). See for example
[1].
[1] http://rally.readthedocs.io/en/latest/plugins/scenario_plugin.html
Vladimir Kozhukalov
On Mon, Jun 27, 2016 at 4:46 PM, Igor Kalnitsky
wrote:
> On Jun 27, 2016, at 16:23, Alex Schultz 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 f
Hi!
On Mon, Jun 27, 2016 at 4:23 PM, Alex Schultz wrote:
>
>
> On Mon, Jun 27, 2016 at 7:10 AM, Vladimir Kozhukalov <
> vkozhuka...@mirantis.com> wrote:
>
>> Dear colleagues,
>>
>> I'd like to suggest to replace Fuel-ostf with Rally. Rally is quite
>> popular project and as far as I know it has
On Mon, Jun 27, 2016 at 7:10 AM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> Dear colleagues,
>
> I'd like to suggest to replace Fuel-ostf with Rally. Rally is quite
> popular project and as far as I know it has all necessary features
> (including dashboard). We only need to implement
11 matches
Mail list logo
