<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:17:46 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-1566]  Suggested Lustre Version</title>
                <link>https://jira.whamcloud.com/browse/LU-1566</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;My name is Bob Torgerson, and I work as an HPC Analyst for the Arctic&lt;br/&gt;
Region Supercomputing Center in Fairbanks, Alaska. Recently, we have been&lt;br/&gt;
working to build a Lustre file system for our high performance systems and&lt;br/&gt;
desktop clients, a file system with a total storage capacity of&lt;br/&gt;
approximately 290 TB. We decided to go with Lustre version 1.8.8 for our&lt;br/&gt;
initial install on the suggestion of Zhiqi Tao, my instructor in a&lt;br/&gt;
WhamCloud training in Alexandria, VA. We have moved forward with the&lt;br/&gt;
installation using Lustre 1.8.8  on RHEL 5 servers and have a working file&lt;br/&gt;
system able to be exported to our clients. However, we have had some issues&lt;br/&gt;
related to hardware such as newer QLogic cards being unsupported in RHEL 5&lt;br/&gt;
that appear that they would be resolved by upgrading to RHEL 6, but at this&lt;br/&gt;
point, Lustre 1.8.8 is unsupported on RHEL 6 servers.&lt;/p&gt;

&lt;p&gt;Before we move further forward with our implementation, I would like to&lt;br/&gt;
discuss with WhamCloud support what version of the Lustre software is&lt;br/&gt;
recommended for production. We have the 1.8.8 Lustre file system working&lt;br/&gt;
now, but have not invited beta testers to try it yet, meaning that we still&lt;br/&gt;
have time to make changes including what version of Lustre we use before we&lt;br/&gt;
invite users to use the file system.&lt;/p&gt;

&lt;p&gt;Any suggestions you could provide to me would be greatly appreciated!&lt;/p&gt;

&lt;p&gt;Thank you in advance,&lt;/p&gt;

&lt;p&gt;Terry &lt;br/&gt;
Penguin Tech Support&lt;br/&gt;
Ph. 415-954-2833&lt;/p&gt;</description>
                <environment></environment>
        <key id="15041">LU-1566</key>
            <summary> Suggested Lustre Version</summary>
                <type id="3" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11318&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="cliffw">Cliff White</assignee>
                                    <reporter username="tsingh">Terry Singh</reporter>
                        <labels>
                    </labels>
                <created>Tue, 26 Jun 2012 12:29:59 +0000</created>
                <updated>Mon, 9 Jul 2012 19:36:17 +0000</updated>
                            <resolved>Mon, 9 Jul 2012 19:36:17 +0000</resolved>
                                    <version>Lustre 1.8.8</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="41164" author="cliffw" created="Tue, 26 Jun 2012 16:59:17 +0000"  >&lt;p&gt;As you wish to run Redhat 6, we would advise you moving to Lustre 2.1, our current production release.&lt;br/&gt;
&lt;a href=&quot;http://downloads.whamcloud.com/public/lustre/latest-maintenance-release/el6&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://downloads.whamcloud.com/public/lustre/latest-maintenance-release/el6&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This will position you for the future, and eliminate the RHEL6 issue. The 1.8 stream is due for retirement (see the Lustre Roadmap &lt;a href=&quot;http://wiki.whamcloud.com/display/PUB/Community+Lustre+Roadmap&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://wiki.whamcloud.com/display/PUB/Community+Lustre+Roadmap&lt;/a&gt;), and especially for a new implementation, we would advise Lustre 2.1&lt;/p&gt;</comment>
                            <comment id="41206" author="pjones" created="Wed, 27 Jun 2012 13:33:34 +0000"  >&lt;p&gt;I would agree that 2.1.x is a sensible approach but I want to clarify that 1.8.x is &lt;em&gt;not&lt;/em&gt; due for retirement. We plan to keep supporting it as long as sufficient demand is there, but recognize that this demand will wane over time.&lt;/p&gt;</comment>
                            <comment id="41627" author="cliffw" created="Mon, 9 Jul 2012 16:41:53 +0000"  >&lt;p&gt;Did this answer your question? Can we do anything more for you on this issue?&lt;/p&gt;</comment>
                            <comment id="41638" author="tsingh" created="Mon, 9 Jul 2012 18:34:26 +0000"  >&lt;p&gt;Hello Cliff, &lt;/p&gt;

&lt;p&gt; Yes, I did answer my questions. Please go ahead and close the case. &lt;/p&gt;

&lt;p&gt;Thanks&lt;br/&gt;
Terry&lt;/p&gt;</comment>
                            <comment id="41641" author="cliffw" created="Mon, 9 Jul 2012 19:36:17 +0000"  >&lt;p&gt;Issue resolved&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvtlj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8740</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>