Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Martin Fick <mogulguy-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: NFS Kernel server inside a container
Date: Wed, 19 May 2010 10:45:38 -0500	[thread overview]
Message-ID: <20100519154538.GA18057@us.ibm.com> (raw)
In-Reply-To: <516306.35958.qm-xC2hcER8YRCvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>

Quoting Martin Fick (mogulguy-/E1597aS9LQAvxtiuMwx3w@public.gmane.org):
> --- On Wed, 5/19/10, Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org> wrote:
> It sounds like you did an NFS client mount inside a
> container. I am actually trying to do the reverse, I
> would like to do kernel server exports from within
> a container.  Specifically, I would like to have
> several data partitions replicated with drbd and to
> be able to export these partitions via NFS 
> independently from different containers with
> different IPs.  
> 
> So, for example, from 2 hosts, I might have 6 NFS 
> partitions to export and during normal operation
> I would expect each host to make 3 of the 
> partitions primary via drbd and to then to
> each launch three containers each with separate 
> IPs which will individually export the 3 different 
> drbd partitions via NFS.  For failover or load 
> balancing, it should then be able to shut down
> any individual container on one host and bring it
> up on the other host without affecting the other
> exports.
> 
> Thanks,
> 
> -Martin

You'll need to use a userspace NFS server.  Something like
http://unfs3.sourceforge.net/.  Certainly looks...  venerable.

-serge

  parent reply	other threads:[~2010-05-19 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 18:51 NFS Kernel server inside a container Martin Fick
     [not found] ` <259227.79616.qm-UkVgyPgTERivuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-05-18 19:46   ` Michael Tokarev
2010-05-19  9:59   ` Daniel Lezcano
     [not found]     ` <4BF3B677.7080601-GANU6spQydw@public.gmane.org>
2010-05-19 15:26       ` Martin Fick
     [not found]         ` <516306.35958.qm-xC2hcER8YRCvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-05-19 15:45           ` Serge E. Hallyn [this message]
2010-05-19 19:33           ` Daniel Lezcano
  -- strict thread matches above, loose matches on Subject: below --
2010-05-18 21:09 Martin Fick
     [not found] ` <187493.1732.qm-4AwnY8zbAf+vuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-05-29 22:11   ` Eric W. Biederman

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=20100519154538.GA18057@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=mogulguy-/E1597aS9LQAvxtiuMwx3w@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