On Thu, Jul 20, 2017 at 3:05 PM, <c.monty@xxxxxx> wrote:
Hello!
My understanding is that I create on (big) pool for all DB backups written to storage.
The clients have restricted access to a specific directory only, means they can mount only this directory.
Can I define a quota for a specific directory, or only for the pool?
You can define quotas per directory but there are a number of caveats with quotas: http://docs.ceph.com/docs/master/cephfs/quota/
And do I need to define the OSD Restriction?
I think you would still need to do this if you have other pools
"To prevent clients from writing or reading data to pools other than those in use for CephFS, set an OSD authentication capability that restricts access to the CephFS data pool(s)."
THX
20. Juli 2017 14:00, "David" <dclistslinux@xxxxxxxxx> schrieb:
I think the multiple namespace feature would be more appropriate for your use case. So that would be multiple file systems within the same pools rather than multiple pools in a single filesystem.
With that said, that might be overkill for your requirement. You might be able to achieve what you need with path restriction: http://docs.ceph.com/docs/master/cephfs/client-auth/ On Thu, Jul 20, 2017 at 10:23 AM, <c.monty@xxxxxx> wrote:
19. Juli 2017 17:34, "LOPEZ Jean-Charles" <jelopez@xxxxxxxxxx> schrieb:
> Hi,
>
> you must add the extra pools to your current file system configuration: ceph fs add_data_pool
> {fs_name} {pool_name}
>
> Once this is done, you just have to create some specific directory layout within CephFS to modify
> the name of the pool targetted by a specific directory. See
> http://docs.ceph.com/docs/master/cephfs/file-layouts
>
> Just set the ceph.dir.layout.pool attribute to the appropriate Pool ID of the new pool.
>
> Regards
> JC
>
>> On Jul 19, 2017, at 07:59, c.monty@xxxxxx wrote:
>>
>> Hello!
>>
>> I want to organize data in pools and therefore created additional pools:
>> ceph osd lspools
>> 0 rbd,1 templates,2 hdb-backup,3 cephfs_data,4 cephfs_metadata,
>>
>> As you can see, pools "cephfs_data" and "cephfs_metadata" belong to a Ceph filesystem.
>>
>> Question:
>> How can I write data to other pools, e.g. hdb-backup?
>>
>> THX
>> _______________________________________________
>> ceph-users mailing list
>> ceph-users@xxxxxxxxxxxxxx
>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Hello JC,
thanks for your reply.
I'm not sure why I should add pools to a current file system configuration.
Therefore it could be helpful to explain my use case.
The Ceph Storage Cluster should provide storage for database backups.
For security reasons I consider to create one pool per database identified by an unique id (e.g. ABC).
And for each pool only a dedicated user (+ ceph admin) can access (read / write) the data in the related pool;
this user is unique for each database (e.g. abcadm).
The first question is:
Do I need to create two RADOS pools as documented in guide 'Create a Ceph filesystem' (http://docs.ceph.com/docs/master/cephfs/createfs/ ) for each database id:
"A Ceph filesystem requires at least two RADOS pools, one for data and one for metadata."
If yes, this would mean to create the following pools:
$ ceph osd pool create abc_data <pg_num>
$ ceph osd pool create abc_metadata <pg_num>
$ ceph osd pool create xyz_data <pg_num>
$ ceph osd pool create xyz_metadata <pg_num>
Or should I create only one "File System Pool" (= cephfs_data and cephfs_metadata) and add all database pools to this file system?
In that case, how can I ensure that admin "abcadm" cannot modify files belonging to database XYZ?
THX
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph. com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
