Linux NFS development
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Benjamin Coddington <bcodding@redhat.com>
Cc: Harald Dunkel <harald.dunkel@aixigo.de>, linux-nfs@vger.kernel.org
Subject: Re: running NFS in LXC
Date: Thu, 15 Feb 2018 10:45:16 -0500	[thread overview]
Message-ID: <20180215154516.GB9999@fieldses.org> (raw)
In-Reply-To: <F9942544-0C31-4618-BF73-292FF4265C31@redhat.com>

On Wed, Feb 14, 2018 at 09:15:05AM -0500, Benjamin Coddington wrote:
> On 14 Feb 2018, at 2:06, Harald Dunkel wrote:
> 
> >Hi Ben,
> >
> >I take this as a "no serious problems by now". Good to hear.
> >Which kernel are you using?
> 
> This was years ago on a 2.6.32 series.  I don't expect you'll have
> serious problems now, either.  As far as I know, my last employer is
> still using that architecture, but I couldn't tell you what software
> versions they're on now..
> 
> We moved to the knfsd-in-a-container from an architecture that was
> essentially a bunch of vanilla knfsds that could mount and any of
> the block devices, and block devices were tied to IP addresses, and
> this was all orchestrated by pacemaker.  The problem with that one
> was that when a block device or filesystem was migrated, the server
> receiving that filesystem had to be put into grace, which disrupted
> any existing NFS serving that was going on.
> 
> Test things, let us know how it works!

I think you were using KVM, right, Ben?

Harald is talking about LXC, and there are still a few problems there.

Jeff, do you object to going back to our plan B for reboot recovery (the
daemon)?  The usermode helper containerization seems stalled and I have
to admit I'm probably not going to take it on myself.  That might be the
only knfsd-in-a-container obstacle left.

--b.

  reply	other threads:[~2018-02-15 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13  9:55 running NFS in LXC Harald Dunkel
2018-02-13 18:28 ` Benjamin Coddington
2018-02-14  7:06   ` Harald Dunkel
2018-02-14 14:15     ` Benjamin Coddington
2018-02-15 15:45       ` J. Bruce Fields [this message]
2018-02-15 19:14         ` Benjamin Coddington
2018-03-20 11:09         ` Harald Dunkel
2018-03-20 12:01         ` Jeff Layton
2018-03-20 13:22           ` Scott Mayhew

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=20180215154516.GB9999@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bcodding@redhat.com \
    --cc=harald.dunkel@aixigo.de \
    --cc=linux-nfs@vger.kernel.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