<br><br><div class="gmail_quote">On Wed, Feb 6, 2013 at 11:10 AM, Daniel P. Berrange <span dir="ltr"><<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Wed, Feb 06, 2013 at 10:46:52AM -0500, Mark McLoughlin wrote:<br>
> On Wed, 2013-02-06 at 15:22 +0000, Daniel P. Berrange wrote:<br>
> > The only way we can do this is if we do *NOT* require the use of<br>
> > classnames in config parameters. Instead we should treat all these<br>
> > config parameters as being more like enumerations, and map those to<br>
> > classnames internally<br>
> ><br>
> > eg for the compute_driver instead of having the user set<br>
> ><br>
> > compute_driver=nova.virt.libvirt.LibvirtDriver<br>
> ><br>
> > they would do<br>
> ><br>
> > compute_driver=libvirt<br>
><br>
> I think there's already good consensus on this and the idea is to use<br>
> entry points and stevedore to achieve it.<br>
><br>
> See:<br>
><br>
> <a href="https://blueprints.launchpad.net/nova/+spec/entrypoints-plugins" target="_blank">https://blueprints.launchpad.net/nova/+spec/entrypoints-plugins</a><br>
> <a href="https://review.openstack.org/11027" target="_blank">https://review.openstack.org/11027</a><br>
> <a href="https://review.openstack.org/15030" target="_blank">https://review.openstack.org/15030</a><br>
<br>
</div>Heh, I've even seen that blueprint before, but it was hard to understand<br>
just what it was on about. A etherpad transcript of a conversation that<br>
you weren't present for, doesn't make a nice design doc for blueprint :-(<br></blockquote><div><br></div><div>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?</div>
<div><br></div><div>Doug</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> The end result is exactly that<br>
><br>
> compute_driver=libvirt<br>
><br>
> will work, along with backwards compat for the original name.<br>
><br>
> It just needs to be resurrected and finished off.<br>
<br>
</div>Indeed, it looks like that is definitely something to have as a<br>
priority item. Even if those patches were resurrected it looks<br>
like quite alot more work is needed, give that they only tackle<br>
3 out of 44+ config parameters!<br>
<br>
Do we have any official position on config file upgrade support<br>
at this time ? It would be helpful to reviewers if they could<br>
clearly identify whether a proposed config change is acceptable<br>
or not from an upgrade POV, since currently people are holding<br>
different changes to different standards before approval<br>
<span class="HOEnZb"><font color="#888888"><br>
Daniel<br>
</font></span><div class="im HOEnZb">--<br>
|: <a href="http://berrange.com" target="_blank">http://berrange.com</a> -o- <a href="http://www.flickr.com/photos/dberrange/" target="_blank">http://www.flickr.com/photos/dberrange/</a> :|<br>
|: <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> -o- <a href="http://virt-manager.org" target="_blank">http://virt-manager.org</a> :|<br>
|: <a href="http://autobuild.org" target="_blank">http://autobuild.org</a> -o- <a href="http://search.cpan.org/~danberr/" target="_blank">http://search.cpan.org/~danberr/</a> :|<br>
|: <a href="http://entangle-photo.org" target="_blank">http://entangle-photo.org</a> -o- <a href="http://live.gnome.org/gtk-vnc" target="_blank">http://live.gnome.org/gtk-vnc</a> :|<br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br>