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

Re: [Xen-users] practical example and explanation of Xen sHype

To: "Christian Horn" <chorn@xxxxxxxxxxxx>
Subject: Re: [Xen-users] practical example and explanation of Xen sHype
From: "Henning Sprang" <henning_sprang@xxxxxx>
Date: Sat, 20 Jan 2007 13:23:52 +0100
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 20 Jan 2007 04:23:31 -0800
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=U3NcJxCKWN1A8+vdNA0bFMMC2GzyNFm6Ikwb7dCoSXUTIngIMdtYBsJ5Di7ae35XLAJlmeYnWLFSBZjDHEuOOO6mr6xte2Jxe66jKnUotTIbVegiO1IoP88jJnhWs3mdskVDib0FURxEnZ4wxxknQuo1qKBNNX/sP8Yd0Yy+By8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070116142644.GB11592@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <5bb00b3f0701150748s42248f4ua75d3f6f9cbcfb76@xxxxxxxxxxxxxx> <20070116142644.GB11592@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 1/16/07, Christian Horn <chorn@xxxxxxxxxxxx> wrote:
Had the same thing in mind when i listened to Ralf Spennebergs pre-
sentation at 23C3 on sHype.
But maybe its a good start when having a framework in mind that has an
overview on all domU of a site and manages their failover/loadbalancin
from a top view.

That is what I wrote in the last part of my mail - this is a possible
scenario, but for this another important piece is lacking, cause it's
not efficient, and tedious, and therefore again a thread to security
to have to bring the policy manually to all xen servers in a
distributed setup with automated load balancing -  manual actions
always call for human errors, e.g. forgetting to copy the changed
policy to one important host!

So, currently, sHype must be seen more like experimental, and should
be marked as this in the manual - with a note on the scenario in which
it will be useful one day if the full distributed security framework
is available.
If it would be documented like this, it would eventually even draw
developers who are interested in helping with the missing parts.

Henning

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

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