<p dir="ltr"><br>
On Feb 27, 2016 9:04 PM, "Amye Scavarda" <<a href="mailto:amye@redhat.com">amye@redhat.com</a>> wrote:<br>
><br>
> On Fri, Feb 26, 2016 at 9:24 PM, Raghavendra Talur <<a href="mailto:rtalur@redhat.com">rtalur@redhat.com</a>> wrote:<br>
> ><br>
> > On Feb 26, 2016 11:23 PM, "Raghavendra Talur" <<a href="mailto:rtalur@redhat.com">rtalur@redhat.com</a>> wrote:<br>
> >><br>
> >><br>
> >><br>
> >> On Fri, Feb 26, 2016 at 6:29 PM, Kaleb Keithley <<a href="mailto:kkeithle@redhat.com">kkeithle@redhat.com</a>><br>
> >> wrote:<br>
> >>><br>
> >>><br>
> >>><br>
> >>> ----- Original Message -----<br>
> >>> > From: "Raghavendra Talur" <<a href="mailto:rtalur@redhat.com">rtalur@redhat.com</a>><br>
> >>> ><br>
> >>> > Most likely it looks like disk is full. Someone please have a look at<br>
> >>> > it.<br>
> >>> ><br>
> >>><br>
> >>> Someone who? Misc is on holiday IIRC. Who else has access?<br>
> >><br>
> >><br>
> >> I think it is only Vijay and Kaushal other than misc who have access.<br>
> ><br>
> > I spoke to Kaushal over phone. He does not have access either. Adding misc<br>
> > hoping to catch his attention.<br>
> ><br>
> >><br>
> >>><br>
> >>><br>
> >>> Why do we think running our own gerrit and jenkins is a good thing? (When<br>
> >>> we could be using the CentOS gerrit and jenkins?)<br>
> >><br>
> >><br>
> >> That discussion did happen in Devconf and will be discussed in<br>
> >> gluster-devel is what I understand. We should wait for people to put across<br>
> >> pros and cons for that.<br>
> >> Personally,<br>
> >> 1. I would want infra which has a large enough team to have a 24/7<br>
> >> monitoring.(As ndevos suggested, if we form a bigger group we can do so with<br>
> >> our current setup.)<br>
> >> 2. Have control over gerrit settings so that we can decide what do we mean<br>
> >> by trivial patches, and what patches carry over review comments etc.<br>
> >><br>
> >><br>
> >>><br>
> >>><br>
> >>> (Yes, I am feeling snarky.)<br>
> >><br>
> >><br>
> >> Understandable, given how easily our infra breaks. We who are in<br>
> >> gluster-infra group have to come up with a solution too.<br>
> >><br>
> >>><br>
> >>> --<br>
> >>><br>
> >>> Kaleb<br>
> >>> _______________________________________________<br>
> >>> Gluster-infra mailing list<br>
> >>> <a href="mailto:Gluster-infra@gluster.org">Gluster-infra@gluster.org</a><br>
> >>> <a href="http://www.gluster.org/mailman/listinfo/gluster-infra">http://www.gluster.org/mailman/listinfo/gluster-infra</a><br>
> >><br>
> >><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Gluster-infra mailing list<br>
> > <a href="mailto:Gluster-infra@gluster.org">Gluster-infra@gluster.org</a><br>
> > <a href="http://www.gluster.org/mailman/listinfo/gluster-infra">http://www.gluster.org/mailman/listinfo/gluster-infra</a><br>
><br>
> Misc is indeed out of the office, but he will return on Monday.<br>
><br>
> In the meantime, can we put this on the list of documented<br>
> infrastructure pieces that more than one person needs access to - so<br>
> that we can start forming that effective infra team? Part of the<br>
> challenge is that the responsibilities haven't been clear, so getting<br>
> people to volunteer to assist is not helpful.<br>
><br>
> The conversation about CentOS's CI/CD is still ongoing, and in no way<br>
> do I want to dissuade Kaleb's snarky yet helpful suggestions. Keep 'em<br>
> coming.</p>
<p dir="ltr">+1 to everything. </p>
<p dir="ltr">Update : the site is working now. Not sure about who fixed it or what fixed it. </p>
<p dir="ltr">> - amye<br>
><br>
> --<br>
> Amye Scavarda | <a href="mailto:amye@redhat.com">amye@redhat.com</a> | Gluster Community Lead<br>
</p>