https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-3914 Lustre <p>Hi James,</p> <p>Soon we'll open a Jira ticket for a (very) quick discussion of the RPM's<br/> that we'll use to put our new storage (Atlas) into production here at<br/> ORNL. We have had a new system that requires a 2.X filesystem (client is<br/> only 2.4). We'll chime in on what we've been building (including<br/> patches/jira tickets), and we need to get a sign-off that we're in good<br/> shape to move into production. Any patches that Intel wants us to include<br/> should also be mentioned so that we can evaluate the patch for our own<br/> stability purposes.</p> <p>This ticket will need pretty fast turn around so I wanted to make you<br/> aware.</p> LU-3914

Need sign off on Lustre RPM's and patches to include for ORNL 2.4 transition to Operations

Task Minor Resolved Fixed James Nunez Jason Hill Mon, 9 Sep 2013 14:40:42 +0000 Mon, 23 Sep 2013 14:51:52 +0000 Mon, 23 Sep 2013 14:51:52 +0000 0 5 <p>James will own providing the response on this. Jason, please provide the details of the patches you are evaluating at your convenience.</p> <p>For the last set of rpms I only included one patch which was for <a href="https://jira.whamcloud.com/browse/LU-3497" title="Lustre build system hardcoded to using ZFS development headers in /usr/include only. " class="issue-link" data-issue-key="LU-3497"><del>LU-3497</del></a>. That patch enables us to build ZFS without installing zfs rpms on your build machines. The only other patch I can think of is also <a href="http://review.whamcloud.com/#/c/6960" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/6960</a> for <a href="https://jira.whamcloud.com/browse/LU-2987" title="llite destory_inode should call rcu free" class="issue-link" data-issue-key="LU-2987"><del>LU-2987</del></a> but this is more to support cray SLES11 SP2 clients. Cray also saw issues with NFS which we might be interested in.</p> <p>I’d like to get a complete picture of what your system will be running and then we can comment on if you should apply patches and which ones. You stated that the clients will be 2.4. Client 2.4.1? What server version will you be using 2.4.1 or 2.5.0? You’ll be using ZFS and SLES 11 SP2. Correct?</p> <p>Is there a ticket open for the NFS issues that Cray saw?</p> <p>Thanks,<br/> James</p> <p>We will have the Cray 1.8.6 client (~18k nodes), a mix of 1.8.8 and 1.8.9 Linux clients(~250 nodes), and the Cray 2.4.0 client (~750 nodes). </p> <p>2.4.1 is the recommended upgrade path. Is this your target release?</p> <p>James,</p> <p>When is the GA release date for 2.4.1 (has it passed and I missed it?)? We need to be in production next week with a small filesystem, and then will transition all of the hardware to production in early October. If you have something that Intel will bless/support now then we'll run it. Otherwise we're going 2.4.0 for now and will evaluate 2.4.1 as an upgrade when it's GA'd and we have some time to test it internally.</p> <p>&#8211;<br/> -Jason</p> <p>Jason, </p> <p>Thank you for your timeline on transitioning to 2.4. Let's find out what patches are recommended with a 2.4.0 installation. </p> <p>Oleg, </p> <p>Would you please comment on recommended patches to 2.4.0?</p> <p>Thank you,<br/> James</p> <p>Just as a note we are running a Lustre 2.4 snapshot from the middle of August.</p> <p>2.4.1 is in release testing at the moment and, depending upon how the testing progresses, should be out soon.</p> <p>We recommend that your initial 2.4 deployment be to the latest b2_4 branch. We plan to include the patch for <a href="https://jira.whamcloud.com/browse/LU-3497" title="Lustre build system hardcoded to using ZFS development headers in /usr/include only. " class="issue-link" data-issue-key="LU-3497"><del>LU-3497</del></a> in the 2.4.2 release and, thus, feel comfortable patching the latest b2_4 code with that patch.</p> <p>We absolutely will support ORNL running on this code.</p> <p>After the initial deployment and testing, we can see whether any further patches may be needed.</p> <p>ORNL said they received an adequate response. Closing ticket.</p> Development Rank 1|hzw1hj: Rank (Obsolete) 10322