All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@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: Wed, 09 Sep 2009 18:26:04 -0400	[thread overview]
Message-ID: <4AA82B7C.8080107@librato.com> (raw)
In-Reply-To: <20090909055636.GA27622-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>



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.

Perhaps we should think of some "plugin" architecture for 'restart'
that will allow the user to ask it to execute some work at between
creating a new container and actually restarting into it ?

> 
> On restart, suppose the user wants to restore the original pids.
> But he does not want to create a new pid-ns, (since he just created
> the container, and is sure the original pids are available).
> 
> To accomplish this the user has to specify the arguments in the following
> order right  (since -pids implies --pidns).
> 
> 	restart --pids --no-pidns
> 
> IOW, the order of the arguments matters.
> 
> Would it be easier to understand if --pids did not imply --pidns ?

Either that, or simply change the semantics such that the order
does not matter:

> 
> (Or in fact the reverse seems to make more sense -i.e --pidns implies
> --pids, with a new option, --no-pids if user absolutely hates the pids
> he was dealt before checkpoint :-)
> 
> 	$ restart
> 		don't create pid ns, don't try to restore pids
> 
> 	$ restart --pids
> 		try to restore original pids, don't create pid-ns
> 
> 	$ restart --pidns
> 		create new pid-namespace and restore original pids
> 
> 	$ restart --pidns --no-pids
> 	$ restart --no-pids --pidns
> 		create new pid-namespace, DO NOT restore pids

Yes, something like that.

Oren.

> 
> Or maybe drop implying and let user explicitly specify one, none or
> both of --pids, --pidns ?
> 
> Sukadev
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers

  parent reply	other threads:[~2009-09-09 22:26 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 [this message]
     [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

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=4AA82B7C.8080107@librato.com \
    --to=orenl-rdfvbdnroixbdgjk7y7tuq@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 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.