>> ok, I don't know where I read the -o option to write the key but the file >> was empty I do a ">" and seems to work to list or create rbd now. >> >> and for what I have tested then, the good syntax is « mon 'profile rbd' osd >> 'profile rbd pool=rbd' » >> >>> In the case we give access to those rbd inside the container, how I can be >>> sure users in each container do not have access to others rbd ? Is >>> the namespace good to isolate each user ? >> >> The question about namespace is still open, if I have a namespace in the osd >> caps, I can't create rbd volume. How I can isolate each client to >> only his own volumes ? > > Unfortunately, RBD doesn't currently support namespaces, but it's on > our backlog.
So if I want to separate data between each container, I need to create a pool per user (one user can have multiple containers). I'm gonna give a look to cephfs, it seems possible to allow access only to a subdirectory per user, could you confirm it ? Thanks, Best regards, -- Yoann Moulin EPFL IC-IT _______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
