darby.vicke...@nasa.gov>>, Ben
Evans <bev...@cray.com<mailto:bev...@cray.com>>,
"lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>"
<lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>>
Subject: Re: [lustre-discuss] de
t;
> /etc/modprobe.d/lustre.conf:
>
> options lnet networks=tcp0(enp4s0),o2ib0(ib1)
> options ko2iblnd map_on_demand=32
>
> -----Original Message-----
> From: Brian Andrus <toomuc...@gmail.com>
> Date: Friday, February 10, 2017 at 12:07 AM
> To: Darby Vicker <dar
,
"lustre-discuss@lists.lustre.org" <lustre-discuss@lists.lustre.org>
Subject: Re: [lustre-discuss] design to enable kernel updates
Darby,
Do you mind if I inquire about the setup for your lustre systems?
I'm trying to understand how the MGS/MGT is setup for high availability.
I under
tre-discuss@lists.lustre.org>
Subject: Re: [lustre-discuss] design to enable kernel updates
It's certainly possible. When I've done that sort of thing, you upgrade
the OS on all the servers first, boot half of them (the A side) to the new
image, all the targets will fail over to the B server
te: Monday, February 6, 2017 at 2:22 PM
To: Brian Andrus <toomuc...@gmail.com>, "lustre-discuss@lists.lustre.org"
<lustre-discuss@lists.lustre.org>
Subject: Re: [lustre-discuss] design to enable kernel updates
It's certainly possible. When I've done that sort of thing, you u
It's certainly possible. When I've done that sort of thing, you upgrade
the OS on all the servers first, boot half of them (the A side) to the new
image, all the targets will fail over to the B servers. Once the A side
is up, reboot the B half to the new OS. Finally, do a failback to the
All,
I have been contemplating how lustre could be configured such that I
could update the kernel on each server without downtime.
It seems this is _almost_ possible when you have a san system so you
have failover for OSTs and MDTs. BUT the MGS/MGT seems to be the
problematic one, since
