Open Stack

What about using a combination of two word names, and generic names. For
example, you might have

    cinder-blockstorage

and

    foo-blockstorage

The advantage there is that we don't need to do the thesaurus.com thing,
but also, it enables to specify just

    blockstorage

via a registry.  The advantage of THAT is that if a user wants to change
out the "default" blockstorage engine (for example) we could provide them
with a way to do that.  The non-default would have to support the same API,
of course, but it definitely fits with the "pluggable" nature of OpenStack.

----  Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160204/e62e27a5/attachment.html>