All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>,
	Rusty Russell <rusty@rustcorp.com.au>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: [RFC] Switching store to use domain id's for keys
Date: Tue, 30 Aug 2005 15:32:46 -0500	[thread overview]
Message-ID: <4314C26E.9020408@us.ibm.com> (raw)

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?

Regards,

Anthony Liguori

             reply	other threads:[~2005-08-30 20:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 20:32 Anthony Liguori [this message]
2005-08-31  9:28 ` [RFC] Switching store to use domain id's for keys Christian Limpach
2005-08-31 20:40   ` Anthony Liguori
2005-09-05  0:11   ` Rusty Russell
2005-09-05  0:26     ` Steven Hand
2005-09-05  1:05       ` Rusty Russell
2005-09-05  1:43         ` Steven Hand
2005-09-05  2:53           ` Rusty Russell
2005-09-05  8:35             ` Steven Hand
2005-09-05  8:52               ` Keir Fraser
2005-09-06  0:07               ` Rusty Russell

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=4314C26E.9020408@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=rusty@rustcorp.com.au \
    --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.