<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:23:07 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-16001] interop between 2.12 and 2.15</title>
                <link>https://jira.whamcloud.com/browse/LU-16001</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;short version:&lt;br/&gt;
will 2.12 servers and 2.15 clients interop ok?&lt;/p&gt;

&lt;p&gt;I don&apos;t know if you do interop testing between LTS releases, but it seems like something that could be desirable to make upgrade paths clearer.&lt;/p&gt;

&lt;p&gt;longer version:&lt;br/&gt;
we have a cluster refresh coming up at the end of the year. currently our clients are rhel7/8 kernels with rhel7 userland and lustre 2.12.x.&lt;br/&gt;
lustre servers are rhel7 and 2.12.x, all zfs, all accessed via lnet routers.&lt;/p&gt;

&lt;p&gt;the new compute client hardware is planned to be rhel9(alma9/rocky9/whatever) which seems to force us to change to lustre 2.15 as 2.12 doesn&apos;t support rhel9.&lt;br/&gt;
some lustre servers are being expanded and others decommissioned, but ideally we&apos;d leave those at 2.12 and rhel7 for a while and not have to upgrade everything at once. lnet routers are being added to talk to the new compute.&lt;/p&gt;

&lt;p&gt;can we keep the lustre servers at 2.12 and still talk to 2.15 clients ok, or do we have to upgrade the servers to 2.15 at the same time we add 2.15 clients?&lt;/p&gt;

&lt;p&gt;if 2.15 on servers is required, then is rhel7 ok, or rhel8 recommended, or ...?&lt;br/&gt;
we are zfs 0.8.5 at the moment.&lt;/p&gt;

&lt;p&gt;any hints and advice is welcome.&lt;br/&gt;
thanks.&lt;/p&gt;

&lt;p&gt;FWIW a couple of days ago I briefly booted an alma9 node with git master lustre + 1 rhel9 patch to our 2.12 servers, and didn&apos;t notice any problems, but also didn&apos;t do much more than boot to root-on-lustre, and ls and df.&lt;/p&gt;

&lt;p&gt;cheers,&lt;br/&gt;
robin&lt;/p&gt;</description>
                <environment>x86_64, zfs</environment>
        <key id="71084">LU-16001</key>
            <summary>interop between 2.12 and 2.15</summary>
                <type id="9" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/undefined.png">Question/Request</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</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="pjones">Peter Jones</assignee>
                                    <reporter username="scadmin">SC Admin</reporter>
                        <labels>
                    </labels>
                <created>Sun, 10 Jul 2022 07:51:32 +0000</created>
                <updated>Mon, 11 Jul 2022 14:11:45 +0000</updated>
                            <resolved>Mon, 11 Jul 2022 14:11:45 +0000</resolved>
                                    <version>Lustre 2.12.9</version>
                    <version>Lustre 2.15.1</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="339994" author="pjones" created="Sun, 10 Jul 2022 13:25:59 +0000"  >&lt;p&gt;HI there&lt;/p&gt;

&lt;p&gt;Yes we do interop testing between LTS versions and we call out the supported interoperability in the changelog - &lt;a href=&quot;https://wiki.lustre.org/index.php?title=Lustre_2.15.0_Changelog.&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://wiki.lustre.org/index.php?title=Lustre_2.15.0_Changelog.&lt;/a&gt;&#160;Using clients for the newer Lustre version with the existing servers in order to get support for more current kernel versions is the most common use case for running in an interoperability configuration. We are actively working on getting RHEL9 client support fully in place for 2.1.5.x releases. There is still some work remaining but this should comfortably be complete by the end of the year.&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="340056" author="scadmin" created="Mon, 11 Jul 2022 13:48:02 +0000"  >&lt;p&gt;Hi Peter,&lt;/p&gt;

&lt;p&gt;thanks for that. I&apos;d missed that in the changelog.&lt;/p&gt;

&lt;p&gt;I&apos;m relieved we&apos;ll be able to space out the new hardware and client OS changes from the lustre server update effort. phew.&lt;/p&gt;

&lt;p&gt;please close the ticket. thanks for the quick response.&lt;/p&gt;

&lt;p&gt;cheers,&lt;br/&gt;
robin&lt;/p&gt;</comment>
                            <comment id="340063" author="pjones" created="Mon, 11 Jul 2022 14:11:45 +0000"  >&lt;p&gt;Great news - thanks Robin&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|i02u7b:</customfieldvalue>

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