WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xenstore documentation

To: NAHieu <nahieu@xxxxxxxxx>
Subject: Re: [Xen-devel] xenstore documentation
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Tue, 04 Oct 2005 12:42:49 -0500
Cc: Jacob Gorm Hansen <jacobg@xxxxxxx>, harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Rami Rosen <rosenrami@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, rolf.neugebauer@xxxxxxxxx
Delivery-date: Tue, 04 Oct 2005 17:40:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5d7aca950510041024l7d82d7d7h536e0e3aa0ff8728@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <e08041f30510031003p6c4911b8n22dbf10bd1a1997f@xxxxxxxxxxxxxx> <ae5426fb0510032327r4589aaerc4d279825dca0ad8@xxxxxxxxxxxxxx> <e08041f30510040520g53e96456xa7d93168fa8cdf90@xxxxxxxxxxxxxx> <1128429737.30221.12.camel@xxxxxxxxxxxxxxxxxxxxx> <5d7aca950510040555k19e8fb71kb74deff11c344451@xxxxxxxxxxxxxx> <1128432335.30221.33.camel@xxxxxxxxxxxxxxxxxxxxx> <1128436946.29007.6.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5d7aca950510041024l7d82d7d7h536e0e3aa0ff8728@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050912)
NAHieu wrote:

or no ;) depending on what you want to do. so for example if you only
ever have one backend in the system then you "could" store that under a
well known name in the store and the frontends can simply read that.
you'll also need a place for the BE to watch for FE updates in a similar
fashion.


Rolf, I am really suprised here: how can BE watch for FE updates? BE
and FE are in different domain, so they cannot access each other
xenstore tree. (??)
Yes they can. Permissions are currently off so technically any domain can access any other domains tree.

When permissions are enabled, the backends will have at least read permission on all the frontend domains.

Regards,

Anthony Liguori

So exactly what did you mean?

Thanks.
Hieu

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel