This is something we have talked about in the past -- and I think it would be a good addition. The caveat is that if we would now have config-level, per-pool level, per-image level (via rbd image-meta), and command-line/environment variable configuration overrides. I think there needs to be clear tooling in the rbd CLI to dump RBD configuration overrides and the source of those overrides -- and it needs to be well documented. On Mon, Mar 27, 2017 at 9:31 AM, Dongsheng Yang <dongsheng.yang@xxxxxxxxxxxx> wrote: > Jason, > do you think it's good idea to introduce a rbd_config object to > record some configurations of per-pool, such as default_features. > > That means, we can set some configurations differently in different > pool. In this way, we can also handle the per-pool setting in rbd-mirror. > > Thanx > Yang > > > On 27/03/2017, 21:20, Jason Dillaman wrote: >> >> On Mon, Mar 27, 2017 at 4:00 AM, Dongsheng Yang >> <dongsheng.yang@xxxxxxxxxxxx> wrote: >>> >>> Hi Fulvio, >>> >>> On 03/24/2017 07:19 PM, Fulvio Galeazzi wrote: >>> >>> Hallo, apologies for my (silly) questions, I did try to find some doc on >>> rbd-mirror but was unable to, apart from a number of pages explaining how >>> to >>> install it. >>> >>> My environment is CenOS7 and Ceph 10.2.5. >>> >>> Can anyone help me understand a few minor things: >>> >>> - is there a cleaner way to configure the user which will be used for >>> rbd-mirror, other than editing the ExecStart in file >>> /usr/lib/systemd/system/ceph-rbd-mirror@.service ? >>> For example some line in ceph.conf... looks like the username >>> defaults to the cluster name, am I right? >>> >>> >>> It should just be "ceph", no matter what the cluster name is, if I read >>> the >>> code correctly. >> >> The user id is passed in via the systemd instance name. For example, >> if you wanted to use the "mirror" user id to connect to the local >> cluster, you would run "systemctl enable ceph-rbd-mirror@mirror". >> >>> - is it possible to throttle mirroring? Sure, it's a crazy thing to do >>> for "cinder" pools, but may make sense for slowly changing ones, like >>> a "glance" pool. >>> >>> >>> The rbd core team is working on this. Jason, right? >> >> This is in our backlog of desired items for the rbd-mirror daemon. >> Having different settings for different pools was not in our original >> plan, but this is something that also came up during the Vault >> conference last week. I've added an additional backlog item to cover >> per-pool settings. >> >>> - is it possible to set per-pool default features? I read about >>> "rbd default features = ###" >>> but this is a global setting. (Ok, I can still restrict pools to be >>> mirrored with "ceph auth" for the user doing mirroring) >>> >>> >>> "per-pool default features" sounds like a reasonable feature request. >>> >>> About the "ceph auth" for mirroring, I am working on a rbd acl design, >>> will consider pool-level, namespace-level and image-level. Then I think >>> we can do a permission check on this. >> >> Right now, the best way to achieve that is by using different configs >> / user ids for different services. For example, if OpenStack glance >> used "glance" and cinder user "cinder", the ceph.conf's >> "[client.glance]" section could have different default features as >> compared to a "[client.cinder]" section. >> >>> Thanx >>> Yang >>> >>> >>> >>> Thanks! >>> >>> Fulvio >>> >>> >>> >>> _______________________________________________ >>> 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
 |