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/
Home Products Support Community News


[Xen-devel] [RFC] Switching store to use domain id's for keys

To: Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [RFC] Switching store to use domain id's for keys
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Tue, 30 Aug 2005 15:32:46 -0500
Delivery-date: Tue, 30 Aug 2005 20:31:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
Hey guys,

As I go through the console code, I notice that the domain console information is being stored in /console/%d/domain instead of within the /domain tree as one would expect.

The reasoning seems obvious to me, there's no easy way to get the UUID for a domain so constructing a UUID based path outside of Xend is very difficult.

Perhaps now is a good time to reconsider just using domain ids instead of UUIDs for the paths? In a cluster we could just use <nodeid>/domain/<domid> for unique identification.

Or, if we really want to use UUIDs in the node path, perhaps we can add UUIDs to the domain structure in the hypervisor so that we can actually query it through getdomaininfo?


Anthony Liguori

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>