[openstack-dev] RFC: Classnames in config parameters harmful to users / upgrades

Daniel P. Berrange berrange at redhat.com
Thu Feb 7 12:23:47 UTC 2013


On Wed, Feb 06, 2013 at 04:10:23PM -0500, Doug Hellmann wrote:
> On Wed, Feb 6, 2013 at 11:10 AM, Daniel P. Berrange <berrange at redhat.com>wrote:
> 
> > On Wed, Feb 06, 2013 at 10:46:52AM -0500, Mark McLoughlin wrote:
> > > On Wed, 2013-02-06 at 15:22 +0000, Daniel P. Berrange wrote:
> > > > The only way we can do this is if we do *NOT* require the use of
> > > > classnames in config parameters. Instead we should treat all these
> > > > config parameters as being more like enumerations, and map those to
> > > > classnames internally
> > > >
> > > > eg for the compute_driver instead of having the user set
> > > >
> > > >   compute_driver=nova.virt.libvirt.LibvirtDriver
> > > >
> > > > they would do
> > > >
> > > >   compute_driver=libvirt
> > >
> > > I think there's already good consensus on this and the idea is to use
> > > entry points and stevedore to achieve it.
> > >
> > > See:
> > >
> > >   https://blueprints.launchpad.net/nova/+spec/entrypoints-plugins
> > >   https://review.openstack.org/11027
> > >   https://review.openstack.org/15030
> >
> > Heh, I've even seen that blueprint before, but it was hard to understand
> > just what it was on about. A etherpad transcript of a conversation that
> > you weren't present for, doesn't make a nice design doc for blueprint :-(
> >
> 
> You did a great job of summarizing the issue. Could you find a way to add
> that information to the blueprint? Maybe start a wiki page to replace the
> etherpad, include your summary and the link to the etherpad?

Good idea, I'll see about doing that.

Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|



More information about the OpenStack-dev mailing list