[Gluster-infra] review.gluster.org not working

[Amye Scavarda]

On Fri, Feb 26, 2016 at 9:24 PM, Raghavendra Talur <rtalur at redhat.com> wrote:
>
> On Feb 26, 2016 11:23 PM, "Raghavendra Talur" <rtalur at redhat.com> wrote:
>>
>>
>>
>> On Fri, Feb 26, 2016 at 6:29 PM, Kaleb Keithley <kkeithle at redhat.com>
>> wrote:
>>>
>>>
>>>
>>> ----- Original Message -----
>>> > From: "Raghavendra Talur" <rtalur at redhat.com>
>>> >
>>> > Most likely it looks like disk is full. Someone please have a look at
>>> > it.
>>> >
>>>
>>> Someone who? Misc is on holiday IIRC. Who else has access?
>>
>>
>> I think it is only Vijay and Kaushal other than misc who have access.
>
> I spoke to Kaushal over phone. He does not have access either. Adding misc
> hoping to catch his attention.
>
>>
>>>
>>>
>>> Why do we think running our own gerrit and jenkins is a good thing? (When
>>> we could be using the CentOS gerrit and jenkins?)
>>
>>
>> That discussion did happen in Devconf and will be discussed in
>> gluster-devel is what I understand. We should wait for people to put across
>> pros and cons for that.
>> Personally,
>> 1. I would want infra which has a large enough team to have a 24/7
>> monitoring.(As ndevos suggested, if we form a bigger group we can do so with
>> our current setup.)
>> 2. Have control over gerrit settings so that we can decide what do we mean
>> by trivial patches, and what patches carry over review comments etc.
>>
>>
>>>
>>>
>>> (Yes, I am feeling snarky.)
>>
>>
>> Understandable, given how easily our infra breaks. We who are in
>> gluster-infra group have to come up with a solution too.
>>
>>>
>>> --
>>>
>>> Kaleb
>>> _______________________________________________
>>> Gluster-infra mailing list
>>> Gluster-infra at gluster.org
>>> http://www.gluster.org/mailman/listinfo/gluster-infra
>>
>>
>
>
> _______________________________________________
> Gluster-infra mailing list
> Gluster-infra at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-infra

Misc is indeed out of the office, but he will return on Monday.

In the meantime, can we put this on the list of documented
infrastructure pieces that more than one person needs access to - so
that we can start forming that effective infra team? Part of the
challenge is that the responsibilities haven't been clear, so getting
people to volunteer to assist is not helpful.

The conversation about CentOS's CI/CD is still ongoing, and in no way
do I want to dissuade Kaleb's snarky yet helpful suggestions. Keep 'em
coming.
- amye

-- 
Amye Scavarda | amye at redhat.com | Gluster Community Lead