Open Stack

On Tue, Dec 18, 2012 at 7:20 PM, Craig Vyvial <cp16net at gmail.com> wrote:
> I do not think making the client "smart" enough to be able to tell which
> extensions are available is the right approach. It seems like overkill for
> the client's responsibility.
>
> I maybe reading in to this to far but it seems like if you want to install
> or enable an extension you should have to install to enable it... aka
> install python-novaclient-security-groups.
> Then each extension can be updated maintained separately.
>
> But i guess the main draw back I see with this is that then its a pain to
> "test" this functionality between extensions and core code.
> But I am sure people/companies have their own custom extensions that have
> never made it into the core code or never will have already felt some of
> these pains.
>
> -Craig V

In bzr we made nearly all extensions live outside the core tree.
Install-to-use was the approach, and looking back, we delivered a
fairly poor experience on that side. The plugin system was good and
easy to use, but releases usually had some friction, and users /never/
knew that their experience could be much better if they installed
plugin X.

As Openstack has a server-side facility with its extensions, that
makes the problem of discovery easier, but the issue of installation
no better, and thats a big chunk of the user story.

-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Cloud Services