All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Dor Laor <dor.laor@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org,
	Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: [PATCH] Add support for a	configuration file
Date: Wed, 14 May 2008 16:02:59 +0100	[thread overview]
Message-ID: <20080514150259.GG15783@redhat.com> (raw)
In-Reply-To: <1210776776.24261.814.camel@localhost.localdomain>

On Wed, May 14, 2008 at 05:52:56PM +0300, Dor Laor wrote:
> 
> On Wed, 2008-05-14 at 17:41 +0300, Avi Kivity wrote:
> > Daniel P. Berrange wrote:
> > > That's very nearly YAML format[1], which is attractive because parsers
> > > are available in every major programming language, and it is still
> > > pretty human friendly.
> > >
> > > So my preference would be to go with the last option and make sure
> > > it really is YAML compliant so people can use standard tools for 
> > > generating and parsing the format.
> > >   
> > 
> > Using a standard format has the added benefit that things like quoting 
> > are taken care of.
> > 
> > Filenames with leading and trailing spaces, anyone?  Embedded control 
> > characters?
> > 
> 
> Please don't jump over me but I think it is worth mentioning OVF, at
> least for to know what's you opinions.

OVF is insanely overcomplicated. It is also addressing a different problem
space, that of virtual machine applinance interchange / distribution. And 
it is a disgusting format for users to deal with. 

> Open Virtualization Format -
> http://www.vmware.com/appliances/learn/ovf.html
> 
> It's xml based, supported by all major hypervisors, so qemu/kvm/xen
> users might eventually use a product that support OVF.
> Since its a new format it is open for changes and has lots of
> flexibility. As a start we don't have to be completely compatible with
> it.

It is a 'open' format defined in secret invitation only cabal by
a bunch of proprietry software vendors. No thanks.

Dan.
-- 
|: Red Hat, Engineering, Boston   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Dor Laor <dor.laor@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: [kvm-devel] [PATCH] Add support for a	configuration file
Date: Wed, 14 May 2008 16:02:59 +0100	[thread overview]
Message-ID: <20080514150259.GG15783@redhat.com> (raw)
In-Reply-To: <1210776776.24261.814.camel@localhost.localdomain>

On Wed, May 14, 2008 at 05:52:56PM +0300, Dor Laor wrote:
> 
> On Wed, 2008-05-14 at 17:41 +0300, Avi Kivity wrote:
> > Daniel P. Berrange wrote:
> > > That's very nearly YAML format[1], which is attractive because parsers
> > > are available in every major programming language, and it is still
> > > pretty human friendly.
> > >
> > > So my preference would be to go with the last option and make sure
> > > it really is YAML compliant so people can use standard tools for 
> > > generating and parsing the format.
> > >   
> > 
> > Using a standard format has the added benefit that things like quoting 
> > are taken care of.
> > 
> > Filenames with leading and trailing spaces, anyone?  Embedded control 
> > characters?
> > 
> 
> Please don't jump over me but I think it is worth mentioning OVF, at
> least for to know what's you opinions.

OVF is insanely overcomplicated. It is also addressing a different problem
space, that of virtual machine applinance interchange / distribution. And 
it is a disgusting format for users to deal with. 

> Open Virtualization Format -
> http://www.vmware.com/appliances/learn/ovf.html
> 
> It's xml based, supported by all major hypervisors, so qemu/kvm/xen
> users might eventually use a product that support OVF.
> Since its a new format it is open for changes and has lots of
> flexibility. As a start we don't have to be completely compatible with
> it.

It is a 'open' format defined in secret invitation only cabal by
a bunch of proprietry software vendors. No thanks.

Dan.
-- 
|: Red Hat, Engineering, Boston   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2008-05-14 15:02 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 21:19 [PATCH] Add support for a configuration file Anthony Liguori
2008-05-13 21:19 ` [Qemu-devel] " Anthony Liguori
2008-05-13 23:07 ` Anthony Liguori
2008-05-13 23:07   ` [Qemu-devel] " Anthony Liguori
2008-05-13 23:20   ` Daniel P. Berrange
2008-05-13 23:20     ` [Qemu-devel] Re: [kvm-devel] " Daniel P. Berrange
2008-05-14  6:35     ` Colin Adams
2008-05-14  6:35       ` [Qemu-devel] Re: [kvm-devel] " Colin Adams
2008-05-14 14:41     ` [Qemu-devel] " Avi Kivity
2008-05-14 14:41       ` [Qemu-devel] Re: [kvm-devel] " Avi Kivity
2008-05-14 14:52       ` [Qemu-devel] " Dor Laor
2008-05-14 14:52         ` [Qemu-devel] Re: [kvm-devel] " Dor Laor
2008-05-14 15:02         ` Daniel P. Berrange [this message]
2008-05-14 15:02           ` Daniel P. Berrange
2008-05-14 15:18         ` [Qemu-devel] " Anthony Liguori
2008-05-14 15:18           ` [kvm-devel] " Anthony Liguori
2008-05-14 14:59       ` Anthony Liguori
2008-05-14 14:59         ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2008-05-14 15:10       ` Andreas Färber
2008-05-15 14:50         ` Ian Jackson
2008-05-14  8:27   ` [Qemu-devel] " Fabrice Bellard
2008-05-14  8:27     ` Fabrice Bellard
2008-05-14 10:31     ` Avi Kivity
2008-05-14 10:31       ` Avi Kivity
2008-05-14 12:26       ` Fabrice Bellard
2008-05-14 12:26         ` Fabrice Bellard
2008-05-14 13:31         ` Daniel P. Berrange
2008-05-14 13:31           ` [kvm-devel] " Daniel P. Berrange
2008-05-15  8:04           ` Avi Kivity
2008-05-15  8:04             ` [kvm-devel] " Avi Kivity
2008-05-15 11:52             ` Daniel P. Berrange
2008-05-15 11:52               ` [kvm-devel] " Daniel P. Berrange
2008-05-15 12:04               ` Avi Kivity
2008-05-15 12:04                 ` [kvm-devel] " Avi Kivity
2008-05-15 12:16                 ` Andreas Färber
2008-05-15 12:20                 ` Laurent Vivier
2008-05-15 12:20                   ` [kvm-devel] " Laurent Vivier
2008-05-14 14:06         ` Anthony Liguori
2008-05-14 14:06           ` Anthony Liguori
2008-05-14 14:26         ` Paul Brook
2008-05-14 14:26           ` Paul Brook
2008-05-14 14:45           ` Javier Guerra
2008-05-14 14:45             ` [kvm-devel] " Javier Guerra
2008-05-14 15:13             ` Johannes Schindelin
2008-05-14 15:13               ` [kvm-devel] " Johannes Schindelin
2008-05-14 15:30               ` [kvm-devel] " Javier Guerra
2008-05-14 15:30                 ` [kvm-devel] [Qemu-devel] " Javier Guerra
2008-05-14 15:37                 ` [kvm-devel] " Johannes Schindelin
2008-05-14 15:37                   ` [kvm-devel] [Qemu-devel] " Johannes Schindelin
2008-05-14 15:42                   ` [kvm-devel] " Javier Guerra
2008-05-14 15:42                     ` [kvm-devel] [Qemu-devel] " Javier Guerra
2008-05-14 16:07                   ` Kelly French
2008-05-14 16:07                     ` [kvm-devel] " Kelly French
2008-05-15 14:59                     ` Paul Brook
2008-05-15 14:59                       ` [kvm-devel] " Paul Brook
2008-05-14 16:01                 ` Andreas Färber
2008-05-14 16:21                   ` Daniel P. Berrange
2008-05-14 16:37                     ` Andreas Färber
2008-05-14 16:29               ` Fabrice Bellard
2008-05-17 21:49                 ` Luca Barbato
2008-05-14 15:22             ` [kvm-devel] " Daniel P. Berrange
2008-05-14 15:22               ` [kvm-devel] [Qemu-devel] " Daniel P. Berrange
2008-05-14 15:09           ` Anthony Liguori
2008-05-14 15:09             ` Anthony Liguori
2008-05-14 15:18             ` Paul Brook
2008-05-14 15:18               ` [Qemu-devel] " Paul Brook
2008-05-14 16:25           ` Fabrice Bellard
2008-05-14 16:25             ` [Qemu-devel] " Fabrice Bellard
2008-05-14 14:36   ` andrzej zaborowski
2008-05-14 14:36     ` andrzej zaborowski
2008-05-14 15:10     ` Johannes Schindelin
2008-05-14 15:10       ` Johannes Schindelin
2008-05-15 14:58     ` Ian Jackson
2008-05-15 14:58       ` Ian Jackson
2008-05-15 12:03 ` [Qemu-devel] " Erik de Castro Lopo
2008-05-15 12:36   ` andrzej zaborowski
2008-05-15 13:22     ` Daniel P. Berrange
2008-05-15 14:46       ` andrzej zaborowski
2008-05-15 15:05   ` Anthony Liguori
2008-05-15 15:26     ` Avi Kivity
2008-05-15 18:50       ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2008-05-14 10:03 [Qemu-devel] " Balazs Attila-Mihaly (Cd-MaN)

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=20080514150259.GG15783@redhat.com \
    --to=berrange@redhat.com \
    --cc=dor.laor@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=paul@codesourcery.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.