Rally-CI is single daemon which listens gerrit events, run tests and
publish results.
It sounds much like zuul but it is not zuul. The primary goal of rally-ci
is simpleness. It does not any git merges, it have not any complex
pipeline logic. Just test every single CR and put +1 or -1.
First of
- We should start making agenda for each meeting and publish it to
Rally wiki
+1
- We should do 2 meeting per week:
We can do both things in one meeting.
__
OpenStack Development Mailing List (not for usage
It is not known issue, but it will be fixed very soon.
Meanwhile I can suggest that rally was unable to connect to VM for some
reason.
I ran into below rally exception while trying to run Rally scenario.
u'Traceback (most recent call last):\n File
will just work? Such number of failures leads
to
significant amount of extra work for test nodes.
--
Regards,
Sergey Skripnick
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
intervals updating only one parameter.
Btw if we will have only one argument, we can make some method that will
automatically adjust it before running benchmark.
Thoughts?
Best regards,
Boris Pavlovic
--
Regards,
Sergey Skripnick
+1I would like to propose Kun Huang to Rally Core team.As you saw already, he is doing a lot of good reviews, and catch a lot of nits and bugs, so he will be a good core reviewer.
Here is detailed statistics for the latest 30 days:http://stackalytics.com/report/contribution/rally/30
://wiki.openstack.org/wiki/Rally
--
Regards,
Sergey Skripnick
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
as possible.
I believe it is impossible to use threads without changes in the code.
--
Regards,
Sergey Skripnick
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
feel free to propose other solutions.
--
Regards,
Sergey Skripnick
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
+1 for Hugh, but IMO no need to rush with Alexei's removalHi stackers,I would like to:1) Nominate Hugh Saunders to Rally core, he is doing a lot of good reviews (and always testing patches=) ):http://stackalytics.com/report/reviews/rally/30
2) Remove Alexei from core team, because unfortunately
use
subprocess module. Why do we need oslo.processutils.ssh_execute? We can
use paramiko
instead.
--
Regards,
Sergey Skripnick
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
On Fri, Jan 10, 2014 at 12:54 PM, Sergey Skripnick
sskripn...@mirantis.com wrote:
I appreciate that we want to fix the ssh client. I'm not certain that
writing our own is the best answer.
I was supposed to fix oslo.processutils.ssh with this class, but it may
be fixed
work with eventlet.
[0] https://github.com/paramiko/paramiko/pull/245
[1] https://github.com/mwilliamson/spur.py/blob/master/spur/io.py#L22
--
Regards,
Sergey Skripnick
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
by stackforge/rally and
may be used by other projects instead of buggy oslo.processutils.ssh.
--
Regards,
Sergey Skripnick
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi all,
I'm surprised there is no common ssh library in oslo so I filed this
blueprint[0]. I would be happy to address any comments/suggestions.
[0] https://blueprints.launchpad.net/oslo/+spec/common-ssh-client
--
Regards,
Sergey Skripnick
This definitely should be somewhere in wiki or blog and in the bookmarks.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
16 matches
Mail list logo
