[Nfs-ganesha-support] Re: Nfs-ganesha rgw config for multi tenancy rgw users

Yes same access key and secret access key ( no uid is used ) -----Original Message----- From: Daniel Gryniewicz [mailto:dang@redhat.com] Sent: maandag 30 april 2018 14:40 To: Marc Roos; support Subject: Re: [Nfs-ganesha-support] Re: Nfs-ganesha rgw config for multi tenancy rgw users I mean does the s3cmd (or cyberduck) use the exact same credentials as

are specified in the ganesha.conf? Daniel On 04/26/2018 10:09 AM, Marc Roos wrote: > > > Yes, I can access the bucket via the s3cmd and cyberduck, or are you > refering to something else? > > > > -----Original Message----- > From: Daniel Gryniewicz [mailto:dang@redhat.com] > Sent: donderdag 26 april 2018 15:38 > To: support(a)lists.nfs-ganesha.org > Subject: [Nfs-ganesha-support] Re: Nfs-ganesha rgw config for multi > tenancy rgw users > > Does test$tester1 have permissions to access RGW? Mounting / should > see all the buckets, so it's likely a permission issue. > > Daniel > > On 04/26/2018 03:56 AM, Marc Roos wrote: >> >> >> I have the same as with / path, I can do the mount, but it is just >> empty >> >> [@mnt]# mount nfs:/rgwtester nfstest/ [@mnt]# ls -l nfstest/ >> ls: reading directory nfstest/: Remote I/O error total 0 >> >> >> >> Apr 26 14:56:15 c01 nfs-ganesha[3981596]: [main] >> export_commit_common >> :CONFIG :INFO :Export 301 created at pseudo (/rgwtester) with path >> (test3) and tag ((null)) perms (options=03303002 ,

>> , , , , , >> ) >> Apr 26 14:56:15 c01 nfs-ganesha[3981596]: [main] >> export_commit_common >> :CONFIG :INFO :Export 301 created at pseudo (/rgwtester) with path >> (test3) and tag ((null)) perms (options=03303002 ,

>> , , , , , >> ) >> Apr 26 14:56:15 c01 nfs-ganesha[3981596]: [main] >> export_commit_common >> :CONFIG :INFO :Export 301 has 1 defined clients Apr 26 14:56:15 c01 >> nfs-ganesha[3981596]: [main] export_commit_common :CONFIG :INFO >> :Export 301 has 1 defined clients Apr 26 14:56:15 c01 >> nfs-ganesha[3981596]: [main] build_default_root :CONFIG :INFO >> :Export >> 0 (/) successfully created Apr 26 14:56:15 c01 nfs-ganesha[3981596]: >> [main] build_default_root :CONFIG :INFO :Export 0 (/) successfully >> created Apr 26 14:56:16 c01 nfs-ganesha[3981596]: [main] >> fsal_save_ganesha_credentials :FSAL :INFO :Ganesha uid=0 gid=0 >> ngroups=0 Apr 26 14:56:16 c01 nfs-ganesha[3981596]: [main] >> fsal_save_ganesha_credentials :FSAL :INFO :Ganesha uid=0 gid=0 >> ngroups=0 >> >> -----Original Message----- >> From: Daniel Gryniewicz [mailto:dang@redhat.com] >> Sent: donderdag 26 april 2018 14:47 >> To: support(a)lists.nfs-ganesha.org >> Subject: [Nfs-ganesha-support] Re: Nfs-ganesha rgw config for multi >> tenancy rgw users >> >> I think it should be: >> >> Path="test3" >> >> so without the initial '/'. Buckets aren't paths, we're just >> abusing >> the existing Ganesha config to select them. >> >> Other than that, the client entry should match the equivalent entry >> in > >> your ceph.conf. >> >> Daniel >> >> On 04/26/2018 01:52 AM, Marc Roos wrote: >>> >>> >>> >>> I have problems exporting a bucket that really does exist. I have >>> tried Path = "/test:test3"; Path = "/test3"; Results in ganesha >>> fails > >>> to start with message ExportId=301 Path=/test:test3 >>> FSAL_ERROR=(Invalid object >>> type,0) >>> >>> If I use path=/ I can mount something but that is a empty export, >>> but > >>> cannot put files there. >>> >>> I have this in ganesha (client.rwg3 works with civetweb), should be

>>> sufficient not? >>> >>> RGW { >>> cluster = "ceph"; >>> name = "client.rgw3"; >>> ceph_conf = "/etc/ceph/ceph.conf"; >>> # for vstart cluster, name = "client.admin" >>> #init_args = "-d --debug-rgw=16"; } >>> >>> EXPORT { >>> Export_ID=301; >>> Path = "/test3"; >>> Pseudo = "/rgwtester"; >>> >>> FSAL { Name = RGW; User_Id = "test$tester1"; >>> Access_Key_Id ="sameass3"; Secret_Access_Key = "sameass3"; } >>> Disable_ACL = FALSE; >>> CLIENT { Clients = 192.168.x.0/24; } } >>> >>> [@~]$ s3cmd -c .s3cfg.tester1 ls >>> 2018-01-31 21:48 s3://test >>> 2018-02-01 11:44 s3://test2 >>> 2018-02-02 17:10 s3://test3 >>> >>> >>> [@~]$ s3cmd -c .s3cfg.tester1 ls s3://test3 >>> 2018-02-02 17:13 10485760 s3://test3/10MB.txt >>> 2018-02-05 12:57 26784 s3://test3/aB8q5BA_460s.jpg >>> >>> [@ ganesha]# rpm -qa | grep ganesh >>> nfs-ganesha-xfs-2.5.5-.el7.x86_64 >>> nfs-ganesha-2.5.5-.el7.x86_64 >>> nfs-ganesha-rgw-2.5.5-.el7.x86_64 >>> nfs-ganesha-ceph-2.5.5-.el7.x86_64 >>> nfs-ganesha-vfs-2.5.5-.el7.x86_64 >>> nfs-ganesha-mem-2.5.5-.el7.x86_64 >>> >>> On CentOS7 >>> _______________________________________________ >>> Support mailing list -- support(a)lists.nfs-ganesha.org To >>> unsubscribe >>> send an email to support-leave(a)lists.nfs-ganesha.org >>> >> _______________________________________________ >> Support mailing list -- support(a)lists.nfs-ganesha.org To unsubscribe

>> send an email to support-leave(a)lists.nfs-ganesha.org >> >> _______________________________________________ >> Support mailing list -- support(a)lists.nfs-ganesha.org To unsubscribe

>> send an email to support-leave(a)lists.nfs-ganesha.org >> > _______________________________________________ > Support mailing list -- support(a)lists.nfs-ganesha.org To unsubscribe > send an email to support-leave(a)lists.nfs-ganesha.org > > _______________________________________________ Support mailing list -- support(a)lists.nfs-ganesha.org To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org