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

[Xen-devel] Re: CKRM port

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: CKRM port
From: Diwaker Gupta <diwakergupta@xxxxxxxxx>
Date: Sat, 16 Oct 2004 19:14:08 -0700
Delivery-date: Sun, 17 Oct 2004 06:45:53 +0100
Domainkey-signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ZblhTX3Ue9lNVX2K4s3v45tRKDLpz3DqvQLiyD+RTt94cR0/vHRxdW59P5gIJA2CgSevblXUm5j4p4aFpuh8slXqHSxVKYFK3u5rc0APdXhnkmFhxE2JALj04UIYy9LA/xgNYiwDsSdDDAAAOqu8mcMjYNj0OBcXZT/EhCQVcbs
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <1b0b455704101619132fdd9b8b@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <Pine.LNX.4.44.0410142310340.24467-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <E1CIM03-0005Rr-00@xxxxxxxxxxxxxxxxx> <1b0b455704101619132fdd9b8b@xxxxxxxxxxxxxx>
Reply-to: Diwaker Gupta <diwakergupta@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Sorry, forgot to CC to the list.


---------- Forwarded message ----------
From: Diwaker Gupta <diwakergupta@xxxxxxxxx>
Date: Sat, 16 Oct 2004 19:13:13 -0700
Subject: Re: [Xen-devel] CKRM port
To: Ian Pratt <ian.pratt@xxxxxxxxxxxx>


> It would be kinda nice to have control over all the VMs
> integrated into the same name space as the dom0 kernel's CKRM,
> but its not really necessary. I'd rather have something in a
> similar style done by a daemon in user space, enabling control
> over all the VMs in a particular cluster rather than just the
> local machine. The intention would be to provide a single
> management interface for a whole cluster, with a pool of VMs
> running over it. Live migration gives you a good deal of
> transparency as regards moving VMs between physical nodes.

I was, in fact, investigating a CKRM port in this regard. The idea, as
you said, would be to have a live pool of VMs. Given the transparencey
of migration, and the ease of dynamic management of VMs, we'd like to
"virtualize" the whole cluster so that multiple users can have their
own "virtual clusters" for their experiments. But we want to be able
to really fine tune the allocation and management of various
resources. CKRM looks to be a good first step, though I believe it can
be done using existing Xen features (like the atropos scheduler)
--
Diwaker Gupta
http://resolute.ucsd.edu/diwaker


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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