Re: [Gluster-devel] [Gluster-users] 2018 - Plans and Expectations on Gluster Community

[Hetz Ben Hamo]

Hi Amar,

If can say something about the development of GlusterFS - is that there are
2 missing things:

1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 because
someone support to enable NFS-Ganesha. from the gluster command has been
vanished without anything mentioned in the error message what other
commands replaces it. Judging from other people's answers - the answer is
storhaug does it from now, but there are practically *0 Documentation* how
to use it.
2. There's a new tool in glusterFS to enable automation called gdep[oy, but
again, the documentation for it is pretty short, there isn't for example a
config for 2 node replication cluster with NFS-Ganesha, one of the most
popular configuration for testing so a person could help from this example
how things do work.
3. The commercial product (RHGS) is "stuck" in the 3.3 days, is there any
chance it will move forward to any of the last stable versions?

Thanks


On Tue, Jan 2, 2018 at 4:15 AM, Amar Tumballi  wrote:

> Hi All,
>
> First of all, happy new year 2018! Hope all of your wishes come true this
> year, and hope you will have time for contributing to Gluster Project this
> year too :-)
>
> As a contributor and one of the maintainers of the project I would like to
> propose below plans for Gluster Project, and please share your feedback,
> and comments on them.
>
>
>- *Improved Automation to reduce the process burden*
>
> We started some effort in this direction already. The thought process is
> captured here: https://docs.google.com/document/d/1AFkZmRRDXRxs21GnGa
> uieIyiIiRZ-nTEW8CPi7Gbp3g/edit?usp=sharing
>
> We need your help to share experience from other projects, and help to
> automate most of it.
>
>- *Use case driven documentation*
>
> Will be an on-going effort, but instead of focusing on more options,
> different way of doing things, we will try to keep one very well tested way
> in documentation.
>
> All other options, hacks etc will be moved into 'Advanced' section.
>
>- *Participation, meetups in more conferences and events, across the
>globe.*
>
> We will try to participate in more events, so users can interact with more
> developers, and express their concerns, suggestions, discuss ideas etc.
>
> We will be open to hear both good and bad things about project, so we can
> continue good things, and fix the things which are not going well. Do let
> us know about some events where you would like to see some of the
> developers, so we can see what can be done to arrange their travel.
>
>- *Focus on Integrations with other projects/products.*
>
> In storage, it is better to be 100% (or close to it) fit for some use
> cases / few use cases, instead of trying to be good for everyone and
> solving around 90% issues in generic use-case. Hence we will try to get
> complete at certain use cases while continuing to get better overall.
>
> We will be happy to get contribution in this direction, and also will work
> on making sure project is integration friendly. We will take integration
> issues with priority, and would work with different communities to get this
> effort move on properly.
>
>
>- *Continue with stable release cycles*
>
> Since last 4-5 releases, we have been sticking to timelines. We promise to
> keep this going. We will make Gluster 4.0 happen, and by 4.1 release, would
> like to see most of the community starts thinking about migration to 4.x
> versions.
>
> 
>
> We are also working on many more 'tasks' in the meantime. If you need
> anything, feel free to send an email, and/or raise an issue in github.
>
> Once again, Wish you all happy new year 2018!
>
> Regards,
>
> --
> Amar Tumballi (amarts)
>
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] 2018 - Plans and Expectations on Gluster Community

[Hetz Ben Hamo]

Thanks for this info, I wish it was mentioned somewhere in the
documentation.

On Tue, Jan 2, 2018 at 11:27 AM, Atin Mukherjee  wrote:

>
>
> On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo  wrote:
>
>> Hi Amar,
>>
>> If can say something about the development of GlusterFS - is that there
>> are 2 missing things:
>>
>> 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 because
>> someone support to enable NFS-Ganesha. from the gluster command has been
>> vanished without anything mentioned in the error message what other
>> commands replaces it. Judging from other people's answers - the answer is
>> storhaug does it from now, but there are practically *0 Documentation* how
>> to use it.
>> 2. There's a new tool in glusterFS to enable automation called gdep[oy,
>> but again, the documentation for it is pretty short, there isn't for
>> example a config for 2 node replication cluster with NFS-Ganesha, one of
>> the most popular configuration for testing so a person could help from this
>> example how things do work.
>> 3. The commercial product (RHGS) is "stuck" in the 3.3 days, is there any
>> chance it will move forward to any of the last stable versions?
>>
>
> That's not true, RHGS 3.3 is not GlusterFS 3.3 rather it's a rebase to
> glusterfs-3.8.4 + plenty of cherry picks from mainline. It's just how RHGS
> chooses to maintain its version numbers.
>
> Thanks
>
>
> On Tue, Jan 2, 2018 at 4:15 AM, Amar Tumballi  wrote:
>
>> Hi All,
>>
>> First of all, happy new year 2018! Hope all of your wishes come true this
>> year, and hope you will have time for contributing to Gluster Project this
>> year too :-)
>>
>> As a contributor and one of the maintainers of the project I would like
>> to propose below plans for Gluster Project, and please share your feedback,
>> and comments on them.
>>
>>
>>- *Improved Automation to reduce the process burden*
>>
>> We started some effort in this direction already. The thought process is
>> captured here: https://docs.google.com/document/d/1AFkZmRRDXRxs21GnGa
>> uieIyiIiRZ-nTEW8CPi7Gbp3g/edit?usp=sharing
>>
>> We need your help to share experience from other projects, and help to
>> automate most of it.
>>
>>- *Use case driven documentation*
>>
>> Will be an on-going effort, but instead of focusing on more options,
>> different way of doing things, we will try to keep one very well tested way
>> in documentation.
>>
>> All other options, hacks etc will be moved into 'Advanced' section.
>>
>>- *Participation, meetups in more conferences and events, across the
>>globe.*
>>
>> We will try to participate in more events, so users can interact with
>> more developers, and express their concerns, suggestions, discuss ideas etc.
>>
>> We will be open to hear both good and bad things about project, so we can
>> continue good things, and fix the things which are not going well. Do let
>> us know about some events where you would like to see some of the
>> developers, so we can see what can be done to arrange their travel.
>>
>>- *Focus on Integrations with other projects/products.*
>>
>> In storage, it is better to be 100% (or close to it) fit for some use
>> cases / few use cases, instead of trying to be good for everyone and
>> solving around 90% issues in generic use-case. Hence we will try to get
>> complete at certain use cases while continuing to get better overall.
>>
>> We will be happy to get contribution in this direction, and also will
>> work on making sure project is integration friendly. We will take
>> integration issues with priority, and would work with different communities
>> to get this effort move on properly.
>>
>>
>>- *Continue with stable release cycles*
>>
>> Since last 4-5 releases, we have been sticking to timelines. We promise
>> to keep this going. We will make Gluster 4.0 happen, and by 4.1 release,
>> would like to see most of the community starts thinking about migration to
>> 4.x versions.
>>
>> 
>>
>> We are also working on many more 'tasks' in the meantime. If you need
>> anything, feel free to send an email, and/or raise an issue in github.
>>
>> Once again, Wish you all happy new year 2018!
>>
>> Regards,
>>
>> --
>> Amar Tumballi (amarts)
>>
>> ___
>> Gluster-users mailing list
>> gluster-us...@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
>
>
>> ___
>> Gluster-users mailing list
>> gluster-us...@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] 2018 - Plans and Expectations on Gluster Community

[Shyam Ranganathan]

On 01/03/2018 08:05 AM, Kaleb S. KEITHLEY wrote:
> On 01/02/2018 11:03 PM, Vijay Bellur wrote:
>> ...     The people who were writing storhaug never finished it. Keep
>> using
>>     3.10 until storhaug gets finished.
>>
>>
>>
>> Since 3.10 will be EOL in approximately 2 months from now, what would
>> be our answer for NFS HA if storahug is not finished by then?

Correction, 3.10 will not be EOL when 4.0 is released, as 4.0 is an STM.
The oldest LTM will be EOL'd when the next LTM releases, which is 4.1.
Hence, we have another 5 months before which 3.10 is EOL'd.

>>
>>   -   Use ctdb
>>   -   Restore nfs.ganesha CLI support
>>   -   Something else?
>>
>> Have we already documented upgrade instructions for those users
>> utilizing nfs.ganesha CLI in 3.8? If not already done so, it would be
>> useful to have them listed somewhere.
>>
> 
> I have a pretty high degree of confidence that I can have storhaug
> usable by or before 4.0. The bits I have on my devel box are almost
> ready to post on github.
> 
> I'd like to abandon the github repo at
> https://github.com/linux-ha-storage/storhaug; and create a new repo
> under https://github.com/gluster/storhaug. I dare say there are other
> Linux storage solutions besides gluster+ganesha+samba that storhaug
> doesn't handle.
> 
> And upgrade instructions for what? Upgrading/switching from legacy
> glusterd to storhaug? No, not yet. Doesn't make sense since there's no
> (usable) storhaug yet.
> 
> -- 
> 
> Kaleb
> 
> 
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] 2018 - Plans and Expectations on Gluster Community

[Kaleb S. KEITHLEY]

On 01/02/2018 11:03 PM, Vijay Bellur wrote:
... 
The people who were writing storhaug never finished it. Keep using

3.10 until storhaug gets finished.



Since 3.10 will be EOL in approximately 2 months from now, what would be 
our answer for NFS HA if storahug is not finished by then?


  -   Use ctdb
  -   Restore nfs.ganesha CLI support
  -   Something else?

Have we already documented upgrade instructions for those users 
utilizing nfs.ganesha CLI in 3.8? If not already done so, it would be 
useful to have them listed somewhere.




I have a pretty high degree of confidence that I can have storhaug 
usable by or before 4.0. The bits I have on my devel box are almost 
ready to post on github.


I'd like to abandon the github repo at 
https://github.com/linux-ha-storage/storhaug; and create a new repo 
under https://github.com/gluster/storhaug. I dare say there are other 
Linux storage solutions besides gluster+ganesha+samba that storhaug 
doesn't handle.


And upgrade instructions for what? Upgrading/switching from legacy 
glusterd to storhaug? No, not yet. Doesn't make sense since there's no 
(usable) storhaug yet.


--

Kaleb


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

Re: [Gluster-devel] [Gluster-users] 2018 - Plans and Expectations on Gluster Community

[Vijay Bellur]

On Tue, Jan 2, 2018 at 4:09 AM, Kaleb S. KEITHLEY 
wrote:

>
>
>>
>> On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo  h...@hetz.biz>> wrote:
>>
>> Hi Amar,
>>
>> If can say something about the development of GlusterFS - is that
>> there are 2 missing things:
>>
>> 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8
>> because someone [removed] support to enable NFS-Ganesha. from the
>> gluster
>> command has been vanished without anything mentioned in the error
>> message what other commands replaces it.
>>
>
> Not true. The nfs-ganesha support is still there in GlusterFS-3.10.
>
> Judging from other people's
>> answers - the answer is storhaug does it from now, but there are
>> practically *0 Documentation* how to use it.
>>
>
> The people who were writing storhaug never finished it. Keep using 3.10
> until storhaug gets finished.
>


Since 3.10 will be EOL in approximately 2 months from now, what would be
our answer for NFS HA if storahug is not finished by then?

 -   Use ctdb
 -   Restore nfs.ganesha CLI support
 -   Something else?

Have we already documented upgrade instructions for those users utilizing
nfs.ganesha CLI in 3.8? If not already done so, it would be useful to have
them listed somewhere.

Thanks,
Vijay
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] 2018 - Plans and Expectations on Gluster Community

[Amar Tumballi]

On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo  wrote:

> Hi Amar,
>
> If can say something about the development of GlusterFS - is that there
> are 2 missing things:
>
> 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 because
> someone support to enable NFS-Ganesha. from the gluster command has been
> vanished without anything mentioned in the error message what other
> commands replaces it. Judging from other people's answers - the answer is
> storhaug does it from now, but there are practically *0 Documentation* how
> to use it.
>

Sorry about your experience regarding upgrade. We have taken upgrade as a
major priority for release team, and hence are actually calling 4.1 as the
first release of 4.x series saner to upgrade, where as 4.0 release would be
good for anyone starting new, and want to test in a new setup.

We will make sure that the documentation focus will cover migration section
properly.


> 2. There's a new tool in glusterFS to enable automation called gdep[oy,
> but again, the documentation for it is pretty short, there isn't for
> example a config for 2 node replication cluster with NFS-Ganesha, one of
> the most popular configuration for testing so a person could help from this
> example how things do work.
>

Yes, When I spoke of Focus on Integrations, this was on our head. We want
to make sure we have peripheral projects to deal with managing filesystem.
gDeploy is one of that.

Actually, to make things more ansible friendly, we also started
https://github.com/gluster/gluster-ansible too. Which can be used as per
the need. We will most probably move towards documenting steps using these
projects in the use case specific documentation.


3. The commercial product (RHGS) is "stuck" in the 3.3 days, is there any
> chance it will move forward to any of the last stable versions?
>
>
This is more of a question for Red Hat Product / Support team. I am sure
Red Hat's product version is not direct map to glusterfs version.

Regards,
Amar


> Thanks
>
>
> On Tue, Jan 2, 2018 at 4:15 AM, Amar Tumballi  wrote:
>
>> Hi All,
>>
>> First of all, happy new year 2018! Hope all of your wishes come true this
>> year, and hope you will have time for contributing to Gluster Project this
>> year too :-)
>>
>> As a contributor and one of the maintainers of the project I would like
>> to propose below plans for Gluster Project, and please share your feedback,
>> and comments on them.
>>
>>
>>- *Improved Automation to reduce the process burden*
>>
>> We started some effort in this direction already. The thought process is
>> captured here: https://docs.google.com/document/d/1AFkZmRRDXRxs21GnGa
>> uieIyiIiRZ-nTEW8CPi7Gbp3g/edit?usp=sharing
>>
>> We need your help to share experience from other projects, and help to
>> automate most of it.
>>
>>- *Use case driven documentation*
>>
>> Will be an on-going effort, but instead of focusing on more options,
>> different way of doing things, we will try to keep one very well tested way
>> in documentation.
>>
>> All other options, hacks etc will be moved into 'Advanced' section.
>>
>>- *Participation, meetups in more conferences and events, across the
>>globe.*
>>
>> We will try to participate in more events, so users can interact with
>> more developers, and express their concerns, suggestions, discuss ideas etc.
>>
>> We will be open to hear both good and bad things about project, so we can
>> continue good things, and fix the things which are not going well. Do let
>> us know about some events where you would like to see some of the
>> developers, so we can see what can be done to arrange their travel.
>>
>>- *Focus on Integrations with other projects/products.*
>>
>> In storage, it is better to be 100% (or close to it) fit for some use
>> cases / few use cases, instead of trying to be good for everyone and
>> solving around 90% issues in generic use-case. Hence we will try to get
>> complete at certain use cases while continuing to get better overall.
>>
>> We will be happy to get contribution in this direction, and also will
>> work on making sure project is integration friendly. We will take
>> integration issues with priority, and would work with different communities
>> to get this effort move on properly.
>>
>>
>>- *Continue with stable release cycles*
>>
>> Since last 4-5 releases, we have been sticking to timelines. We promise
>> to keep this going. We will make Gluster 4.0 happen, and by 4.1 release,
>> would like to see most of the community starts thinking about migration to
>> 4.x versions.
>>
>> 
>>
>> We are also working on many more 'tasks' in the meantime. If you need
>> anything, feel free to send an email, and/or raise an issue in github.
>>
>> Once again, Wish you all happy new year 2018!
>>
>> Regards,
>>
>> --
>> Amar Tumballi (amarts)
>>
>> ___
>> Gluster-users mailing list
>> gluster-us...@gluster.org
>> 

Re: [Gluster-devel] [Gluster-users] 2018 - Plans and Expectations on Gluster Community

[Atin Mukherjee]

On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo  wrote:

> Hi Amar,
>
> If can say something about the development of GlusterFS - is that there
> are 2 missing things:
>
> 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 because
> someone support to enable NFS-Ganesha. from the gluster command has been
> vanished without anything mentioned in the error message what other
> commands replaces it. Judging from other people's answers - the answer is
> storhaug does it from now, but there are practically *0 Documentation* how
> to use it.
> 2. There's a new tool in glusterFS to enable automation called gdep[oy,
> but again, the documentation for it is pretty short, there isn't for
> example a config for 2 node replication cluster with NFS-Ganesha, one of
> the most popular configuration for testing so a person could help from this
> example how things do work.
> 3. The commercial product (RHGS) is "stuck" in the 3.3 days, is there any
> chance it will move forward to any of the last stable versions?
>

That's not true, RHGS 3.3 is not GlusterFS 3.3 rather it's a rebase to
glusterfs-3.8.4 + plenty of cherry picks from mainline. It's just how RHGS
chooses to maintain its version numbers.

Thanks


On Tue, Jan 2, 2018 at 4:15 AM, Amar Tumballi  wrote:

> Hi All,
>
> First of all, happy new year 2018! Hope all of your wishes come true this
> year, and hope you will have time for contributing to Gluster Project this
> year too :-)
>
> As a contributor and one of the maintainers of the project I would like to
> propose below plans for Gluster Project, and please share your feedback,
> and comments on them.
>
>
>- *Improved Automation to reduce the process burden*
>
> We started some effort in this direction already. The thought process is
> captured here: https://docs.google.com/document/d/1AFkZmRRDXRxs21GnGa
> uieIyiIiRZ-nTEW8CPi7Gbp3g/edit?usp=sharing
>
> We need your help to share experience from other projects, and help to
> automate most of it.
>
>- *Use case driven documentation*
>
> Will be an on-going effort, but instead of focusing on more options,
> different way of doing things, we will try to keep one very well tested way
> in documentation.
>
> All other options, hacks etc will be moved into 'Advanced' section.
>
>- *Participation, meetups in more conferences and events, across the
>globe.*
>
> We will try to participate in more events, so users can interact with more
> developers, and express their concerns, suggestions, discuss ideas etc.
>
> We will be open to hear both good and bad things about project, so we can
> continue good things, and fix the things which are not going well. Do let
> us know about some events where you would like to see some of the
> developers, so we can see what can be done to arrange their travel.
>
>- *Focus on Integrations with other projects/products.*
>
> In storage, it is better to be 100% (or close to it) fit for some use
> cases / few use cases, instead of trying to be good for everyone and
> solving around 90% issues in generic use-case. Hence we will try to get
> complete at certain use cases while continuing to get better overall.
>
> We will be happy to get contribution in this direction, and also will work
> on making sure project is integration friendly. We will take integration
> issues with priority, and would work with different communities to get this
> effort move on properly.
>
>
>- *Continue with stable release cycles*
>
> Since last 4-5 releases, we have been sticking to timelines. We promise to
> keep this going. We will make Gluster 4.0 happen, and by 4.1 release, would
> like to see most of the community starts thinking about migration to 4.x
> versions.
>
> 
>
> We are also working on many more 'tasks' in the meantime. If you need
> anything, feel free to send an email, and/or raise an issue in github.
>
> Once again, Wish you all happy new year 2018!
>
> Regards,
>
> --
> Amar Tumballi (amarts)
>
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>


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