10:03 a.m.
3.x is the current stable, but we haven't yet done a back port release,
as we only very recently opened 4-dev. With 3.0, the numbering has
changed, so we only use 2 version numbers rather than 3, so we skipped
2.9 entirely and went to 3.0. As soon as we have stuff to backport to
3.x, we'll open a 3-stable branch.
We have no current timetable for 4.x.
As to the ceph problem, we should backport the fixes to 2.8.x. We've
actually been waiting for those to be backported to released versions of
ceph, so that our CI builds start working again.
Daniel
On 2/4/20 9:56 AM, Denis Kondratenko wrote:
Hi guys,
There was new feature, that actually changed Ceph rados API:
https://github.com/ceph/ceph/pull/28664
Ganesha side:
https://github.com/nfs-ganesha/nfs-ganesha/commit/d197efbad9b353a562581ac...
It was backported to Nautilus, Luminous
Backporting make this affect downstream nfs-ganesha (2.8.3 for example),
after Ceph update, it doesn't build, not probably works any more.
Also it could be seen in Jenkins jobs here:
https://ci.centos.org/job/nfs-ganesha_trigger-fsal_rgw/
As result 2.8.3 ganesha couldn't be build with recent Ceph Nautilus,
Luminous and etc.
Question, how to be with it ?
I see couple of options:
1. revert API changes to Ceph and create new API function rgw_lookup2,
fix ganesha
2. backport feature to 2.8.x and maybe other supported branches
3. revert Ceph backports ?
4. other ?
BTW another question, is what are current release model for the nfs-ganesha?
I see last stable branch is V2.8-stable, there was no 2.9 or 3.0.
Are there plans for stable branches ?
Another question :) what is the current plans for 4.x release ?
Thanks,