[LU-17910] lustre-iokit should also follow the 'lustre_name'

• Type: Improvement
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.16.0
• Severity: 3
• Assignee: Shaun Tancheff
• Reporter: Shaun Tancheff

Description

Currently lustre-iokit does not follow the lustre_name scheme for alternate lustre naming.

Unless there is a reason to keep the package name hard coded let it follow the same naming scheme as the other packages ...

For example the following should be able to build all the packages with cray-lustre based naming

git clean -dfx > /dev/null 2>&1
sh ./autogen.sh
./configure --enable-dist
make lustre.spec lustre-dkms.spec dist Makefile
mkdir -p my_pkgs/SOURCES
cp -v rpm/* lustre-*.tar.* my_pkgs/SOURCES
rpmbuild --define "_topdir $(pwd)/my_pkgs" --define 'lustre_name cray-lustre' --without servers --ba lustre-dkms.spec
rpmbuild --define "_topdir $(pwd)/my_pkgs" --define 'lustre_name cray-lustre-client' --without servers --ba lustre.spec

# Dist packages:
find my_pkgs/RPMS my_pkgs/SRPMS -type f

Note the change in – define 'lustre_name cray-lustre-client' for lustre.spec and – define 'lustre_name cray-lustre' for lustre-dkms.spec due to the dkms build appending -client to the name.
The final packages names must align otherwise there are issues at installation due to package dependencies.