<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:26:42 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-2614] Add build support for HCA virtualisation </title>
                <link>https://jira.whamcloud.com/browse/LU-2614</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Change lbuild script to support compilation of Mellanox (alpha) OFED stack&lt;br/&gt;
to support SR-IOV virtualisation for IB HCAs&lt;/p&gt;

&lt;p&gt;NOTE:  Work needed to support the testing of IB Virtualization on the Julich cluster,&lt;/p&gt;</description>
                <environment></environment>
        <key id="17162">LU-2614</key>
            <summary>Add build support for HCA virtualisation </summary>
                <type id="6" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11315&amp;avatarType=issuetype">Story</type>
                                            <priority id="2" iconUrl="https://jira.whamcloud.com/images/icons/priorities/critical.svg">Critical</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="6">Not a Bug</resolution>
                                        <assignee username="heckes">Frank Heckes</assignee>
                                    <reporter username="heckes">Frank Heckes</reporter>
                        <labels>
                    </labels>
                <created>Mon, 14 Jan 2013 08:59:14 +0000</created>
                <updated>Fri, 1 Mar 2019 22:41:27 +0000</updated>
                            <resolved>Fri, 1 Mar 2019 22:41:27 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="50415" author="simmonsja" created="Mon, 14 Jan 2013 10:32:13 +0000"  >&lt;p&gt;Out of curiosity is this their OFED-1.9 stack?&lt;/p&gt;</comment>
                            <comment id="50425" author="heckes" created="Mon, 14 Jan 2013 11:55:30 +0000"  >&lt;p&gt;No, not as far as I know. We working with the pre-release version supporting SR-IOV for &lt;br/&gt;
Mellanox HCA&apos;s that is available for RHEL/CentOS 6.2 only, just to prepare the&lt;br/&gt;
build system and autotest framework to make use of the feature quickly for &apos;production&apos; &lt;br/&gt;
as soon as support for 6.3 and other distros will be released.&lt;/p&gt;</comment>
                            <comment id="50484" author="adilger" created="Tue, 15 Jan 2013 13:18:34 +0000"  >&lt;p&gt;Frank, any reason why this is for 2.2 and not 2.4?&lt;/p&gt;</comment>
                            <comment id="50531" author="heckes" created="Wed, 16 Jan 2013 04:16:49 +0000"  >&lt;p&gt;At the moment the Mellanox SR-IOV enabled OFED only&lt;br/&gt;
supports kernel version 2.6.32-220.X. (Tried to do for current&lt;br/&gt;
master branch, but naive build failed and I would end up in coding the ofa kernel)&lt;br/&gt;
This kernel seems to be available in b2_2 only (please correct me if I&apos;m wrong).&lt;br/&gt;
I expect Rhel/CentOS6.3 supported OFED to be shared with us&lt;br/&gt;
next Monday.&lt;br/&gt;
Anyway, I decided to use this branch to create a prototype. Looks&lt;br/&gt;
very promissing all build succeed (i.e Lustre was built against&lt;br/&gt;
the SR-IOV OFED) and we&apos;re going to run autotest against it today.&lt;br/&gt;
Once that work, we can easily replace the new OFED to run build of the &lt;br/&gt;
master branch.&lt;/p&gt;</comment>
                            <comment id="51105" author="heckes" created="Thu, 24 Jan 2013 10:16:22 +0000"  >&lt;p&gt;Changed lbuild to compile SR-IOV OFED stack and compile Lustre against it.&lt;br/&gt;
Software builds executed successful (see: &lt;a href=&quot;http://build.whamcloud.com/job/lustre-reviews-vib/arch=x86_64,build_type=server,distro=el6,ib_stack=vofa/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://build.whamcloud.com/job/lustre-reviews-vib/arch=x86_64,build_type=server,distro=el6,ib_stack=vofa/&lt;/a&gt;)&lt;br/&gt;
    Constraints: Rhel/CentOS 6.2, kernel 2.6.32.220.* for server&lt;br/&gt;
Autotest ran successful, too. (although test_123a failed; see: &lt;a href=&quot;https://maloo.whamcloud.com/test_sets/c20ab082-6633-11e2-a42b-52540035b04c&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://maloo.whamcloud.com/test_sets/c20ab082-6633-11e2-a42b-52540035b04c&lt;/a&gt; , it proves the concept) &lt;/p&gt;

&lt;p&gt;Wait for Rhel/CentOS 6.3 OFED stack to use the framework changes (jenkins, lbuild) for master branch and finally land the change.&lt;/p&gt;</comment>
                            <comment id="55744" author="heckes" created="Mon, 8 Apr 2013 15:12:22 +0000"  >&lt;p&gt;Received Mellanox (SR-IOV enabled) OFED stack for CentOS 6.3.&lt;br/&gt;
Made changes to compile Lustre against Mellanox OFED stack (see gerrit:5295 patch 17)&lt;br/&gt;
Build has been started in test queue &apos;Frank_Heckes&apos;; waiting for test results.&lt;/p&gt;</comment>
                            <comment id="55852" author="heckes" created="Tue, 9 Apr 2013 12:48:32 +0000"  >&lt;p&gt;Build tested almost successful, besides test_0c, test_0d and test_73a of &apos;replay-single&apos; suite. These error are related to bug &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-414&quot; title=&quot;error looking up logfile&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-414&quot;&gt;&lt;del&gt;LU-414&lt;/del&gt;&lt;/a&gt;.&lt;br/&gt;
Installation and all other tests ran successful which proves the concept. &lt;br/&gt;
See session :&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://maloo.whamcloud.com/test_sessions/0c32a460-a0dd-11e2-b429-52540035b04c&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://maloo.whamcloud.com/test_sessions/0c32a460-a0dd-11e2-b429-52540035b04c&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The build is currently available on Whamcloud internal jenkins-node &apos;jenkins-staging&apos;. I&apos;ll make them available asap.&lt;/p&gt;</comment>
                            <comment id="57511" author="jlevi" created="Thu, 2 May 2013 13:20:09 +0000"  >&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/#change,5295&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,5295&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="93689" author="heckes" created="Wed, 10 Sep 2014 14:12:40 +0000"  >&lt;p&gt;Pushed change that will change the RPM specfile to build the Mellanox kernel modules and kernel-devel RPM to fit into the Jenkins build environment:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/#/c/11593/2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/11593/2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The change have been successful tested on node identical to onyx Jenkins builder on J&#252;lich autotest cluster Juliette.&lt;br/&gt;
The RPMs have been installed, a Lustre FS had been created and tested successful using on single SR-IOV enable node of Juliette.&lt;/p&gt;

&lt;p&gt;Anyway change is too inflexible. Will supply new change which will only change the --o2ib-path flag for Lustre configure.&lt;/p&gt;</comment>
                            <comment id="95512" author="heckes" created="Thu, 2 Oct 2014 14:02:02 +0000"  >&lt;ul&gt;
	&lt;li&gt;New patch relying on the modification of variable CONFIGURE_FLAGS only to provide the correct&lt;br/&gt;
path of the Mellanox OFED compat header files to Lustre configure (via &lt;tt&gt;--with-o2ib=...&lt;/tt&gt;) has been&lt;br/&gt;
pushed:&lt;br/&gt;
&lt;a href=&quot;http://review.whamcloud.com/#/c/11593/3&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/11593/3&lt;/a&gt;&lt;br/&gt;
Build ended  successful, but code need a correction and additionally an extension to download the Mellanox OFED tar archive&lt;br/&gt;
automatically.&lt;/li&gt;
	&lt;li&gt;Change need to be test also in Jenkins job &apos;lustre-reviews-vib&apos;, since configuration of &apos;lustre-reviews&apos;&lt;br/&gt;
won&apos;t cover the execution of MLNX builds (vib or mlnx label + setting in script file is missing in lustre-reviews)&lt;br/&gt;
Queue has to be enable as soon as patch is review +1 in lustre-reviews.&lt;br/&gt;
Code for Mellanox build has been verified on community cluster Juliette (FZ J&#252;lich) so far only.&lt;/li&gt;
	&lt;li&gt;Checked the execution of normal Lustre &apos;inkernel&apos; build in VM that run on top of a hypervisor with Mellanox OFED installed&lt;br/&gt;
and SR-IOV enabled. It pass all basic test (creation of FS, client file operations (create, remove, ...), small performance test)&lt;br/&gt;
This would increase the test coverage for &apos;inkernel&apos; and if available openfabric builds, too. Anyway some technical aspects (does&lt;br/&gt;
all user land libs and programs execute well without runtime surprises; especially for all MPI applications) has to clarified &lt;br/&gt;
and discussed.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="243184" author="mdiep" created="Fri, 1 Mar 2019 22:41:27 +0000"  >&lt;p&gt;closing due to we have IB support in our lbuild for a while now&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|hzvf9b:</customfieldvalue>

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