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


Re: [Xen-users] streaming server on a virtual machine.

To: Brian Krusic <brian@xxxxxxxxxx>
Subject: Re: [Xen-users] streaming server on a virtual machine.
From: Grant McWilliams <grantmasterflash@xxxxxxxxx>
Date: Mon, 28 Sep 2009 10:58:55 -0700
Cc: Mike Wright <mike.wright@xxxxxxxxxxxxxx>, xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>, John Madden <jmadden@xxxxxxxxxxx>
Delivery-date: Mon, 28 Sep 2009 11:00:02 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=EQ80CYYuXKYfGDI0isMBO0ViGNlPTG/neSCjBS9HOxU=; b=Q4pC+PTt7klRQIwTlLQyQrNUKRAJCMUcO3WdPEi+puo1VoPgfdSRsRBsHiOWe9+xX5 rddUTUM8SOpB50EUqs32lyEQayrna69/9AYCOcrKK20mQMZYrA97/0vSPyDRsPuzTp4m zxe3or0MOK4CGEvufEGtiltWe8vNQZoNukVKs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=uGh6a/41fCEYqMXUI80JiZjvcumNcXlAKG6PUM+EeaKk+PsNqknCL3eKLdfCs6UOn0 K/fDIAgtwmBbn/+i7O+n4bbUF6hh4mRfdsXPLAPWrEE+U2YdI/iwGWh4E+/uJMHvgXkD JDlGJfX8R/P6eIgtZeKt1nCam4IoegOcckFFQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <24AF2127-1F4F-4D3A-B9EF-704FDEE64EB7@xxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <ab520d140909180307g31d6c768i8a749509a066354b@xxxxxxxxxxxxxx> <684AEB5D-3EAE-4643-95C1-CC1C5385EC6C@xxxxxxxxxx> <ed123fa30909270742o39f9eb6qc4b23e62f78e5ebb@xxxxxxxxxxxxxx> <DAA0F742-C66A-4F27-82F5-8E4AC56D63CF@xxxxxxxxxx> <ed123fa30909271655s44462bddked6832448f5b4cf6@xxxxxxxxxxxxxx> <D7AD782B-70E4-4871-8C84-9695FEC65CB4@xxxxxxxxxx> <4AC0DBA0.7070000@xxxxxxxxxxxxxx> <ed123fa30909281012u4244e8e2h4fe489f91b1ab9a1@xxxxxxxxxxxxxx> <1254158777.17608.38.camel@quagmire> <24AF2127-1F4F-4D3A-B9EF-704FDEE64EB7@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On Mon, Sep 28, 2009 at 10:39 AM, Brian Krusic <brian@xxxxxxxxxx> wrote:
Thats a great question.

I provide my own repos which sync to Centos/Plus/RPMForge/Gitco upon my choosing, normally once a month.

I then test any new updates before going live with a foreach loop, yumming hosts in my list.

I did the same is an MS$ env and am unsure of a better way.  But I've never managed more then 1,000 nodes.

Any one care to share there methodology?

- Brian

On Sep 28, 2009, at 10:26 AM, John Madden wrote:

On Mon, 2009-09-28 at 10:12 -0700, Grant McWilliams wrote:
The key words here are "read only".  Do not allow any domUs to write
to the same LV.

How do you facilitate providing updates to the domU's, for example, when
package upgrades need to take place?


I think what he's probably asking more than anything is since you have multiple OSs running off a single LV who gets the job of updating?

I would assume that you have to shutdown the other domains (maybe pause?), remount /usr as read/write, do the updates using one DomU and the unpause the others. I think this would be problemic though because you just updated one portion of the OS and didn't touch anything else (configs etc..).
This whole method makes me a bit nervous. Either that or you just never update!

Could you give us more detail on your update procedure please.

Grant McWilliams
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>