UAS Priorities and Supported Platforms

Official Policy Statement: UAS Priorities and Supported Platforms

30 April 1998

Making statements of priorities and policies is useless if we only say what we WILL do. We need to also say what we will NOT do if we are pressed for time/resources. In other words, we can't just list what is on the top of the list of priorities; we must also state what will fall off the bottom of the list.

Therefore, I am putting forth this policy on the platform support within the UAS group, which outlines which platforms will NOT be fully supported, and under what circumstances this will happen.

General outline: For each package, we will make an attempt to build it on all platforms. If it doesn't build/run easily, then we will drop support on some platforms (notably: AIX+3, AIX+4 except for farm applications, Linux+2 except for Fermi-specific and/or software that would greatly benefit from strong version tracking).

Specific outline: As of the release of ups v4_0x, UAS group will build our software packages following the priorities listed below.

Flavor Priority Guidelines
AIX+3 Absolute lowest priority. If it doesn't build real easily on the first try, then don't build it. This operating system will be removed from the supported list of OS's Real Soon Now, after which time we will no longer even attempt to build AIX+3 releases.
AIX+4 Extremely low. If it doesn't build easily, then don't build it. (Applications which are absolutely required for PC farms are exceptions).
IRIX+5 High. Required as long as either IRIX+5 is supported. Possibly longer.
IRIX+6 High. All IRIX+6 applications should be built with the -n32 option. If users need to link against an -o32 version, they should install and use the IRIX+5 release. See the "IRIX+6 Application Binary Interfaces" document, which was the basis for the FUE policy statement to this effect.
Linux+2 Medium. If it doesn't build real easily, AND it comes with Linux itself, then don't build it; if it's a Fermi-only supported product, then it must be ported to Linux. See the previously published UAS Linux Support Policy, as well as the Linux at Fermilab support statement from the Computing Division.
OSF1+V3 High. Required as long as OSF1+V3 is supported.
OSF1+V4 Medium. On the one hand, most OSF1+V3-built applications will run with no problem whatsoever on OSF1+V4. On the other hand, it is easier in the long run for us to just go ahead and build it, so that we can write automated scripts which do the same things on all fnalu nodes (instead of having a special case for how we declare OSF1+V4 products). Therefore, whenever possible, we will just go ahead and build an OSF1+V4 version.
SunOS+5 High. Required as long as SunOS+5 is supported.

Flavor	Priority	Guidelines
AIX+3	Absolute lowest priority.	If it doesn't build real easily on the first try, then don't build it. This operating system will be removed from the supported list of OS's Real Soon Now, after which time we will no longer even attempt to build AIX+3 releases.
AIX+4	Extremely low.	If it doesn't build easily, then don't build it. (Applications which are absolutely required for PC farms are exceptions).
IRIX+5	High.	Required as long as either IRIX+5 is supported. Possibly longer.
IRIX+6	High.	All IRIX+6 applications should be built with the -n32 option. If users need to link against an -o32 version, they should install and use the IRIX+5 release. See the "IRIX+6 Application Binary Interfaces" document, which was the basis for the FUE policy statement to this effect.
Linux+2	Medium.	If it doesn't build real easily, AND it comes with Linux itself, then don't build it; if it's a Fermi-only supported product, then it must be ported to Linux. See the previously published UAS Linux Support Policy, as well as the Linux at Fermilab support statement from the Computing Division.
OSF1+V3	High.	Required as long as OSF1+V3 is supported.
OSF1+V4	Medium.	On the one hand, most OSF1+V3-built applications will run with no problem whatsoever on OSF1+V4. On the other hand, it is easier in the long run for us to just go ahead and build it, so that we can write automated scripts which do the same things on all fnalu nodes (instead of having a special case for how we declare OSF1+V4 products). Therefore, whenever possible, we will just go ahead and build an OSF1+V4 version.
SunOS+5	High.	Required as long as SunOS+5 is supported.

This document updated on 30 April 1998.
Send comments to uas-group@fnal.gov.
Lauri Loebel Carpenter, uas group leader.