[openstack-dev] [keystone] driver/pluggable base classes and ABCMeta

Julien Danjou julien at danjou.info
Thu Aug 22 13:19:10 UTC 2013

On Thu, Aug 22 2013, Morgan Fainberg wrote:

> In short, the drivers should probably be actual abstract classes, since
> that is what they effectively are.  I've seen this functionality used in
> both Neutron and Ironic.  I could see it providing some benefits from it in
> Keystone.  I wanted to get the general feeling from the Mailing List on
> using abstracted base classes in lieu of our current implementation prior
> to proposing a Blueprint, etc.  I don't see this as a Havana implementation
> but possibly something to consider for Icehouse.
> I don't know if the benefits really would bring us a huge win in Keystone,
> but I think it would make understanding what should be implemented when
> subclassing for driver development (and similar pluggable systems) a bit
> more clear.

We already rely on ABC heavily in Ceilometer, and we found it quite
useful. Definitely a good move I'd say.

Julien Danjou
// Free Software hacker / independent consultant
// http://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130822/db651b9c/attachment.pgp>

More information about the OpenStack-dev mailing list