<div dir="ltr"><div>I merged this and posted the backport merging the two patches into one: <a href="https://review.gluster.org/#/c/17192">https://review.gluster.org/#/c/17192</a><br></div>Regressions started just now. <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 5, 2017 at 3:31 PM, Kaushal M <span dir="ltr"><<a href="mailto:kshlmster@gmail.com" target="_blank">kshlmster@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Thu, May 4, 2017 at 6:40 PM, Kaushal M <<a href="mailto:kshlmster@gmail.com">kshlmster@gmail.com</a>> wrote:<br>
> On Thu, May 4, 2017 at 4:38 PM, Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
>> On Thu, May 04, 2017 at 03:39:58PM +0530, Pranith Kumar Karampuri wrote:<br>
>>> On Wed, May 3, 2017 at 2:36 PM, Kaushal M <<a href="mailto:kshlmster@gmail.com">kshlmster@gmail.com</a>> wrote:<br>
>>><br>
>>> > On Tue, May 2, 2017 at 3:55 PM, Pranith Kumar Karampuri<br>
>>> > <<a href="mailto:pkarampu@redhat.com">pkarampu@redhat.com</a>> wrote:<br>
>>> > ><br>
>>> > ><br>
>>> > > On Sun, Apr 30, 2017 at 9:01 PM, Shyam <<a href="mailto:srangana@redhat.com">srangana@redhat.com</a>> wrote:<br>
>>> > >><br>
>>> > >> Hi,<br>
>>> > >><br>
>>> > >> Release 3.11 for gluster has been branched [1] and tagged [2].<br>
>>> > >><br>
>>> > >> We have ~4weeks to release of 3.11, and a week to backport features that<br>
>>> > >> slipped the branching date (May-5th).<br>
>>> > >><br>
>>> > >> A tracker BZ [3] has been opened for *blockers* of 3.11 release. Request<br>
>>> > >> that any bug that is determined as a blocker for the release be noted<br>
>>> > as a<br>
>>> > >> "blocks" against this bug.<br>
>>> > >><br>
>>> > >> NOTE: Just a heads up, all bugs that are to be backported in the next 4<br>
>>> > >> weeks need not be reflected against the blocker, *only* blocker bugs<br>
>>> > >> identified that should prevent the release, need to be tracked against<br>
>>> > this<br>
>>> > >> tracker bug.<br>
>>> > >><br>
>>> > >> We are not building beta1 packages, and will build out RC0 packages once<br>
>>> > >> we cross the backport dates. Hence, folks interested in testing this<br>
>>> > out can<br>
>>> > >> either build from the code or wait for (about) a week longer for the<br>
>>> > >> packages (and initial release notes).<br>
>>> > >><br>
>>> > >> Features tracked as slipped and expected to be backported by 5th May<br>
>>> > are,<br>
>>> > >><br>
>>> > >> 1) [RFE] libfuse rebase to latest? #153 (@amar, @csaba)<br>
>>> > >><br>
>>> > >> 2) SELinux support for Gluster Volumes #55 (@ndevos, @jiffin)<br>
>>> > >> - Needs a +2 on <a href="https://review.gluster.org/13762" rel="noreferrer" target="_blank">https://review.gluster.org/<wbr>13762</a><br>
>>> > >><br>
>>> > >> 3) Enhance handleops readdirplus operation to return handles along with<br>
>>> > >> dirents #174 (@skoduri)<br>
>>> > >><br>
>>> > >> 4) Halo - Initial version (@pranith)<br>
>>> > ><br>
>>> > ><br>
>>> > > I merged the patch on master. Will send out the port on Thursday. I have<br>
>>> > to<br>
>>> > > leave like right now to catch train and am on leave tomorrow, so will be<br>
>>> > > back on Thursday and get the port done. Will also try to get the other<br>
>>> > > patches fb guys mentioned post that preferably by 5th itself.<br>
>>> ><br>
>>> > Niels found that the HALO patch has pulled in a little bit of the IPv6<br>
>>> > patch. This shouldn't have happened.<br>
>>> > The IPv6 patch is currently stalled because it depends on an internal<br>
>>> > FB library. The IPv6 bits that made it in pull this dependency.<br>
>>> > This would have lead to a -2 on the HALO patch by me, but as I wasn't<br>
>>> > aware of it, the patch was merged.<br>
>>> ><br>
>>> > The IPV6 changes are in rpcsvh.{c,h} and <a href="http://configure.ac" rel="noreferrer" target="_blank">configure.ac</a>, and don't seem<br>
>>> > to affect anything HALO. So they should be easily removable and should<br>
>>> > be removed.<br>
>>> ><br>
>>><br>
>>> As per the <a href="http://configure.ac" rel="noreferrer" target="_blank">configure.ac</a> the macro is enabled only when we are building<br>
>>> gluster with "--with-fb-extras", which I don't think we do anywhere, so<br>
>>> didn't think they are important at the moment. Sorry for the confusion<br>
>>> caused because of this. Thanks to Kaushal for the patch. I will backport<br>
>>> that one as well when I do the 3.11 backport of HALO. So will wait for the<br>
>>> backport until Kaushal's patch is merged.<br>
>><br>
>> Note that there have been disucssions about preventing special vendor<br>
>> (Red Hat or Facebook) flags and naming. In that sense, --with-fb-extras<br>
>> is not acceptible. Someone was interested in providing a "site.h"<br>
>> configuration file that different vendors can use to fine-tune certain<br>
>> things that are too detailed for ./configure options.<br>
>><br>
>> We should remove the --with-fb-extras as well, specially because it is<br>
>> not useful for anyone that does not have access to the forked fbtirpc<br>
>> library.<br>
>><br>
>> Kaushal mentioned he'll update the patch that removed the IPv6 default<br>
>> define, to also remove the --with-fb-extras and related bits.<br>
><br>
> The patch removing IPV6 and fbextras is at<br>
> <a href="https://review.gluster.org/17174" rel="noreferrer" target="_blank">https://review.gluster.org/<wbr>17174</a> waiting for regression tests to run.<br>
<br>
</div></div>This has now passed its tests. I don't want to merge my own patch, so<br>
I'd like it if someone can merge it.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> I've merged the Selinux backports, <a href="https://review.gluster.org/17159" rel="noreferrer" target="_blank">https://review.gluster.org/<wbr>17159</a><br>
> and <a href="https://review.gluster.org/17157" rel="noreferrer" target="_blank">https://review.gluster.org/<wbr>17157</a> into release-3.11<br>
><br>
>><br>
>> Thanks,<br>
>> Niels<br>
>><br>
>>><br>
>>><br>
>>><br>
>>> ><br>
>>> > ><br>
>>> > >><br>
>>> > >><br>
>>> > >> Thanks,<br>
>>> > >> Kaushal, Shyam<br>
>>> > >><br>
>>> > >> [1] 3.11 Branch: <a href="https://github.com/gluster/glusterfs/tree/release-3.11" rel="noreferrer" target="_blank">https://github.com/gluster/<wbr>glusterfs/tree/release-3.11</a><br>
>>> > >><br>
>>> > >> [2] Tag for 3.11.0beta1 :<br>
>>> > >> <a href="https://github.com/gluster/glusterfs/tree/v3.11.0beta1" rel="noreferrer" target="_blank">https://github.com/gluster/<wbr>glusterfs/tree/v3.11.0beta1</a><br>
>>> > >><br>
>>> > >> [3] Tracker BZ for 3.11.0 blockers:<br>
>>> > >> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.0" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=glusterfs-3.<wbr>11.0</a><br>
>>> > >><br>
>>> > >> ______________________________<wbr>_________________<br>
>>> > >> maintainers mailing list<br>
>>> > >> <a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
>>> > >> <a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > > --<br>
>>> > > Pranith<br>
>>> > ><br>
>>> > > ______________________________<wbr>_________________<br>
>>> > > Gluster-devel mailing list<br>
>>> > > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
>>> > > <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
>>> ><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Pranith<br>
>><br>
>>> ______________________________<wbr>_________________<br>
>>> maintainers mailing list<br>
>>> <a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
>>> <a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
>><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div>