Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-6677

Package lustre correctly for Fedora/RHEL

Details

    • Task
    • Resolution: Done
    • Minor
    • None
    • None
    • 9223372036854775807

    Description

      LLNL will be moving to RHEL7 on new systems in the not-too-distant-future. As part of the move, we are also transitioning to a new rpm build farm based on the standard Fedora Koji build system.

      We need Lustre to be correctly RPM packaged using modern RPM packaging best practices, and it needs to be buildable under Koji. Off the top of my head, there are two main initial things that need to change to meet that definition:

      1. Lustre must use some modern form of the kmod packaging standard to package its kernel modules
      2. Lustre must build with weak modules support

      Attachments

        Issue Links

          Activity

            [LU-6677] Package lustre correctly for Fedora/RHEL
            morrone Christopher Morrone (Inactive) made changes -
            Resolution New: Done [ 10000 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

            LU-5614 was only one of the components necessary. But yes, I think things are complete enough now to close this.

            morrone Christopher Morrone (Inactive) added a comment - LU-5614 was only one of the components necessary. But yes, I think things are complete enough now to close this.
            mdiep Minh Diep added a comment -

            Hi Chris,

            Is there anything else we need to do on this ticket? it seems like this is a dup of LU-5614

            mdiep Minh Diep added a comment - Hi Chris, Is there anything else we need to do on this ticket? it seems like this is a dup of LU-5614
            morrone Christopher Morrone (Inactive) made changes -
            Link Original: This issue is blocked by LU-3956 [ LU-3956 ]
            morrone Christopher Morrone (Inactive) made changes -
            Labels Original: llnl topllnl New: llnl
            pjones Peter Jones made changes -
            End date New: 15/Sep/15
            Start date New: 02/Jun/15
            npearl Nate Pearlstein (Inactive) made changes -
            Link New: This issue is related to SGI-131 [ SGI-131 ]
            pjones Peter Jones made changes -
            Link Original: This issue is related to JFC-10 [ JFC-10 ]
            jfc John Fuchs-Chesney (Inactive) made changes -
            Link New: This issue is related to JFC-10 [ JFC-10 ]
            mdiep Minh Diep added a comment -

            I could be wrong but both approaches are very similar. I tend to like the approach that uses a single spec file.
            Both will need some changes in the building infrastructure which need to install kernel-devel right on to the build node which is not too difficult to do.

            If there's a way to do without installing kernel-devel on the build node, it would be great.

            mdiep Minh Diep added a comment - I could be wrong but both approaches are very similar. I tend to like the approach that uses a single spec file. Both will need some changes in the building infrastructure which need to install kernel-devel right on to the build node which is not too difficult to do. If there's a way to do without installing kernel-devel on the build node, it would be great.

            People

              mdiep Minh Diep
              morrone Christopher Morrone (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: