The most realistic backlog feature would be for adding support for namespaces within RBD [1], but it's not being actively developed at the moment. Of course, the usual caveat that "everyone with access to the cluster network would be trusted" would still apply. It's because of that assumption that adding support for RBD namespaces hasn't really bubbled up the priority list in all honesty. [1] https://trello.com/c/UafuAuEV On Thu, Oct 19, 2017 at 4:16 PM, Jorge Pinilla López <jorpilo@xxxxxxxxx> wrote: > I want to give permissions to my clients but only for reading/writting an > specific RBD image not the hole pool. > > If I give permissions to the hole pool, a client could delete all the images > in the pool or mount any other image and I don't really want that. > > I've read about using prefix > (https://blog-fromsomedude.rhcloud.com/2016/04/26/Allowing-a-RBD-client-to-map-only-one-RBD/) > > But I wounder if is there any future plan to support an easier client > rbd-image permissions? > > ________________________________ > Jorge Pinilla López > jorpilo@xxxxxxxxx > Estudiante de ingenieria informática > Becario del area de sistemas (SICUZ) > Universidad de Zaragoza > PGP-KeyID: A34331932EBC715A > ________________________________ > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- Jason _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |