Linux Container Development
 help / color / mirror / Atom feed
From: Cedric Le Goater <legoater-GANU6spQydw@public.gmane.org>
To: Sukadev Bhattiprolu
	<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: restart (mktree) program usage
Date: Fri, 18 Sep 2009 08:58:54 +0200	[thread overview]
Message-ID: <4AB32FAE.8020404@free.fr> (raw)
In-Reply-To: <20090917013546.GA30161-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

On 09/17/2009 03:35 AM, Sukadev Bhattiprolu wrote:
> Oren Laadan [orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org] wrote:
> | 
> | 
> | Sukadev Bhattiprolu wrote:
> | > I have a usage question on the 'restart' (formerly mktree) program.
> | > 
> | > In the following container c/r case: 
> | > 
> | > 	- create a container
> | > 	- log in to the container,
> | > 	- restore filesystem(s) from snapshot
> | > 	- restart application from checkpoint
> | 
> | FWIW, I'd expect that future versions of 'restart' will be capable
> | of doing this entire setup, (filesystem(s) included), as it matures.
> | 
> | Note that this use case that you suggest will only work to restart
> | subtrees; it is unsuitable for full containers (with pids) because
> | the pid of init (1) will already be in use.
> 
> True. But if originally the application was started as:
> 
> 	Create container
> 	Login to contaienr
> 	Set up filesystem
> 	Start application

You should take a look at lxc, which is doing what you want.

Metacluster (IBM's proprietary C/R solution) is fully integrated with lxc 
containers and the current lxc development plans focus on externalizing 
some home made C/R plugins we've been doing for it. We should then spend 
some time on blcr.

And we expect you guys to work on oren's patchset ? but I guess that will 
all depend on how 'proprietary' is mktree, by 'proprietary' I mean 
dependent on the kernel patch. 

Cheers,

C.

      parent reply	other threads:[~2009-09-18  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09  5:56 restart (mktree) program usage Sukadev Bhattiprolu
     [not found] ` <20090909055636.GA27622-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-09-09 22:26   ` Oren Laadan
     [not found]     ` <4AA82B7C.8080107-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-09-17  1:35       ` Sukadev Bhattiprolu
     [not found]         ` <20090917013546.GA30161-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-09-17  3:14           ` Oren Laadan
     [not found]             ` <4AB1A99D.3020307-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-09-17 13:18               ` Serge E. Hallyn
     [not found]                 ` <20090917131843.GA29297-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-09-17 16:53                   ` Sukadev Bhattiprolu
     [not found]                     ` <20090917165311.GB13855-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-09-17 17:13                       ` Serge E. Hallyn
2009-09-17 17:58                   ` Oren Laadan
     [not found]                     ` <4AB278D0.50604-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-09-17 18:20                       ` Serge E. Hallyn
2009-09-18  6:58           ` Cedric Le Goater [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=4AB32FAE.8020404@free.fr \
    --to=legoater-ganu6spqydw@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox