<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:15:10 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-1273] lbuild-sles11 and self-service capabilities</title>
                <link>https://jira.whamcloud.com/browse/LU-1273</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Currently, lbuild-sles11 is unable to service build requests for kernels that haven&apos;t already been downloaded by hand into lbuild-data.  The package/repo management for SLES has made this difficult, as the command-line tools provided (zypper, yast) don&apos;t work very well for package download (zypper requires root privileges, even for download-only mode), yast is just a frontend for their curses-based system management tool.&lt;/p&gt;

&lt;p&gt;We do now have a local cobbler mirror of SLES11 updates (&lt;a href=&quot;http://cobbler.lab.whamcloud.com/cobbler/repo_mirror/updates-sles11.1-x86_64/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://cobbler.lab.whamcloud.com/cobbler/repo_mirror/updates-sles11.1-x86_64/&lt;/a&gt;) which is periodically refreshed.  In theory, we ought to be able to teach lbuild-sles11 to use wget/curl to grab the kernel packages it requires from this local mirror.&lt;/p&gt;

&lt;p&gt;This may or may not be desirable, in that it would introduce a dependency on the environment we have set up locally.  Perhaps it could be generalized a bit to default to our local mirror URL, but be overridable via an environment variable (e.g. SLES11_MIRROR_URL=${SLES11_MIRROR_URL:-&lt;a href=&quot;http://cobbler.lab.whamcloud.com/cobbler/repo_mirror/updates-sles11.1-x86_64/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://cobbler.lab.whamcloud.com/cobbler/repo_mirror/updates-sles11.1-x86_64/&lt;/a&gt;}) which at least gives outsiders a chance to set up their own mirror and use it without needing to modify lbuild-sles11 locally.&lt;/p&gt;

&lt;p&gt;Or we could just keep doing things by hand, with a documented process for dealing with sles kernel updates.&lt;/p&gt;</description>
                <environment></environment>
        <key id="13805">LU-1273</key>
            <summary>lbuild-sles11 and self-service capabilities</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</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="10000">Done</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="mjmac">Michael MacDonald</reporter>
                        <labels>
                    </labels>
                <created>Fri, 30 Mar 2012 10:10:02 +0000</created>
                <updated>Mon, 29 May 2017 04:11:08 +0000</updated>
                            <resolved>Mon, 29 May 2017 04:11:07 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="32927" author="brian" created="Fri, 30 Mar 2012 11:19:22 +0000"  >&lt;p&gt;Having a local mirror location externally overridable, &lt;em&gt;AND&lt;/em&gt; having a reasonable failure mode in the case where a local mirror is not available would not be too objectionable.&lt;/p&gt;

&lt;p&gt;I do question though whether a location internal to our lab should be committed to the public repo.  Perhaps the mirror location in the code should be undefined and everyone has to provide it externally and we just add that external specification to our jenkin&apos;s call to lbuild.&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|hzvb87:</customfieldvalue>

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