On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo <hetz@xxxxxxxx> 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
ThanksOn Tue, Jan 2, 2018 at 4:15 AM, Amar Tumballi <atumball@xxxxxxxxxx> 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-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
Amar Tumballi (amarts)
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
