[ceph-users] rados-java issue tracking and release
hi, does anyone know who is maintaining rados-java and perform release to the Maven central? In May, there was a release to Maven central *[1], but the release version is not based on the latest code base from: https://github.com/ceph/rados-java I wonder if the one who do the Maven release could tag a version and release the current snapshot. Besides, I am not sure if the rados-java developers will notice any issue reported in the ceph issue tracker. would it be better if the rados-java project could enable issue tracking at github? thx [1] http://search.maven.org/#artifactdetails%7Ccom.ceph%7Crados%7C0.1.4%7Cjar regards, mingfai ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
[ceph-users] keyvaluestore upgrade from v0.87 to v0.94.1
hi, I have a ceph cluster that use keyvaluestore-dev. After upgraded from v0.87 to v0.94.1, and changed the configuration (removed -dev suffix and added enable experimental ...), OSD is still fail to start, with the following error: 7fb8b06ce900 -1 osd.0 0 OSD::init() : unable to read osd superblock 7fb8b06ce900 -1 ** ERROR: osd init failed: (22) Invalid argument any idea if such upgrade is supported? how can I troubleshoot the problem? thx regards, mingfai ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] keyvaluestore upgrade from v0.87 to v0.94.1
thx for your info. My installation was upgraded with ceph-deploy install --release hammer HOST, and it can't be downgrade with --release giant as stated clearly in a warning message in the doc saying Important Once you upgrade a daemon, you cannot downgrade it.. I plan to do a clean installation of the old 0.87 version to recover my data, with the old keyring and conf. Any important thing to note for this kind of data recovery work? thx regards, mingfai On Sat, May 23, 2015 at 10:59 AM, Haomai Wang haomaiw...@gmail.com wrote: Experimental feature like keyvaluestore won't support upgrade from 0.87 to 0.94. Sorry On Sat, May 23, 2015 at 7:35 AM, Mingfai mingfai...@gmail.com wrote: hi, I have a ceph cluster that use keyvaluestore-dev. After upgraded from v0.87 to v0.94.1, and changed the configuration (removed -dev suffix and added enable experimental ...), OSD is still fail to start, with the following error: 7fb8b06ce900 -1 osd.0 0 OSD::init() : unable to read osd superblock 7fb8b06ce900 -1 ** ERROR: osd init failed: (22) Invalid argument any idea if such upgrade is supported? how can I troubleshoot the problem? thx regards, mingfai ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com -- Best Regards, Wheat ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
[ceph-users] does ceph auth caps support multiple pools?
hi, Is it possible to specify multiple pool names for authorization? in my test, only the following are allowed, ceph auth caps client.CLIENT_ID osd 'allow *' ceph auth caps client.CLIENT_ID osd 'allow * pool=*' Let's say I want to grant access to a-1 and a-2 but not any other pools, it doesn't support styles such as: #use comma ceph auth caps client.CLIENT_ID osd 'allow * pool=a-1,a-2' #use asterisk ceph auth caps client.CLIENT_ID osd 'allow * pool=a-*' #specific multiple pools ceph auth caps client.CLIENT_ID osd 'allow * pool=a-1 pool=a-2' #use multiple osd caps ceph auth caps client.CLIENT_ID osd 'allow * pool=a-1' osd 'allow * pool=a-2' any idea? p.s. I checked the doc as well as tried different combination http://ceph.com/docs/master/rados/operations/user-management/ regards, mingfai ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
