From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
libvir-list@redhat.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Paul Mackerras <paulus@au1.ibm.com>,
Pradipta Kumar Banerjee <bpradip@in.ibm.com>
Subject: Re: [Qemu-devel] [libvirt] [qemu-devel] Default machine type setting for ppc64
Date: Tue, 21 May 2013 18:42:25 +0100 [thread overview]
Message-ID: <20130521174225.GV31290@redhat.com> (raw)
In-Reply-To: <519BAAFA.6030101@redhat.com>
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 :|
next prev parent reply other threads:[~2013-05-21 17:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 8:19 [Qemu-devel] [qemu-devel][libvirt] Default machine type setting for ppc64 Li Zhang
2013-05-21 8:24 ` [Qemu-devel] [libvirt] " Li Zhang
2013-05-21 8:31 ` [Qemu-devel] [qemu-devel][libvirt] " Peter Maydell
2013-05-21 8:39 ` Daniel P. Berrange
2013-05-21 8:45 ` Peter Maydell
2013-05-21 9:02 ` Li Zhang
2013-05-21 9:24 ` Peter Maydell
2013-05-21 9:25 ` Daniel P. Berrange
2013-05-21 15:00 ` Li Zhang
2013-05-21 9:55 ` Paul Mackerras
2013-05-21 10:01 ` Daniel P. Berrange
2013-05-21 10:22 ` Peter Maydell
2013-05-21 12:04 ` Anthony Liguori
2013-05-21 12:15 ` Peter Maydell
2013-05-21 14:40 ` Christian Borntraeger
2013-05-21 16:42 ` Anthony Liguori
2013-05-21 17:12 ` [Qemu-devel] [libvirt] [qemu-devel] " Eric Blake
2013-05-21 17:42 ` Daniel P. Berrange [this message]
2013-05-21 20:01 ` Anthony Liguori
2013-05-22 15:26 ` Li Zhang
2013-05-21 15:17 ` [Qemu-devel] [qemu-devel][libvirt] " Li Zhang
2013-05-21 8:45 ` Li Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130521174225.GV31290@redhat.com \
--to=berrange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=bpradip@in.ibm.com \
--cc=eblake@redhat.com \
--cc=libvir-list@redhat.com \
--cc=paulus@au1.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).