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-3465 Lustre <p>Changes to the build system were made to allow for Intel MIC installations, which seem to require installing lustre in odd paths. I'm not entirely comfortable with our current solution. One of the main requirements seems to be that Lustre (included the kernel modules) needs to be installed in a non-standard filesystem root. </p> <p>I wonder if it isn't possible to achieve that goal through more standard means. For instance, we could make Lustre packages relocatable, and then use standard rpm --root, --dbpath, --relocate, and --prefix options at installation time to install the package into a non-standard location.</p> <p>I believe that Cray also installs lustre in non-standard subdirectories, so perhaps we can come up with a non-MIC-specific solution that works for multiple people.</p> LU-3465

Reevaluate method for installing rpms in different root

Technical task LU-1199 Minor Closed Duplicate Minh Diep Christopher Morrone Wed, 12 Jun 2013 20:59:04 +0000 Mon, 16 Sep 2013 22:33:04 +0000 Mon, 16 Sep 2013 22:33:04 +0000 Lustre 2.5.0 0 8 <p>I know of no situation or reason where we (HPDD) install Lustre in "odd paths". Can you provide any examples?</p> <p>Are you aware of the new MIC work? <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=morrone" class="user-hover" rel="morrone">morrone</a>: I have not been paying attention to what's landing for it. I only found a0a72a9f47f85250cdbfdf4ef2e760425bd013ac/<a href="https://jira.whamcloud.com/browse/LU-2752" title="Enhance build for cross compilation for the Intel(R) Xeon Phi(TM) card" class="issue-link" data-issue-key="LU-2752"><del>LU-2752</del></a> but that doesn't seem to affect packaging just cross-compiling. Sorry to be showing up late to the party, but can you be specific about which changes you are talking about that are causing the use of "odd paths"?</p> <p>Things like the new %{?rootdir}/ custom prefix that have been added in the spec file.</p> <p>Hrm, yeah. I had not seen that before it landed. I too would prefer some investigation into relocatable RPMs rather than customizing RPMs to "odd paths".</p> <p>Minh can you please review this suggestion to understand what would be required? thanks Peter</p> <p>Chris,<br/> Right now we have file installed in /usr, /lib, /sbin/, /etc. Is it feasible, possible to make them relocatable?</p> <p>I don't know, that is exactly the question that needs to be answered.</p> <p>Duplicate of <a href="https://jira.whamcloud.com/browse/LU-3958" title="Reevaluate method for installing rpms in different root" class="issue-link" data-issue-key="LU-3958"><del>LU-3958</del></a></p> Related LU-3958 Development Rank 1|hzvt6v: Rank (Obsolete) 8662