Re: [Gluster-devel] mainline compilation fails

[Raghavendra Gowdappa]

I noticed that these were dependent patches. But, kind of carelessly assumed 
that this is parent patch, doesn't have any dependencies and merged. Sorry for 
the trouble. Will be more diligent henceforth :)

- Original Message -
> From: "Poornima Gurusiddaiah" 
> To: "Prasanna Kalever" , "Gluster Devel" 
> , "Kaushal M"
> , "Nigel Babu" 
> Sent: Monday, August 29, 2016 10:55:08 AM
> Subject: Re: [Gluster-devel] mainline compilation fails
> 
> Hi,
> 
> Regarding the enforcement of the dependencies while merging, i see that
> the dependent patches on any patch is mentioned in the "Related Changes"
> column [1]. It still doesn't enforce, in the cherry-pick way of
> submitting changes, by default it ignores the lineage [2]. But there are
> ways to enforce this. Will let the gluster infra maintainers to comment
> on the same.
> 
> [1]
> https://gerrit-review.googlesource.com/Documentation/user-review-ui.html#related-changes
> [2]
> https://gerrit-review.googlesource.com/Documentation/project-configuration.html#project_options
> 
> Regards,
> Poornima
> - Original Message -
> 
> > From: "Prasanna Kalever" 
> > To: "Atin Mukherjee" 
> > Cc: "Gluster Devel" 
> > Sent: Saturday, August 27, 2016 11:11:33 AM
> > Subject: Re: [Gluster-devel] mainline compilation fails
> 
> > Oops!
> > Didn't noticed these changes were part of parent/child patches, Just
> > noticed "BUILD BROKEN" and went into action :)
> 
> > I'm not sure about it!
> 
> > If it takes time to decide on whether the other set of patches need to
> > be taken or not, at-least my patch will fix the broken build (That
> > much I can assure)
> 
> > Lets see if the regressions break after these patch goes in (mostly
> > not, that I see from the code)
> 
> > Thanks,
> > --
> > Prasanna
> 
> > On Sat, Aug 27, 2016 at 8:34 PM, Atin Mukherjee
> >  wrote:
> > >
> > >
> > > On Saturday 27 August 2016, Prasanna Kalever  wrote:
> > >>
> > >> Here is the patch that should fix it
> > >> http://review.gluster.org/#/c/15331/
> > >
> > >
> > > Thanks! Well thats an easy way, but the question here is dont we need the
> > > parent patch to be merged to ensure there is no other functionality
> > > broken.
> > > Currently I see that the parent patch has a -1, in that case is it
> > > required
> > > to revert 15225?
> > >>
> > >>
> > >> Happy weekend!
> > >>
> > >> --
> > >> Prasanna
> > >>
> > >>
> > >> On Sat, Aug 27, 2016 at 7:49 PM, Atin Mukherjee 
> > >> wrote:
> > >> > [1] has broken mainline compilation and I feel this could be because
> > >> > its
> > >> > parent patch is not been merged otherwise smoke should have caught it.
> > >> > Please resolve it at earliest.
> > >> >
> > >> > [1] http://review.gluster.org/#/c/15225/
> > >> >
> > >> >
> > >> > --Atin
> > >> >
> > >> > ___
> > >> > Gluster-devel mailing list
> > >> > Gluster-devel@gluster.org
> > >> > http://www.gluster.org/mailman/listinfo/gluster-devel
> > >> ___
> > >> Gluster-devel mailing list
> > >> Gluster-devel@gluster.org
> > >> http://www.gluster.org/mailman/listinfo/gluster-devel
> > >
> > >
> > >
> > > --
> > > --Atin
> > ___
> > Gluster-devel mailing list
> > Gluster-devel@gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] 3.9. feature freeze status check

[Kotresh Hiremath Ravishankar]

Hi Pranith,

Please add the following feature of bitrot to 3.9 road map page. It is merged.

feature/bitrot: Ondemand scrub option for bitrot 
(http://review.gluster.org/#/c/15111/)

Thanks and Regards,
Kotresh H R

- Original Message -
> From: "Poornima Gurusiddaiah" 
> To: "Pranith Kumar Karampuri" 
> Cc: "Anoop Chirayath Manjiyil Sajan" , "Kaushal Madappa" 
> , "Gluster Devel"
> , "Jose Rivera" 
> Sent: Monday, August 29, 2016 10:18:46 AM
> Subject: Re: [Gluster-devel] 3.9. feature freeze status check
> 
> Hi,
> 
> Updated inline.
> 
> 
> 
> 
> From: "Pranith Kumar Karampuri" 
> To: "Rajesh Joseph" , "Manikandan Selvaganesh"
> , "Csaba Henk" , "Niels de Vos"
> , "Jiffin Thottan" , "Aravinda
> Vishwanathapura Krishna Murthy" , "Anoop Chirayath
> Manjiyil Sajan" , "Ravishankar Narayanankutty"
> , "Kaushal Madappa" ,
> "Raghavendra Talur" , "Poornima Gurusiddaiah"
> , "Soumya Koduri" , "Kaleb
> Keithley" , "Jose Rivera" ,
> "Prashanth Pai" , "Samikshan Bairagya"
> , "Vijay Bellur" , "Prasanna
> Kalever" 
> Cc: "Gluster Devel" 
> Sent: Friday, August 26, 2016 12:21:07 PM
> Subject: Re: 3.9. feature freeze status check
> 
> Prasanna, Prashant,
> Could you add a short description of the features you are working on for 3.9
> as well to the list?
> 
> On Fri, Aug 26, 2016 at 9:39 PM, Pranith Kumar Karampuri <
> pkara...@redhat.com > wrote:
> 
> 
> 
> 
> 
> On Fri, Aug 26, 2016 at 9:38 PM, Pranith Kumar Karampuri <
> pkara...@redhat.com > wrote:
> 
> 
> 
> hi,
> Now that we are almost near the feature freeze date (31st of Aug), want to
> get a sense if any of the status of the features.
> 
> I meant "want to get a sense of the status of the features"
> 
> 
> 
> 
> Please respond with:
> 1) Feature already merged
> 2) Undergoing review will make it by 31st Aug
> 3) Undergoing review, but may not make it by 31st Aug
> 4) Feature won't make it for 3.9.
> 
> I added the features that were not planned(i.e. not in the 3.9 roadmap page)
> but made it to the release and not planned but may make it to release at the
> end of this mail.
> If you added a feature on master that will be released as part of 3.9.0 but
> forgot to add it to roadmap page, please let me know I will add it.
> 
> Here are the features planned as per the roadmap:
> 1) Throttling
> Feature owner: Ravishankar
> 
> 2) Trash improvements
> Feature owners: Anoop, Jiffin
> 
> 3) Kerberos for Gluster protocols:
> Feature owners: Niels, Csaba
> 
> 4) SELinux on gluster volumes:
> Feature owners: Niels, Manikandan
> 
> 5) Native sub-directory mounts:
> Feature owners: Kaushal, Pranith
> 
> 6) RichACL support for GlusterFS:
> Feature owners: Rajesh Joseph
> 
> 7) Sharemodes/Share reservations:
> Feature owners: Raghavendra Talur, Poornima G, Soumya Koduri, Rajesh Joseph,
> Anoop C S
> 
> 8) Integrate with external resource management software
> Feature owners: Kaleb Keithley, Jose Rivera
> 
> 9) Python Wrappers for Gluster CLI Commands
> Feature owners: Aravinda VK
> 
> 10) Package and ship libgfapi-python
> Feature owners: Prashant Pai
> 
> 11) Management REST APIs
> Feature owners: Aravinda VK
> 
> 12) Events APIs
> Feature owners: Aravinda VK
> 
> 13) CLI to get state representation of a cluster from the local glusterd pov
> Feature owners: Samikshan Bairagya
> 
> 14) Posix-locks Reclaim support
> Feature owners: Soumya Koduri
> 
> 15) Deprecate striped volumes
> Feature owners: Vijay Bellur, Niels de Vos
> 
> 16) Improvements in Gluster NFS-Ganesha integration
> Feature owners: Jiffin Tony Thottan, Soumya Koduri
> 
> The following need to be added to the roadmap:
> 
> Features that made it to master already but were not palnned:
> 1) Multi threaded self-heal in EC
> Feature owner: Pranith (Did this because serkan asked for it. He has 9PB
> volume, self-healing takes a long time :-/)
> 
> 2) Lock revocation (Facebook patch)
> Feature owner: Richard Wareing
> 
> Features that look like will make it to 3.9.0:
> 1) Hardware extension support for EC
> Feature owner: Xavi
> 
> 2) Reset brick support for replica volumes:
> Feature owner: Anuradha
> 
> 3) Md-cache perf improvements in smb:
> Feature owner: Poornima
> Feature undergoing review. It will be in tech-preview for this release. Main
> feature will be merged by 31st August 2016.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --
> Pranith
> 
> 
> 
> --
> Pranith
> 
> 
> 
> --
> Pranith
> 
> Regards,
> Poornima
> 
> 
> 
> 
> 
> 
> ___
> 

Re: [Gluster-devel] mainline compilation fails

[Poornima Gurusiddaiah]

Hi, 

Regarding the enforcement of the dependencies while merging, i see that 
the dependent patches on any patch is mentioned in the "Related Changes" 
column [1]. It still doesn't enforce, in the cherry-pick way of
submitting changes, by default it ignores the lineage [2]. But there are
ways to enforce this. Will let the gluster infra maintainers to comment
on the same.

[1] 
https://gerrit-review.googlesource.com/Documentation/user-review-ui.html#related-changes
[2] 
https://gerrit-review.googlesource.com/Documentation/project-configuration.html#project_options

Regards,
Poornima
- Original Message - 

> From: "Prasanna Kalever" 
> To: "Atin Mukherjee" 
> Cc: "Gluster Devel" 
> Sent: Saturday, August 27, 2016 11:11:33 AM
> Subject: Re: [Gluster-devel] mainline compilation fails

> Oops!
> Didn't noticed these changes were part of parent/child patches, Just
> noticed "BUILD BROKEN" and went into action :)

> I'm not sure about it!

> If it takes time to decide on whether the other set of patches need to
> be taken or not, at-least my patch will fix the broken build (That
> much I can assure)

> Lets see if the regressions break after these patch goes in (mostly
> not, that I see from the code)

> Thanks,
> --
> Prasanna

> On Sat, Aug 27, 2016 at 8:34 PM, Atin Mukherjee
>  wrote:
> >
> >
> > On Saturday 27 August 2016, Prasanna Kalever  wrote:
> >>
> >> Here is the patch that should fix it
> >> http://review.gluster.org/#/c/15331/
> >
> >
> > Thanks! Well thats an easy way, but the question here is dont we need the
> > parent patch to be merged to ensure there is no other functionality broken.
> > Currently I see that the parent patch has a -1, in that case is it required
> > to revert 15225?
> >>
> >>
> >> Happy weekend!
> >>
> >> --
> >> Prasanna
> >>
> >>
> >> On Sat, Aug 27, 2016 at 7:49 PM, Atin Mukherjee 
> >> wrote:
> >> > [1] has broken mainline compilation and I feel this could be because its
> >> > parent patch is not been merged otherwise smoke should have caught it.
> >> > Please resolve it at earliest.
> >> >
> >> > [1] http://review.gluster.org/#/c/15225/
> >> >
> >> >
> >> > --Atin
> >> >
> >> > ___
> >> > Gluster-devel mailing list
> >> > Gluster-devel@gluster.org
> >> > http://www.gluster.org/mailman/listinfo/gluster-devel
> >> ___
> >> Gluster-devel mailing list
> >> Gluster-devel@gluster.org
> >> http://www.gluster.org/mailman/listinfo/gluster-devel
> >
> >
> >
> > --
> > --Atin
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] 3.9. feature freeze status check

[Poornima Gurusiddaiah]

Hi, 

Updated inline. 

- Original Message -

> From: "Pranith Kumar Karampuri" 
> To: "Rajesh Joseph" , "Manikandan Selvaganesh"
> , "Csaba Henk" , "Niels de Vos"
> , "Jiffin Thottan" , "Aravinda
> Vishwanathapura Krishna Murthy" , "Anoop Chirayath
> Manjiyil Sajan" , "Ravishankar Narayanankutty"
> , "Kaushal Madappa" ,
> "Raghavendra Talur" , "Poornima Gurusiddaiah"
> , "Soumya Koduri" , "Kaleb
> Keithley" , "Jose Rivera" ,
> "Prashanth Pai" , "Samikshan Bairagya"
> , "Vijay Bellur" , "Prasanna
> Kalever" 
> Cc: "Gluster Devel" 
> Sent: Friday, August 26, 2016 12:21:07 PM
> Subject: Re: 3.9. feature freeze status check

> Prasanna, Prashant,
> Could you add a short description of the features you are working on for 3.9
> as well to the list?

> On Fri, Aug 26, 2016 at 9:39 PM, Pranith Kumar Karampuri <
> pkara...@redhat.com > wrote:

> > On Fri, Aug 26, 2016 at 9:38 PM, Pranith Kumar Karampuri <
> > pkara...@redhat.com > wrote:
> 

> > > hi,
> > 
> 
> > > Now that we are almost near the feature freeze date (31st of Aug), want
> > > to
> > > get a sense if any of the status of the features.
> > 
> 

> > I meant "want to get a sense of the status of the features"
> 

> > > Please respond with:
> > 
> 
> > > 1) Feature already merged
> > 
> 
> > > 2) Undergoing review will make it by 31st Aug
> > 
> 
> > > 3) Undergoing review, but may not make it by 31st Aug
> > 
> 
> > > 4) Feature won't make it for 3.9.
> > 
> 

> > > I added the features that were not planned(i.e. not in the 3.9 roadmap
> > > page)
> > > but made it to the release and not planned but may make it to release at
> > > the
> > > end of this mail.
> > 
> 
> > > If you added a feature on master that will be released as part of 3.9.0
> > > but
> > > forgot to add it to roadmap page, please let me know I will add it.
> > 
> 

> > > Here are the features planned as per the roadmap:
> > 
> 
> > > 1) Throttling
> > 
> 
> > > Feature owner: Ravishankar
> > 
> 

> > > 2) Trash improvements
> > 
> 
> > > Feature owners: Anoop, Jiffin
> > 
> 

> > > 3) Kerberos for Gluster protocols:
> > 
> 
> > > Feature owners: Niels, Csaba
> > 
> 

> > > 4) SELinux on gluster volumes:
> > 
> 
> > > Feature owners: Niels, Manikandan
> > 
> 

> > > 5) Native sub-directory mounts:
> > 
> 
> > > Feature owners: Kaushal, Pranith
> > 
> 

> > > 6) RichACL support for GlusterFS:
> > 
> 
> > > Feature owners: Rajesh Joseph
> > 
> 

> > > 7) Sharemodes/Share reservations:
> > 
> 
> > > Feature owners: Raghavendra Talur, Poornima G, Soumya Koduri, Rajesh
> > > Joseph,
> > > Anoop C S
> > 
> 

> > > 8) Integrate with external resource management software
> > 
> 
> > > Feature owners: Kaleb Keithley, Jose Rivera
> > 
> 

> > > 9) Python Wrappers for Gluster CLI Commands
> > 
> 
> > > Feature owners: Aravinda VK
> > 
> 

> > > 10) Package and ship libgfapi-python
> > 
> 
> > > Feature owners: Prashant Pai
> > 
> 

> > > 11) Management REST APIs
> > 
> 
> > > Feature owners: Aravinda VK
> > 
> 

> > > 12) Events APIs
> > 
> 
> > > Feature owners: Aravinda VK
> > 
> 

> > > 13) CLI to get state representation of a cluster from the local glusterd
> > > pov
> > 
> 
> > > Feature owners: Samikshan Bairagya
> > 
> 

> > > 14) Posix-locks Reclaim support
> > 
> 
> > > Feature owners: Soumya Koduri
> > 
> 

> > > 15) Deprecate striped volumes
> > 
> 
> > > Feature owners: Vijay Bellur, Niels de Vos
> > 
> 

> > > 16) Improvements in Gluster NFS-Ganesha integration
> > 
> 
> > > Feature owners: Jiffin Tony Thottan, Soumya Koduri
> > 
> 

> > > The following need to be added to the roadmap:
> > 
> 

> > > Features that made it to master already but were not palnned:
> > 
> 
> > > 1) Multi threaded self-heal in EC
> > 
> 
> > > Feature owner: Pranith (Did this because serkan asked for it. He has 9PB
> > > volume, self-healing takes a long time :-/)
> > 
> 

> > > 2) Lock revocation (Facebook patch)
> > 
> 
> > > Feature owner: Richard Wareing
> > 
> 

> > > Features that look like will make it to 3.9.0:
> > 
> 
> > > 1) Hardware extension support for EC
> > 
> 
> > > Feature owner: Xavi
> > 
> 

> > > 2) Reset brick support for replica volumes:
> > 
> 
> > > Feature owner: Anuradha
> > 
> 

> > > 3) Md-cache perf improvements in smb:
> > 
> 
> > > Feature owner: Poornima
> > 
> 

Feature undergoing review. It will be in tech-preview for this release. Main 
feature will be merged by 31st August 2016. 

> > > --
> > 
> 
> > > Pranith
> > 
> 

> > --
> 
> > Pranith
> 

> --
> Pranith

Regards, 
Poornima 
___
Gluster-devel mailing 

Re: [Gluster-devel] mainline compilation fails

[Atin Mukherjee]

I've merged this patch to unblock the other patches to go through the smoke
and other regression. Given the volume of patches we have in the pipeline
for 3.9 and we are just couple of days away to 3.9 branching, this needed
an immediate attention.

We now need to rebase all 3.9 targeted patches (the ones which failed smoke
and other tests).

On Sun, Aug 28, 2016 at 8:34 PM, Atin Mukherjee  wrote:

> The patch http://review.gluster.org/#/c/15331/ is now ready for merge.
>
> Niels - could you merge it?
>
>
> On Saturday 27 August 2016, Prasanna Kalever  wrote:
>
>> Oops!
>> Didn't noticed these changes were part of parent/child patches, Just
>> noticed "BUILD BROKEN" and went into action :)
>>
>> I'm not sure about it!
>>
>> If it takes time to decide on whether the other set of patches need to
>> be taken or not, at-least my patch will fix the broken build (That
>> much I can assure)
>>
>> Lets see if the regressions break after these patch goes in (mostly
>> not, that I see from the code)
>>
>> Thanks,
>> --
>> Prasanna
>>
>>
>> On Sat, Aug 27, 2016 at 8:34 PM, Atin Mukherjee
>>  wrote:
>> >
>> >
>> > On Saturday 27 August 2016, Prasanna Kalever 
>> wrote:
>> >>
>> >> Here is the patch that should fix it
>> >> http://review.gluster.org/#/c/15331/
>> >
>> >
>> > Thanks! Well thats an easy way, but the question here is dont we need
>> the
>> > parent patch to be merged to ensure there is no other functionality
>> broken.
>> > Currently I see that the parent patch has a -1, in that case is it
>> required
>> > to revert 15225?
>> >>
>> >>
>> >> Happy weekend!
>> >>
>> >> --
>> >> Prasanna
>> >>
>> >>
>> >> On Sat, Aug 27, 2016 at 7:49 PM, Atin Mukherjee 
>> >> wrote:
>> >> > [1] has broken mainline compilation and I feel this could be because
>> its
>> >> > parent patch is not been merged otherwise smoke should have caught
>> it.
>> >> > Please resolve it at earliest.
>> >> >
>> >> > [1] http://review.gluster.org/#/c/15225/
>> >> >
>> >> >
>> >> > --Atin
>> >> >
>> >> > ___
>> >> > Gluster-devel mailing list
>> >> > Gluster-devel@gluster.org
>> >> > http://www.gluster.org/mailman/listinfo/gluster-devel
>> >> ___
>> >> Gluster-devel mailing list
>> >> Gluster-devel@gluster.org
>> >> http://www.gluster.org/mailman/listinfo/gluster-devel
>> >
>> >
>> >
>> > --
>> > --Atin
>>
>
>
> --
> --Atin
>



-- 

--Atin
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Update on GlusterFS-3.7.15

[Kaushal M]

Maintainers please stop merging patches into release-3.7 till further notice.

If anyone has changes that need to be merged, notify me here before
end of day today.

~kaushal

On Mon, Aug 22, 2016 at 6:03 PM, Oleksandr Natalenko
 wrote:
> [1] and [2], please. Those are 2 parts of one fix that is backported from
> master. They are already backported to 3.8, so only backport to 3.7 is left.
>
> Regards,
>   Oleksandr
>
> [1] http://review.gluster.org/#/c/14835/
> [2] http://review.gluster.org/#/c/15167/
>
>
>
> 22.08.2016 15:25, Kaushal M wrote:
>>
>> Notify the maintainers and me of any changes you need merged. You can
>> reply to this thread to notify. Try to ensure that your changes get
>> merged before this weekend.
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Gluster Community Newsletter, August 2016

[Amye Scavarda]

Important happenings for Gluster this month:
3.7.14 released
3.8.3 released

CFP for Gluster Developer Summit open until August 31st
http://www.gluster.org/pipermail/gluster-devel/2016-August/050435.html

gluster-users:
[Gluster-users] release-3.6 end of life
http://www.gluster.org/pipermail/gluster-users/2016-August/028078.html
- Joe requests a review of the 3.6 EOL proposal

[Gluster-users] The out-of-order GlusterFS 3.8.3 release addresses a
usability regression
http://www.gluster.org/pipermail/gluster-users/2016-August/028155.html
Niels de Vos announces 3.8.3

[Gluster-users] GlusterFS-3.7.14 released
http://www.gluster.org/pipermail/gluster-users/2016-August/027755.html
Kaushal M announces 3.7.14

Gluster-devel:

[Gluster-devel] Proposing a framework to leverage existing Python unit test
standards for our testing
http://www.gluster.org/pipermail/gluster-devel/2016-August/050321.html
Sankarshan Mukhopadhyay

[Gluster-devel] Events API: Adding support for Client Events
http://www.gluster.org/pipermail/gluster-devel/2016-August/050324.html
Aravinda discusses changes in Eventings

[Gluster-devel] Geo-replication: Improving the performance during History
Crawl
http://www.gluster.org/pipermail/gluster-devel/2016-August/050372.html
Aravinda starts a conversation about history and geo-replication

[Gluster-devel] Backup support for GlusterFS
http://www.gluster.org/pipermail/gluster-devel/2016-August/050381.html
Alok Srivastava revives an older thread on backup support for GlusterFS

[Gluster-devel] md-cache improvements
http://www.gluster.org/pipermail/gluster-devel/2016-August/050402.html
- Dan makes suggestions for md-cache improvements

[gluster-devel] Documentation Tooling Review
http://www.gluster.org/pipermail/gluster-devel/2016-August/050418.html
- Amye proposes some documentation tooling review

[Gluster-devel] CFP for Gluster Developer Summit
http://www.gluster.org/pipermail/gluster-devel/2016-August/050435.html
- Call for Proposals for Gluster Developer Summit

gluster-infra
[Gluster-infra] Please welcome Worker Ant
http://www.gluster.org/pipermail/gluster-infra/2016-August/002671.html
Nigel announces a new bugzilla bot

[Gluster-infra] Idea: Failure Trends
http://www.gluster.org/pipermail/gluster-infra/2016-August/002636.html
Nigel proposes a test failure tracking website

-- 
Amye Scavarda | a...@redhat.com | Gluster Community Lead
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] release-3.6 end of life

[Osborne, Paul (paul.osbo...@canterbury.ac.uk)]

Hi,


I would like to second this request.


I have Gluster 3.6.6 (which is due for upgrade real soon now) and 3.6.9 in use 
under Debian 7 "Wheezy" which itself is LTS until April 2018.


Whilst I plan to upgrade to 3.7 (or even 3.8) at some point; with the needing 
to book downtime etc to upgrade my entire clusters this is not a short term 
plan and takes careful testing, planning and approval of management to disrupt 
to services that are dependant.


Best wishes

Paul
--
Paul Osborne
Senior Systems Engineer
Canterbury Christ Church University
Tel: 01227 782751

From: gluster-users-boun...@gluster.org  on 
behalf of Joe Julian 
Sent: 18 August 2016 18:10:09
To: Gluster Devel; Gluster Users
Subject: [Gluster-users] release-3.6 end of life

I'd like to plead with the community to continue to support 3.6 as a
"lts" release. It's the last release version that can be used on Ubuntu
14.04 (Trusty Tahr) LTS which many users may be stuck using for quite
some time (eol of April 2019).

___
Gluster-users mailing list
gluster-us...@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] mainline compilation fails

[Atin Mukherjee]

The patch http://review.gluster.org/#/c/15331/ is now ready for merge.

Niels - could you merge it?

On Saturday 27 August 2016, Prasanna Kalever  wrote:

> Oops!
> Didn't noticed these changes were part of parent/child patches, Just
> noticed "BUILD BROKEN" and went into action :)
>
> I'm not sure about it!
>
> If it takes time to decide on whether the other set of patches need to
> be taken or not, at-least my patch will fix the broken build (That
> much I can assure)
>
> Lets see if the regressions break after these patch goes in (mostly
> not, that I see from the code)
>
> Thanks,
> --
> Prasanna
>
>
> On Sat, Aug 27, 2016 at 8:34 PM, Atin Mukherjee
> > wrote:
> >
> >
> > On Saturday 27 August 2016, Prasanna Kalever  > wrote:
> >>
> >> Here is the patch that should fix it
> >> http://review.gluster.org/#/c/15331/
> >
> >
> > Thanks! Well thats an easy way, but the question here is dont we need the
> > parent patch to be merged to ensure there is no other functionality
> broken.
> > Currently I see that the parent patch has a -1, in that case is it
> required
> > to revert 15225?
> >>
> >>
> >> Happy weekend!
> >>
> >> --
> >> Prasanna
> >>
> >>
> >> On Sat, Aug 27, 2016 at 7:49 PM, Atin Mukherjee  >
> >> wrote:
> >> > [1] has broken mainline compilation and I feel this could be because
> its
> >> > parent patch is not been merged otherwise smoke should have caught it.
> >> > Please resolve it at earliest.
> >> >
> >> > [1] http://review.gluster.org/#/c/15225/
> >> >
> >> >
> >> > --Atin
> >> >
> >> > ___
> >> > Gluster-devel mailing list
> >> > Gluster-devel@gluster.org 
> >> > http://www.gluster.org/mailman/listinfo/gluster-devel
> >> ___
> >> Gluster-devel mailing list
> >> Gluster-devel@gluster.org 
> >> http://www.gluster.org/mailman/listinfo/gluster-devel
> >
> >
> >
> > --
> > --Atin
>


-- 
--Atin
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] 3.9. feature freeze status check

[Pranith Kumar Karampuri]

On Sat, Aug 27, 2016 at 1:22 PM, Raghavendra Gowdappa 
wrote:

>
>
> - Original Message -
> > From: "Pranith Kumar Karampuri" 
> > To: "Rajesh Joseph" , "Manikandan Selvaganesh" <
> mselv...@redhat.com>, "Csaba Henk"
> > , "Niels de Vos" , "Jiffin
> Thottan" , "Aravinda
> > Vishwanathapura Krishna Murthy" , "Anoop Chirayath
> Manjiyil Sajan" ,
> > "Ravishankar Narayanankutty" , "Kaushal
> Madappa" , "Raghavendra Talur"
> > , "Poornima Gurusiddaiah" ,
> "Soumya Koduri" , "Kaleb
> > Keithley" , "Jose Rivera" ,
> "Prashanth Pai" , "Samikshan
> > Bairagya" , "Vijay Bellur" 
> > Cc: "Gluster Devel" 
> > Sent: Friday, August 26, 2016 9:38:55 PM
> > Subject: [Gluster-devel] 3.9. feature freeze status check
> >
> > hi,
> > Now that we are almost near the feature freeze date (31st of Aug), want
> to
> > get a sense if any of the status of the features.
> >
> > Please respond with:
> > 1) Feature already merged
> > 2) Undergoing review will make it by 31st Aug
> > 3) Undergoing review, but may not make it by 31st Aug
> > 4) Feature won't make it for 3.9.
> >
> > I added the features that were not planned(i.e. not in the 3.9 roadmap
> page)
> > but made it to the release and not planned but may make it to release at
> the
> > end of this mail.
> > If you added a feature on master that will be released as part of 3.9.0
> but
> > forgot to add it to roadmap page, please let me know I will add it.
> >
> > Here are the features planned as per the roadmap:
> > 1) Throttling
> > Feature owner: Ravishankar
> >
> > 2) Trash improvements
> > Feature owners: Anoop, Jiffin
> >
> > 3) Kerberos for Gluster protocols:
> > Feature owners: Niels, Csaba
> >
> > 4) SELinux on gluster volumes:
> > Feature owners: Niels, Manikandan
> >
> > 5) Native sub-directory mounts:
> > Feature owners: Kaushal, Pranith
> >
> > 6) RichACL support for GlusterFS:
> > Feature owners: Rajesh Joseph
> >
> > 7) Sharemodes/Share reservations:
> > Feature owners: Raghavendra Talur, Poornima G, Soumya Koduri, Rajesh
> Joseph,
> > Anoop C S
> >
> > 8) Integrate with external resource management software
> > Feature owners: Kaleb Keithley, Jose Rivera
> >
> > 9) Python Wrappers for Gluster CLI Commands
> > Feature owners: Aravinda VK
> >
> > 10) Package and ship libgfapi-python
> > Feature owners: Prashant Pai
> >
> > 11) Management REST APIs
> > Feature owners: Aravinda VK
> >
> > 12) Events APIs
> > Feature owners: Aravinda VK
> >
> > 13) CLI to get state representation of a cluster from the local glusterd
> pov
> > Feature owners: Samikshan Bairagya
> >
> > 14) Posix-locks Reclaim support
> > Feature owners: Soumya Koduri
> >
> > 15) Deprecate striped volumes
> > Feature owners: Vijay Bellur, Niels de Vos
> >
> > 16) Improvements in Gluster NFS-Ganesha integration
> > Feature owners: Jiffin Tony Thottan, Soumya Koduri
> >
> > The following need to be added to the roadmap:
> >
> > Features that made it to master already but were not palnned:
> > 1) Multi threaded self-heal in EC
> > Feature owner: Pranith (Did this because serkan asked for it. He has 9PB
> > volume, self-healing takes a long time :-/)
> >
> > 2) Lock revocation (Facebook patch)
> > Feature owner: Richard Wareing
> >
> > Features that look like will make it to 3.9.0:
> > 1) Hardware extension support for EC
> > Feature owner: Xavi
> >
> > 2) Reset brick support for replica volumes:
> > Feature owner: Anuradha
> >
> > 3) Md-cache perf improvements in smb:
> > Feature owner: Poornima
>
> This has pending reviews. I'll try to close it by Aug 31st.
>

Yeah, if it can be merged by 31st that will be great!


>
> >
> > --
> > Pranith
> >
> > ___
> > Gluster-devel mailing list
> > Gluster-devel@gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] md-cache changes and impact on tiering

[Dan Lambright]

- Original Message -
> From: "Poornima Gurusiddaiah" 
> To: "Dan Lambright" , "Nithya Balachandran" 
> 
> Cc: "Gluster Devel" 
> Sent: Tuesday, August 23, 2016 12:56:38 AM
> Subject: md-cache changes and impact on tiering
> 
> Hi,
> 
> The basic patches for md-cache and integrating it with cache-invalidation is
> merged in master. You could try master build and enable the following
> settings, to see if there is any impact on tiering performance at all:
> 
> # gluster volume set  performance.stat-prefetch on
> # gluster volume set  features.cache-invalidation on
> # gluster volume set  performance.cache-samba-metadata on
> # gluster volume set  performance.md-cache-timeout 600
> # gluster volume set  features.cache-invalidation-timeout 600

On the tests I run, this cut the number of LOOKUPs by about three orders of 
magnitude. Each saved lookup reduces a round trip over the network.

I'm running a "small file" performance test. It creates 16K 64 byte files in a 
seven level directory. It then reads each file twice. 

Configuration is HOT: 2 x 2 ramdisk COLD: 2 x (8 + 4) disk, network is 
1Mb/s 9000 mtu. The number of lookups is a factor of the number of 
directories and subvolumes. On each I/O the file is re-opened and each 
directory is laboriously rechecked for existence/permission. 

Without using md-cache, these lookups used to be further propagated across each 
subvolume by DHT to obtain the entire layout. So it would be something like 
order of 16K*7*26 round trips across the network. 

The counts are all visible with gluster profile. 


> 
> Note: It has to be executed in the same order.
> 
> Tracker bug: https://bugzilla.redhat.com/show_bug.cgi?id=1211863
> Patches:
> http://review.gluster.org/#/q/status:open+project:glusterfs+branch:master+topic:bug-1211863
> 
> Thanks,
> Poornima
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Events API new Port requirement

[Aravinda]

Thanks Niels and Joe,

Changed my patch to use 24009. Dynamic port is not required since one 
process per node.


24005 is already registered by "med-ci" as checked in /etc/services

regards
Aravinda

On Sunday 28 August 2016 02:13 PM, Niels de Vos wrote:

On Sat, Aug 27, 2016 at 02:02:43PM -0700, Joe Julian wrote:

On 08/27/2016 12:15 PM, Niels de Vos wrote:

On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:

Hi,

As part of Client events support, glustereventsd needs to be configured to
use a port. Following ports are already used by Gluster components.
24007  For glusterd
24008  For glusterd RDMA port management
38465  Gluster NFS service
38466  Gluster NFS service
38467  Gluster NFS service
38468  Gluster NFS service
38469  Gluster NFS service
49152-49664512 ports for bricks

If I remember correctly, 24009+ ports were used by old GlusterFS(<3.4). In
the patch eventsd is using 24005. Please suggest which port glustereventsd
can use?(Can we use 24009 port)
http://review.gluster.org/15189

I guess you can use 24009, but it would be way better to either:

a. use glusterd-portmapper and get a dynamic port 49152+

Strongly disagree. It's enough that we have to poke dynamic holes in
firewalls already (sure it's easy with firewalld, but with hardware
firewalls or openstack security groups we just have to open a huge hole),
adding one that we also need to use as a service endpoint is too much.

Heh, yes, of course. I also think it needs quite some work in
glustereventsd to be able to use it, and then the clients need to
request the port from glusterd before they can consume events. It is the
way how other gluster clients work atm.


b. register a port at IANA, see /etc/services
 (maybe we should try to register the 24007+24008 ports in any case)

+100

This definitely has my preference too. I've always wanted to try to
register port 24007/8, and maybe the time has come to look into it.

Thanks for sharing your opinion!
Niels


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Events API new Port requirement

[Niels de Vos]

On Sat, Aug 27, 2016 at 02:02:43PM -0700, Joe Julian wrote:
> On 08/27/2016 12:15 PM, Niels de Vos wrote:
> > On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:
> > > Hi,
> > > 
> > > As part of Client events support, glustereventsd needs to be configured to
> > > use a port. Following ports are already used by Gluster components.
> > > 24007  For glusterd
> > > 24008  For glusterd RDMA port management
> > > 38465  Gluster NFS service
> > > 38466  Gluster NFS service
> > > 38467  Gluster NFS service
> > > 38468  Gluster NFS service
> > > 38469  Gluster NFS service
> > > 49152-49664512 ports for bricks
> > > 
> > > If I remember correctly, 24009+ ports were used by old GlusterFS(<3.4). In
> > > the patch eventsd is using 24005. Please suggest which port glustereventsd
> > > can use?(Can we use 24009 port)
> > > http://review.gluster.org/15189
> > I guess you can use 24009, but it would be way better to either:
> > 
> > a. use glusterd-portmapper and get a dynamic port 49152+
> Strongly disagree. It's enough that we have to poke dynamic holes in
> firewalls already (sure it's easy with firewalld, but with hardware
> firewalls or openstack security groups we just have to open a huge hole),
> adding one that we also need to use as a service endpoint is too much.

Heh, yes, of course. I also think it needs quite some work in
glustereventsd to be able to use it, and then the clients need to
request the port from glusterd before they can consume events. It is the
way how other gluster clients work atm.

> > b. register a port at IANA, see /etc/services
> > (maybe we should try to register the 24007+24008 ports in any case)
> +100

This definitely has my preference too. I've always wanted to try to
register port 24007/8, and maybe the time has come to look into it.

Thanks for sharing your opinion!
Niels


signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel