How do I easily upgrade the RPMs installed on the Phi

[JJK]

Hi all,

I just saw the hotfixes released for mpss 3.[345].  Currently I've got a few RPMs from the mpss-<VERSION>-k1om.tar package installed on my Phi's and I am wondering what the best upgrade path for those is. I'm using

$  cat /etc/mpss/conf.d/rpm.conf
Overlay rpm /var/mpss/rpm on

and install the RPMs in /var/mpss/rpm using trial and error - that is, I have to figure out the RPM dependencies by looking at whether they install on the Phi.

My question now is: is there an easy, hopefully automatic, way to upgrade these RPMs together with the mpss-* and glibc-* rpms for each release ? I can write some magic bash/perl script to determine the dependencies from the set of RPM files but before I go down that path I'd like to know if there's a better way.

Note that simply installing ALL rpms is not an option, as that chews up the previous GDDR memory that's on the Phi's - if there's an easy way to run a Phi off an NFS disk then that might also be a solution (and save me some precious MIC-RAM in the process :) )

Host OS used is Scientific Linux 6.6 which is working fine for me as an RHEL6 clone.

TIA,

JJK

[Frances_R_Intel]

For the MPSS in general, it is recommended that you use the uninstall script in the old mpss directory to completely uninstall the rpms for the old version, then do a fresh install of the new version, instead of trying to upgrade. As far as the /var/mpss/rpm and /etc/mpss/conf.d/rpm.conf, those will remain unchanged by the uninstall and reinstall process (and the files /etc/mpss/micN.conf and /etc/mpss/default.conf will not change until you rerun micctrl --initdefaults, which is recommended.) I suspect that none of the rpm files you have placed in /var/mpss/rpm will be different in the new release, except for the version number. I would make a /var/mpss/rpm.new directory, then for each file in /var/mpss/rpm, copy the corresponding file from the k1om directory in the new release to the rpm.new directory, move rpm to rpm.old and rpm.new to rpm. In other words, as you have said, right a little shell script.

[JJK]

Hi Francis,

thanks for the info; actually, I usually just upgrade the RPMs instead of removing the old install ...

I'll look into writing a script to do the phi-side rpm upgrade. It's actually a non-trivial exercise, as it's hard to find the rpm name and version number (looking at the filename won't do) and I will need to check if any dependencies changed between upgrades.

As a side question: where can I find the gpg public key that was used to sign the RPMs ? my SL6 box keeps complaining about a missing signing key when querying the k1om rpms.

[Frances_R_Intel]

As far as just upgrading the RPMs, given your level of experience, you can probably back things out if you get into trouble. I would still recommend against it but as you wish.

As to writing the script, I'm sorry I don't have a better answer for you. However, most of the files in the k1om directory do not change versions from release to release. So, perhaps the best thing is not to worry about it - check to see if the file names in your rpm directory have an exact match in the k1om directory and just worry about the ones that don't.

As to the signing key, as I understand it, the files aren't signed. I think that is what it is complaining about.