Thanks Jiffin, Btw, the nfs-ganesha part in the release notes is having a wrong header, so it's not highlighted. One thing that it is still mystery to me: gluster 3.8.x does all what the release notes of 3.9 says - automatically. Any chance that someone could port it to 3.9? Thanks for the links On Wed, Dec 6, 2017 at 7:28 AM, Jiffin Tony Thottan <jthottan at redhat.com> wrote:> Hi, > > On Monday 04 December 2017 07:43 PM, Hetz Ben Hamo wrote: > > Hi Jiffin, > > I looked at the document, and there are 2 things: > > 1. In Gluster 3.8 it seems you don't need to do that at all, it creates > this automatically, so why not in 3.10? > > > > Kindly please refer the mail[1] and release note [2] for glusterfs-3.9 > > Regards, > Jiffin > > [1] https://www.spinics.net/lists/gluster-devel/msg20488.html > [2] http://docs.gluster.org/en/latest/release-notes/3.9.0/ > > > > 2. The step by step guide, in the last item, doesn't say where exactly do > I need to create the nfs-ganesha directory. The copy/paste seems irrelevant > as enabling nfs-ganesha creates automatically the ganesha.conf and a > subdirectory (called "exports") with the volume share configuration file. > > Also, could someone tell me whats up with no ganesha on 3.12? > > Thanks > > On Mon, Dec 4, 2017 at 11:47 AM, Jiffin Tony Thottan <jthottan at redhat.com> > wrote: > >> >> >> On Saturday 02 December 2017 07:00 PM, Hetz Ben Hamo wrote: >> >> HI, >> >> I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. >> >> I'm trying to create a very simple 2 nodes cluster to be used with >> NFS-ganesha. I've created the bricks and the volume. Here's the output: >> >> # gluster volume info >> >> Volume Name: cluster-demo >> Type: Replicate >> Volume ID: 9c835a8e-c0ec-494c-a73b-cca9d77871c5 >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x 2 = 2 >> Transport-type: tcp >> Bricks: >> Brick1: glnode1:/data/brick1/gv0 >> Brick2: glnode2:/data/brick1/gv0 >> Options Reconfigured: >> nfs.disable: on >> transport.address-family: inet >> cluster.enable-shared-storage: enable >> >> Volume Name: gluster_shared_storage >> Type: Replicate >> Volume ID: caf36f36-0364-4ab9-a158-f0d1205898c4 >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x 2 = 2 >> Transport-type: tcp >> Bricks: >> Brick1: glnode2:/var/lib/glusterd/ss_brick >> Brick2: 192.168.0.95:/var/lib/glusterd/ss_brick >> Options Reconfigured: >> transport.address-family: inet >> nfs.disable: on >> cluster.enable-shared-storage: enable >> >> However, when I'm trying to run gluster nfs-ganesha enable - it creates a >> wrong symbolic link and failes: >> >> # gluster nfs-ganesha enable >> Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the >> trusted pool. Do you still want to continue? >> (y/n) y >> This will take a few minutes to complete. Please wait .. >> nfs-ganesha: failed: creation of symlink ganesha.conf in /etc/ganesha >> failed >> >> wrong link: ganesha.conf -> /var/run/gluster/shared_storag >> e/nfs-ganesha/ganesha.conf >> >> # ls -l /var/run/gluster/shared_storage/ >> total 0 >> >> I've seen some reports (and fixed) in Red Hat's Bugzilla and looked at >> the Red Hat solutions (https://access.redhat.com/solutions/3099581) but >> this doesn't help. >> >> >> Suggestions? >> >> Hi, >> >> It seems you have not created directory nfs-ganesha under shared storage >> and plus copy/create ganesha.conf/ganesha-ha.conf inside >> Please follow this document http://docs.gluster.org/en/lat >> est/Administrator%20Guide/NFS-Ganesha%20GlusterFS%20Integration/ >> >> Regards, >> Jiffin >> >> >> >> >> >> I tried to upgrade to Gluster 3.12 and it seems Ganesha support was >> kicked out? whats replacing it? >> >> >> >> _______________________________________________ >> Gluster-users mailing listGluster-users at gluster.orghttp://lists.gluster.org/mailman/listinfo/gluster-users >> >> >> > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171206/76f828cb/attachment.html>
On Wednesday 06 December 2017 11:08 AM, Hetz Ben Hamo wrote:> Thanks Jiffin, > > Btw, the nfs-ganesha part in the release notes is having a wrong > header, so it's not highlighted. > > One thing that it is still mystery to me: gluster 3.8.x does all what > the release notes of 3.9 says - automatically. Any chance that someone > could port it to 3.9?I didn't get that. can u tell me what all 3.8 does automatically ? -- Jiffin> > Thanks for the links > > On Wed, Dec 6, 2017 at 7:28 AM, Jiffin Tony Thottan > <jthottan at redhat.com <mailto:jthottan at redhat.com>> wrote: > > Hi, > > > On Monday 04 December 2017 07:43 PM, Hetz Ben Hamo wrote: >> Hi Jiffin, >> >> I looked at the document, and there are 2 things: >> >> 1. In Gluster 3.8 it seems you don't need to do that at all, it >> creates this automatically, so why not in 3.10? > > > Kindly please refer the mail[1] and release note [2] for glusterfs-3.9 > > Regards, > Jiffin > > [1] https://www.spinics.net/lists/gluster-devel/msg20488.html > <https://www.spinics.net/lists/gluster-devel/msg20488.html> > [2] http://docs.gluster.org/en/latest/release-notes/3.9.0/ > <http://docs.gluster.org/en/latest/release-notes/3.9.0/> > > > >> 2. The step by step guide, in the last item, doesn't say where >> exactly do I need to create the nfs-ganesha directory. The >> copy/paste seems irrelevant as enabling nfs-ganesha creates >> automatically the ganesha.conf and a subdirectory (called >> "exports") with the volume share configuration file. >> >> Also, could someone tell me whats up with no ganesha on 3.12? >> >> Thanks >> >> On Mon, Dec 4, 2017 at 11:47 AM, Jiffin Tony Thottan >> <jthottan at redhat.com <mailto:jthottan at redhat.com>> wrote: >> >> >> >> On Saturday 02 December 2017 07:00 PM, Hetz Ben Hamo wrote: >>> HI, >>> >>> I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. >>> >>> I'm trying to create a very simple 2 nodes cluster to be >>> used with NFS-ganesha. I've created the bricks and the >>> volume. Here's the output: >>> >>> # gluster volume info >>> >>> Volume Name: cluster-demo >>> Type: Replicate >>> Volume ID: 9c835a8e-c0ec-494c-a73b-cca9d77871c5 >>> Status: Started >>> Snapshot Count: 0 >>> Number of Bricks: 1 x 2 = 2 >>> Transport-type: tcp >>> Bricks: >>> Brick1: glnode1:/data/brick1/gv0 >>> Brick2: glnode2:/data/brick1/gv0 >>> Options Reconfigured: >>> nfs.disable: on >>> transport.address-family: inet >>> cluster.enable-shared-storage: enable >>> >>> Volume Name: gluster_shared_storage >>> Type: Replicate >>> Volume ID: caf36f36-0364-4ab9-a158-f0d1205898c4 >>> Status: Started >>> Snapshot Count: 0 >>> Number of Bricks: 1 x 2 = 2 >>> Transport-type: tcp >>> Bricks: >>> Brick1: glnode2:/var/lib/glusterd/ss_brick >>> Brick2: 192.168.0.95:/var/lib/glusterd/ss_brick >>> Options Reconfigured: >>> transport.address-family: inet >>> nfs.disable: on >>> cluster.enable-shared-storage: enable >>> >>> However, when I'm trying to run?gluster nfs-ganesha enable - >>> it creates a wrong symbolic link and failes: >>> >>> # gluster nfs-ganesha enable >>> Enabling NFS-Ganesha requires Gluster-NFS to be disabled >>> across the trusted pool. Do you still want to continue? >>> ?(y/n) y >>> This will take a few minutes to complete. Please wait .. >>> nfs-ganesha: failed: creation of symlink ganesha.conf in >>> /etc/ganesha failed >>> >>> wrong link: ganesha.conf -> >>> /var/run/gluster/shared_storage/nfs-ganesha/ganesha.conf >>> >>> # ls -l /var/run/gluster/shared_storage/ >>> total 0 >>> >>> I've seen some reports (and fixed) in Red Hat's Bugzilla and >>> looked at the Red Hat solutions >>> (https://access.redhat.com/solutions/3099581 >>> <https://access.redhat.com/solutions/3099581>) but this >>> doesn't help. >>> >>> Suggestions? >> Hi, >> >> It seems you have not created directory nfs-ganesha under >> shared storage and plus copy/create >> ganesha.conf/ganesha-ha.conf inside >> Please follow this document >> http://docs.gluster.org/en/latest/Administrator%20Guide/NFS-Ganesha%20GlusterFS%20Integration/ >> <http://docs.gluster.org/en/latest/Administrator%20Guide/NFS-Ganesha%20GlusterFS%20Integration/> >> >> Regards, >> Jiffin >> >> >> >> >>> >>> I tried to upgrade to Gluster 3.12 and it seems Ganesha >>> support was kicked out? whats replacing it? >>> >>> >>> >>> _______________________________________________ >>> Gluster-users mailing list >>> Gluster-users at gluster.org <mailto:Gluster-users at gluster.org> >>> http://lists.gluster.org/mailman/listinfo/gluster-users >>> <http://lists.gluster.org/mailman/listinfo/gluster-users> >> >> > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171206/c5348b5b/attachment.html>
Hello. After working with the 3.12 flavor of gluster I learned nfs-ganesha was replaced with storhaug in 3.11.Have people been successfully utilizing storhaug and does any documentation exist for using it in a ha nfs configuration or is ha in gluster so rarely used it's a non-issue for most gluster users? Going through the lists, it was recommended in November to not use storhaug and if you want to run ha nfs you should instead use the 3.10 for it's last remaining version of nfs-ganesha. http://lists.gluster.org/pipermail//gluster-users/2017-November/032950.html To me that shift from using nfs-ganesha to storhaug was a huge change to be absorbed for a minor release version and was made bigger when storhaug does not appear to be ready go given the recommendation to go back and use 3.10. 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? Please advise. Thanks, Craig -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171220/67c34047/attachment.html>