[Cinder.glusterfs.ci] [Third-party-announce] Mellanox CI is creating noise on nova patches

[Nurit Vilosny]

Hi Anita, Kyle,
My name is Nurit and I am responsible for the Mellanox’s activity in the community.
Let me assure you that Lenny is not alone here, and that there are several people here to support him in his new role.
As always, all new  code goes through code reviewing, which missed the default of voting = true.
As soon as we discover the error we took off the job and we are working now silently until we will be sure the job is working OK.
Of course we try not to make such mistakes, but they can happen. Our CI team and activity had grown recently (cinder CI, Nova CI), and with the work come mistakes.
I truly think recent history shows our CI is stable, and we constantly work to improve it.

Best regards,
Nurit

From: Kyle Mestery [mailto:mestery at mestery.com]
Sent: Monday, March 02, 2015 5:56 PM
To: Announcements for third party CI operators.
Cc: Lenny Verkhovsky; Moshe Levi
Subject: Re: [Third-party-announce] Mellanox CI is creating noise on nova patches

On Mon, Mar 2, 2015 at 9:02 AM, Anita Kuno <anteaya at anteaya.info<mailto:anteaya at anteaya.info>> wrote:
On 03/02/2015 07:39 AM, Lenny Verkhovsky wrote:
> Hi Anita, Ramy, All,
>
>
>
> My name is Lenny and I am replacing Omri on all OpenStack CI activities at Mellanox.
>
> I am very excited to start working on such interesting, challenging and wide project as OpenStack.
>
>
>
> My first task was bringing Nova CI up and I guess it has already violated community policies.
Hello Lenny, welcome to OpenStack. I cannot express my disappointment
with the fact that although your company has more than one person within
its midst with enough experience of OpenStack that you could have
avoided this situation, they didn't appear to bestow their knowledge
upon you.

The work we do to support folks in this space depends on at the very
least people sharing knowledge within companies rather than just tossing
new people at OpenStack to make all the same mistakes that new people make.

Given this account was operating with such proficiency that it had been
given permission to comment and vote on Neutron, I wonder if those
permissions should be re-evaluated since you are brand new to the task
and could cause quite a bit of damage to Neutron patches if you don't
know what you are doing and are making the mistakes of a new person like
everyone else makes.

Edgar or Mestery, could you share your thoughts?
I tend to agree here. Given the current situation and the fact someone new is operating the Mellanox CI, it's likely we should make it non-voting until it's proven itself again. But I'd like Lenny to indicate whether or not he has the previous person at Mellanox helping him here, as that would help sway things a bit.
Thanks,
Kyle

Thanks,
Anita.
>
> I stopped it until I resolve missing permissions.
>
> Questions regarding solving Nova CI and Cinder CI issues:
>
>                 1. Since we are running Neutron CI and Nova CI by the same team and Gerrit account will it be enough to update
>
>                 https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI for non-voting Nova CI to run again?
>
>
>
>                 2. How/Where can I delete 'extra e-mail' ?
>
>                 [cid:image001.png at 01D05420.0ED1EDF0]
>
>
>
>
>
> p.s. https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_Cinder_CI  Is added and updated.
>
>
>
> Thanks.
>
> Lenny.
>
>
>
>
>
>
>
> -----Original Message-----
>
> From: Anita Kuno [mailto:anteaya at anteaya.info<mailto:anteaya at anteaya.info>]
>
> Sent: Saturday, February 28, 2015 12:55 AM
>
> To: Announcements for Third Party CI Operators.
>
> Subject: [Third-party-announce] Mellanox CI is creating noise on nova patches
>
>
>
> https://review.openstack.org/#/c/160027/
>
>
>
> Mellanox CI is to be testing Neutron:
>
> https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI
>
>
>
> At least one nova core is not aware that Mellanox CI has permission to post comments on nova patches.
>
>
>
> Please check your system configuration to ensure you are only testing the repositories you have permission to test.
>
>
>
> If no action is taken by Mellanox CI by Monday to correct this situation, I will act.
>
>
>
> Thank you,
>
> Anita.
>
>
>
> _______________________________________________
>
> Third-party-announce mailing list
>
> Third-party-announce at lists.openstack.org<mailto:Third-party-announce at lists.openstack.org><mailto:Third-party-announce at lists.openstack.org<mailto:Third-party-announce at lists.openstack.org>>
>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>


_______________________________________________
Third-party-announce mailing list
Third-party-announce at lists.openstack.org<mailto:Third-party-announce at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/cinder.glusterfs.ci/attachments/20150302/889f37b9/attachment-0001.html>
-------------- next part --------------
_______________________________________________
Third-party-announce mailing list
Third-party-announce at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce