Re: CephFS in existing pool namespace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Nov 2, 2016 at 9:10 PM, Dan Jakubiec <dan.jakubiec@xxxxxxxxx> wrote:
> Hi John,
>
> How does one configure namespaces for file/dir layouts?  I'm looking here,
> but am not seeing any mentions of namespaces:
>
>   http://docs.ceph.com/docs/jewel/cephfs/file-layouts/

The field is called "pool_namespace" (set it the same way as "pool").

I've written a patch to add it to the master documentation at [1] and
also added a neater way to clear it which I noticed we didn't have
when playing with it.

Cheers,
John

1. https://github.com/ceph/ceph/pull/11783


> Thanks,
>
> -- Dan
>
> On Oct 28, 2016, at 04:11, John Spray <jspray@xxxxxxxxxx> wrote:
>
> On Thu, Oct 27, 2016 at 9:43 PM, Reed Dier <reed.dier@xxxxxxxxxxx> wrote:
>
> Looking to add CephFS into our Ceph cluster (10.2.3), and trying to plan for
> that addition.
>
> Currently only using RADOS on a single replicated, non-EC, pool, no RBD or
> RGW, and segmenting logically in namespaces.
>
> No auth scoping at this time, but likely something we will be moving to in
> the future as our Ceph cluster grows in size and use.
>
> The main question at hand is bringing CephFS, by way of the kernel driver,
> into our cluster. We are trying to be more efficient with our PG
> enumeration, and questioning whether there is efficiency or unwanted
> complexity by way of creating a namespace in the existing pool, versus a
> completely separate pool.
>
> On top of that, how does the cephfs-metadata pool/namespace equate into
> that? Is this even feasible?
>
> Barring feasibility, how do others plan their pg_num for separate pools for
> cephfs and the metadata pool, compared to a standard object pool?
>
> Hopefully someone has some experience with this and can comment.
>
> TL;DR - is there a way to specify cephfs_data and cephfs_metadata ‘pools’ as
> a namespace, rather than entire pools?
>        $ ceph fs new <fs_name> <metadata pool> <data pool>
> --metadata-namespace <ns1> --data-namespace <ns2>
>        <metadata pool> is the name of the pool where metadata is stored,
> <ns1> the namespace within the aforementioned pool.
>        <data pool> and <ns2> analogous with the metadata side.
>
>
> Currently, you can set a namespace on a file/dir layout which will
> control where the file data goes, but the MDS will still put some
> things outside of that namespace.
>
> The feature ticket for putting everything into namespaces is this one:
> http://tracker.ceph.com/issues/15066
>
> It's one of the simpler things in the backlog so if anyone wants a
> project then it's a good one.
>
> Cheers,
> John
> _______________________________________________
> 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




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux