|
On 20/12/2017 16:51, Craig Lesle wrote:
With the release of 3.12
ltm and now 3.13 stm, when 4.0 is released 3.10 is shown to be
at eol;
Version Status Release_Date
EOL_Version EOL_Date
3.10 LTM 2017-02-27 4.0
3.11 EOL 2017-05-30 3.12 2017-8-30
3.12 LTM 2017-08-30 4.3
3.13 STM 2017-12-7 4.0
4.0 Planned STM about 2018-01 4.1
4.1 Planned LTM about 2018-04 n+
What approach should
a gluster consumer use today in setting up ha nfs on gluster?
Is it still being recommended to use 3.10 with it's eol coming
in what looks to be a matter of days/weeks? Perhaps the 3.10 support period
will be extended for a reasonable amount of time until such
time as storhaus in the 4 tree is ready to go and some kind
of workable upgrade path is
ready to get the HA portion upgraded from 3.10 to 4.x ?
Since storhaug appears to be a sticking point for
moving forward beyond 3.10 in the v3 tree, is it possible to
bring nfs-ganesha back for ha use at least through the v3 tree
or are all eyes on v4 and not looking back?
This is a good question
and I'm also curious to learn the answer. More generally, going
from release to EOL in just three months seems absolutely crazy to
me, particularly as this project is owned by Red Hat who purport
to maintain enterprise-grade support lifetimes. We should be
talking about years, not months. As things stand today, I can't
even deploy a new version before it's already EOL.
Cheers
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
