Re: RGW blueprint for plugin architecture

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

 



Hi,

I started out by defining the plugin system a bit more
(http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rgw:_plugin_architecture).
I'd really appreciate any comments.

On Wed, Aug 14, 2013 at 8:40 PM, Yehuda Sadeh <yehuda@xxxxxxxxxxx> wrote:
>>  - "AUTH" (Authentication backends): Rados/internal, Keystone
>
> That's probably the best place to start.

I also started working on an "auth" type of plugin for all Keystone
support based on the plugin system currently described in the
blueprint (it's an extremely simple and flexible system and IMHO a
good way to start). Contrary to the "plugin system", the auth plugin
itself will move a lot of code around and will therefore have a much
greater impact. So it's probably better to separate these projects
completely. If we can reach consensus about the way the first version
of the plugin system should look like, I will separate these commits
into different branches so we can merge it one step at a time.

Roald
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux