From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:45041) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UeqaC-0004A4-CO for qemu-devel@nongnu.org; Tue, 21 May 2013 13:42:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ueqa5-0000T4-OK for qemu-devel@nongnu.org; Tue, 21 May 2013 13:42:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:10763) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ueqa5-0000Su-GJ for qemu-devel@nongnu.org; Tue, 21 May 2013 13:42:37 -0400 Date: Tue, 21 May 2013 18:42:25 +0100 From: "Daniel P. Berrange" Message-ID: <20130521174225.GV31290@redhat.com> References: <519B2E24.40104@gmail.com> <20130521083953.GB31290@redhat.com> <20130521095527.GB29303@iris.ozlabs.ibm.com> <20130521100136.GE31290@redhat.com> <871u90z3mk.fsf@codemonkey.ws> <519BAAFA.6030101@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <519BAAFA.6030101@redhat.com> Subject: Re: [Qemu-devel] [libvirt] [qemu-devel] Default machine type setting for ppc64 Reply-To: "Daniel P. Berrange" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: Peter Maydell , libvir-list@redhat.com, "qemu-devel@nongnu.org" , Anthony Liguori , Paul Mackerras , Pradipta Kumar Banerjee On Tue, May 21, 2013 at 11:12:26AM -0600, Eric Blake wrote: > On 05/21/2013 10:42 AM, Anthony Liguori wrote: > > Perhaps the right thing to do for OpenStack is to allow for a user > > specified configuration file to select things like the default hardware > > models/machine types? Then this could become node configuration instead > > of dynamic configuration. > > > > I think it could be useful for general users too. Every domain requires > > a lot of the same boiler plate bits. I think a lot of configurations > > would benefit from being able to set global domain options. > > I have also argued in the past that it would be useful for libvirt to > support the idea of a template, where you can specify a domain XML that > inherits defaults from the template. We've already done things like > this for networking, nwfilter, and even secret management (in domain > XML, you declare that you are using a named network object, and that > network object serves as the template instead of you having to hard-code > all the elements into your domain XML), so we have a design to base it > on. But until someone adds such a feature for libvirt, then OpenStack > should be passing explicit XML to libvirt, and tracking defaults at the > OpenStack layer. I don't think the idea of a template belongs in libvirt. Creating basic XML structure with relevant defaults pre-filled for a particular usecase is something that the libvirt-designer library is aiming to take care of for applications. 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 :|