[openstack-dev] Novaclient and Extensions

Craig Vyvial cp16net at gmail.com
Tue Dec 18 19:14:51 UTC 2012


Ok i agree that the user should only have to know 1 thing. The entry point.

Then the discovery of extensions by the client should be api driven by the
cloud entry point.


On Tue, Dec 18, 2012 at 6:03 AM, Christopher Yeoh <cyeoh at au1.ibm.com> wrote:

> On Mon, 17 Dec 2012 22:37:50 -0800
> Monty Taylor <mordred at inaugust.com> wrote:
>
> > On 12/17/2012 10:20 PM, Craig Vyvial 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.
> >
> > Obviously, I agree with Vish here ... but I think that one of the
> > places where you and I may be missing each other is in who the
> > audience is we are talking about.
> >
> > When you say "if you want to install..." that implies a level of
> > agency or understanding that I do not think we should expect from a
> > public cloud user. Why would I, as a consumer of an OpenStack based
> > public cloud ever "want" to install a novaclient extension module?
> > How would I even know I want to do that?
>
> +1
>
> Most users would not know that they have to install an extension
> and just finding out which extensions they should install would be
> difficult for new and inexperienced users. They'd probably just assume
> that the functionality they want is not available.
>
> So I agree we want the client to automatically detect what
> extension capabilities can be used. Perhaps even an easy way for them
> to see what functionality they could have from nova client if the
> corresponding server side support was installed.
>
> Chris
> --
> cyeoh at au.ibm.com
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121218/1f1bfd81/attachment.html>


More information about the OpenStack-dev mailing list