All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 6 of 8] xl: add a global configuration file
Date: Tue, 31 Aug 2010 14:52:30 -0400	[thread overview]
Message-ID: <4C7D4F6E.9070409@oracle.com> (raw)
In-Reply-To: <19581.15544.444760.592141@mariner.uk.xensource.com>


> 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

  reply	other threads:[~2010-08-31 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 11:19 [PATCH 6 of 8] xl: add a global configuration file Stefano Stabellini
2010-08-27 11:34 ` Christoph Egger
2010-08-27 11:42   ` Stefano Stabellini
2010-08-27 21:30 ` Zhigang Wang
2010-08-30  9:48   ` Stefano Stabellini
2010-08-31 17:32     ` Ian Jackson
2010-08-31 18:52       ` Zhigang Wang [this message]
2010-08-31 17:31 ` Ian Jackson

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=4C7D4F6E.9070409@oracle.com \
    --to=zhigang.x.wang@oracle.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.