From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JwIXy-00050k-AD for qemu-devel@nongnu.org; Wed, 14 May 2008 11:05:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JwIXx-0004z8-CM for qemu-devel@nongnu.org; Wed, 14 May 2008 11:05:37 -0400 Received: from [199.232.76.173] (port=37233 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JwIXx-0004yu-4l for qemu-devel@nongnu.org; Wed, 14 May 2008 11:05:37 -0400 Received: from mx1.redhat.com ([66.187.233.31]:35045) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JwIXw-000191-TF for qemu-devel@nongnu.org; Wed, 14 May 2008 11:05:37 -0400 Date: Wed, 14 May 2008 16:02:59 +0100 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] Re: [kvm-devel] [PATCH] Add support for a configuration file Message-ID: <20080514150259.GG15783@redhat.com> References: <1210713545-11916-1-git-send-email-aliguori@us.ibm.com> <482A1F1C.2020902@codemonkey.ws> <20080513232021.GA8844@redhat.com> <482AFA1C.3030800@qumranet.com> <1210776776.24261.814.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1210776776.24261.814.camel@localhost.localdomain> Reply-To: "Daniel P. Berrange" , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Dor Laor Cc: kvm-devel@lists.sourceforge.net, Anthony Liguori , qemu-devel@nongnu.org, Paul Brook 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 :|