All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Wolff <joe-w0bN8YRwa0o@public.gmane.org>
To: Dor Laor <dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Stacked disks
Date: Sun, 02 Sep 2007 17:36:07 -0700	[thread overview]
Message-ID: <46DB56F7.4070909@osdf.com> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E032160D70630A-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>

Thanks, Dor, we'll plan accordingly, and make the base images read-only.

Cheers,
joe



Dor Laor wrote:
>> Hello,
>>
>> I would like to set up stacked disk images as follows:
>>
>> 1) Base-image of Ubuntu, with ubuntu-minimal installed.
>>
>> 2) Multiple other images all based on the single image above, with
>> various single-purpose packages installed; eg Apache, Exim, etc.
>>
>> Now, comes the hard part:
>>
>> Q2: What happens if I change the underlying ubuntu-minimal image (For a
>> good example, to apply security updates), while several of the other
>> "upper" images (Apache Exim, etc) are running?
>>
>> Q1: Easier: If everything is down, can I change the underlying image
> and
>> will the changes be properly reflected in the "upper" (dependent)
>> images?
>>
>>
>> I see problems with simply a file-based algorithm which looks first in
>> the upper image, and then in the base image..
>>
>> It's really a reconciliation problem..
> 
> 
> The quick answer:
> You can't do that (both 1, 2).
> This disks are block devices that represent a physical disk. Doing
> something
> to a block in the base image can erase information that the next image
> relays on.
> Actually it is good practice to chmod a-w BASE_IMG if there are
> children.
> 
> So you shouldn't mess with the base image, you can replicate it and
> update all of them.
> 
> A better answer:
> There is unionFS that might help here: All VMs will mount ro the base
> image while
> having another drive for their private applications. UnionFs work in the
> file level
> above and do the merge between the base and private images so basically
> you can
> update the base image once in a while (when unionFS is down/inactive).
> 
>>
>> FYI: I was a KVM forum attendee; I'm building a hosting infrastructure
>> based on KVM, and so clearly saving / consolidating space & updates
> such
>> as in the example above is of keen interest to me.
>>
>> And Thanks again to the Qumranet team for an informative and successful
>> conference!
>>
>>
>> Thanks,
>> Joe
> 
> Thanks for the participation and for choosing KVM.
> We enjoyed the forum too.
> -Dor

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

      parent reply	other threads:[~2007-09-03  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-02 18:51 Stacked disks Joseph Wolff
     [not found] ` <46DB062E.5070004-w0bN8YRwa0o@public.gmane.org>
2007-09-02 20:07   ` Dor Laor
     [not found]     ` <64F9B87B6B770947A9F8391472E032160D70630A-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-09-03  0:36       ` Joseph Wolff [this message]

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=46DB56F7.4070909@osdf.com \
    --to=joe-w0bn8yrwa0o@public.gmane.org \
    --cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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.