Original issue 939 created by arlake228 on 2014-06-25T13:10:31.000Z:
After the most recent round of builds to address the cacti fix, the LHC community wanted to know if there was an easy way to verify if their sites had yum-updated. It appears the only way to check is by hand right now:
The GUI shows the major/minor release, not the specific build (see attached). Since this suggestion could be complicated to implement, the end goals should be:
Way to tell the specific build of toolkit RPM via the GUI
Registration of the same into the LS for programatic searching
Right now we call 3.3.2 the 'version', and any toolkit RPM build that has this is lumped into that group. We will either need to:
treat the build number as a first class citizen (e.g. the page gets a new entry of build=16) or we bump the release each time there is a new build. Both have different connotations, but seem to hit the same goal.
arlake228
commented
9 years ago
Original issue 939 created by arlake228 on 2014-06-25T13:10:31.000Z:
After the most recent round of builds to address the cacti fix, the LHC community wanted to know if there was an easy way to verify if their sites had yum-updated. It appears the only way to check is by hand right now:
[zurawski@lhcmon ~]$ rpm -qa | grep PS-Toolkit perl-perfSONAR_PS-Toolkit-SystemEnvironment-3.3.2-16.pSPS.noarch perl-perfSONAR_PS-Toolkit-3.3.2-16.pSPS.noarch perl-perfSONAR_PS-Toolkit-LiveCD-3.3.2-16.pSPS.noarch
The GUI shows the major/minor release, not the specific build (see attached). Since this suggestion could be complicated to implement, the end goals should be:
Right now we call 3.3.2 the 'version', and any toolkit RPM build that has this is lumped into that group. We will either need to: