From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zhigang Wang Subject: Re: [PATCH 6 of 8] xl: add a global configuration file Date: Tue, 31 Aug 2010 14:52:30 -0400 Message-ID: <4C7D4F6E.9070409@oracle.com> References: <4C782E89.5070902@oracle.com> <19581.15544.444760.592141@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19581.15544.444760.592141@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org > Stefano Stabellini writes ("Re: [Xen-devel] [PATCH 6 of 8] xl: add a global configuration file"): >> I agree with you on not wanting to see xl becoming heavy, however there >> are few global configuration options that would be too burdensome >> for the user to specify every single time, in particular I am referring >> to the autoballoning operation. > That's one example. Another is the default network bridge: it makes > sense to put that in a global config file as it makes domain config > files more portable between different setups. > > Ian. > That's OK. Then we should guarantee: a configure can only specified in the global configure file or on the command line. But not both. Here is a very bad example (not exist) we should avoid: global.conf: migrate_ssl = true/false # xl migrate --ssl .... Thanks, Zhigang