[LU-6379] Please name the RHEL repos using the $releasever yum variable Created: 18/Mar/15  Updated: 05/Apr/15  Resolved: 05/Apr/15

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.7.0
Fix Version/s: Lustre 2.8.0

Type: Improvement Priority: Minor
Reporter: Marcin Dulak Assignee: Minh Diep
Resolution: Not a Bug Votes: 1
Labels: None
Environment:

RHEL6, RHEL7


Epic/Theme: repo, rhel, yum
Rank (Obsolete): 9223372036854775807

 Description   

The lustre 2.7.0 release stores RPMS for RHEL6 under: https://downloads.hpdd.intel.com/public/lustre/lustre-2.7.0/el6.6

This path is inflexible and cannot be generalized for future RHEL 6 minor release updates (6.X), as there exist no yum variable specifying X.

Solution:

  • provide a symbolic link el6 -> el6.6, which points to the latest release.

After that change the lustre yum repo file can just contain for any RHEL version, e.g. for the server :
...
baseurl=https://downloads.hpdd.intel.com/public/lustre/lustre-2.7.0/el$releasever/server
...

Users who want to stay with 6.6 build of lustre will be able to use the explicit:
.../latest-feature-release/el6.6

This is the method used for handling minor releases by the official CentOS repositories: http://mirror.centos.org/centos/

A similar problem exist for https://downloads.hpdd.intel.com/public/lustre/lustre-2.7.0/el7
which should be a link to 7.0.1406 or whatever version of RHEL 7 lustre has been built against.

For more information about yum variables see: unix.stackexchange.com/questions/19701/yum-how-can-i-view-variables-like-releasever-basearch-yum0



 Comments   
Comment by Minh Diep [ 31/Mar/15 ]

Hi Marcin

I have made the change, could you verify?

Comment by Marcin Dulak [ 04/Apr/15 ]

It looks OK for me - the directory structure of https://downloads.hpdd.intel.com/public/lustre/

{latest-feature-release,lustre-2.7.0}

contains subdirectories named with el$releasever for both RHEL 6 and 7.

Comment by Peter Jones [ 05/Apr/15 ]

Great - thanks for confirming Marcin.

Generated at Sat Feb 10 01:59:42 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.