[lustre-discuss] Lustre Client in a container
E.S. Rosenberg
esr+lustre at mail.hebrew.edu
Tue Jan 2 10:59:51 PST 2018
On Mon, Jan 1, 2018 at 12:38 AM, Patrick Farrell <paf at cray.com> wrote:
>
>
> Keeping in mind that the choice of NFS means that you don’t have the POSIX
> guarantees provided by Lustre, so simultaneous access to the same files is
> dicey unless it’s only reading.
>
That just means that during the migration phase the 2.10 filesystem should
not be production yet or alternatively the 1.8 system is out of prodution
and read-only.... which would anyhow be the goal of a migration or am I
seeing this totally wrong?
Good luck and thanks everyone on lustre-users for being an excelletn
mailing list :)
Eli
> ------------------------------
> *From:* lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on
> behalf of Daniel Kobras <kobras at linux.de>
> *Sent:* Sunday, December 31, 2017 12:26:49 PM
> *To:* David Cohen
> *Cc:* lustre-discuss at lists.lustre.org
> *Subject:* Re: [lustre-discuss] Lustre Client in a container
>
> Hi David!
>
> Do you require both systems to be available as native Lustre filesystems
> on all clients? Otherwise, reexporting one of the systems via NFS during
> the migration phase will keep all data available but decouple the version
> interdependence between servers and clients. In this situation, it’s
> probably the least experimental option.
>
> Kind regards,
>
> Daniel
>
> > Am 31.12.2017 um 09:50 schrieb David Cohen <
> cdavid at physics.technion.ac.il>:
> >
> > Patrick,
> > Thanks for you response.
> > I looking for a way to migrate from 1.8.9 system to 2.10.2, stable
> enough to run the several weeks or more that it might take.
> >
> >
> > David
> >
> > On Sun, Dec 31, 2017 at 12:12 AM, Patrick Farrell <paf at cray.com> wrote:
> > David,
> >
> > I have no direct experience trying this, but I would imagine not -
> Lustre is a kernel module (actually a set of kernel modules), so unless the
> container tech you're using allows loading multiple different versions of
> *kernel modules*, this is likely impossible. My limited understanding of
> container tech on Linux suggests that this would be impossible, containers
> allow userspace separation but there is only one kernel/set of
> modules/drivers.
> >
> > I don't know of any way to run multiple client versions on the same node.
> >
> > The other question is *why* do you want to run multiple client versions
> on one node...? Clients are usually interoperable across a pretty generous
> set of server versions.
> >
> > - Patrick
> >
> >
> > From: lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on
> behalf of David Cohen <cdavid at physics.technion.ac.il>
> > Sent: Saturday, December 30, 2017 11:45:15 AM
> > To: lustre-discuss at lists.lustre.org
> > Subject: [lustre-discuss] Lustre Client in a container
> >
> > Hi,
> > Is it possible to run Lustre client in a container?
> > The goal is to run two different client version on the same node, can it
> be done?
> >
> > David
> >
> >
> > _______________________________________________
> > lustre-discuss mailing list
> > lustre-discuss at lists.lustre.org
> > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20180102/b1071935/attachment.html>
More information about the lustre-discuss
mailing list