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-api

[Xen-API] [xen-api-libs.hg:PATCH 0 of 2] Uuid stuff.

To: <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] [xen-api-libs.hg:PATCH 0 of 2] Uuid stuff.
From: <magnus.therning@xxxxxxxxxxxxx>
Date: Thu, 29 Jul 2010 16:46:51 +0100
Delivery-date: Thu, 29 Jul 2010 08:59:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
This is not ready for merging, but I'd like some comments on the code
and direction.

Besides the minor clean-up (is more needed?) it introduces a new
function, make_uuid_random, which reads from /dev/random (and
therefore may block).

The plan is to change make_uuid to use the PRNG in Random, and then
modify xapi so that make_uuid_random is used where it's necessary
(creating pool secret and sessions, what else?).

Is this a direction that's worthwhile to pursue?
Would a make_uuid_urandom also be necessary?  (E.g. getting session
UUIDs from /dev/random might be too heavy weight for something that's
that short-lived.)

2 files changed, 30 insertions(+), 44 deletions(-)
uuid/uuid.ml  |   38 +++++++++-----------------------------
uuid/uuid.mli |   36 +++++++++++++++++++++---------------

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api