|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Enabling Golden System Comparison
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note: When q-Status is shipped, the Golden Compare CGI Administrative Programs are disabled (they are not executable). These CGI programs need to be enabled to use. To make them executable simple go to the Administrative CGI directory and use chmod as described below:
It is recommeded that if you are to enable these .cgi programs, that you also protect the "AdministrativeMenus" directory under q-Status with a password. To do this see "Authentication" for the Apache web server. |
Selecting this rollover will display the following page with the Golden System section:

Theses menus support the
- List Golden System Parameters
- Create Golden System Parameters
- Archive an Existing Golden Parameter Set
- Modify Golden System Parameters
- Delete Golden System Parameters
These menus are interactive and cross reference each other.
"Archive an Existing Golden Parameter Set" is similar to creating a baseline of the file. The original is still maintained with an assigned date to freeze the set for the archive.
Selecting the "Create Golden System Parameters" will display the following sub menu:

This submenu will allow the administrator to:
- Create a New Blank Parameter File
- Create a New Golden Parameter File from an Existing Golden Parameter File
- Archive an Existing Golden Parameter Set that is the same as in the main menu
- Use an Existing System Parameter (Patches and Packages) to generate a new Golden Parameter File
Using the last option to generate a parameter set from existing systems parameters will generate a list of all packages and patches from the selected system minus any obsolete patch references. These are quite long lists. Defining the list will then allow you to delete patches in the list. For obvious reasons, user-definable items are not supported. The user will then need to use the "Modify Golden System Parameters" to complete the new set. Any set can also be modified with a text editor instead of using the interface.
When using modify or making a new blank Parameter set, the user is presented with a GUI that will assign or update the set. The parameter set is broken down into four section. Each section has its own method for assignment as follows:

Each Golden Parameter File must contain a complete set of general parameters or it will not be a valid golden parameter file. This consist of the following items and their field length or list.
|
Name |
Description |
Format |
|
Title |
short name of parameters |
15 characters |
|
Description |
a description of the file |
20 characters |
|
Release Data |
release date of file |
mm/dd/yy |
|
OS |
Specific OS |
SunOS 5.7 |

Patch parameters can be defined for all platforms or for a single specific type platform. See valid systype table.
|
Name |
Description |
Format |
|
Patch Number |
a valid Sun patch number |
6 characters |
|
Revision |
a valid Sun patch revision number |
2 characters |
|
Platform |
platform type. All means any. |
valid systype |
|
Patch Description |
the patch description |
32 characters |
The patch number field value must be unique to this parameter file list for patches. You can not have multiple patch numbers with different revisions.

Package parameters can be defined for all platforms or for a single specific type platform. See valid systype table.
|
Name |
Description |
Format |
|
Golden |
package name (e.g. SUNWabc) |
15 characters |
|
Package Version |
version number from pkginfo -l |
32 characters |
|
Platform |
platform type. All means any. |
valid systype |
|
Package Description |
the patch description |
32 characters |
The values of Golden field (package name) and the Package Version field must be unique. You can not have multiple Golden fields with different versions.
The item fields are user definable. Item descriptions must be unique.

Item parameters can be defined for all platforms or for a single specific type platform. See valid systype table.
|
Name |
Description |
Format |
|
Version |
version of item |
20 characters |
|
Item Description |
unique field |
32 characters |
|
Platform |
platform type. All means any. |
valid systype |
|
Key |
scan field parameter |
20 characters |
|
Delimiter |
select delimiter See table below |
See table below |
|
Suffix |
suffix of file that contains the info |
10 characters |
|
: |
colon |
|
= |
equal |
|
/ |
slash |
|
\ |
backslash |
|
? |
question |
|
' |
tick |
|
" |
doubletick |
|
! |
exclamation |
In the example raw file below, there is a ITEM whose Item Description (TITLE) is "Sun Fire Controller". Its Version (VALUE) is "SMS 1.5". The Key value (KEY) is "SMS Version". The Delimiter (DELIMITER) is a colon (:). The Suffix (SUFFIX) of the file which contains the information is (.sms). Theses parameters are only valid for Sun Fire 15000 System controller (CP1500).
#ITEM|TITLE|VALUE|KEY|DELIMITER|SUFFIX|PLATFORM(S) ITEM|Sun Fire Controller|SMS 1.5|SMS Version|:|sms|CP1500 ITEM|OS Config|JS-0047.5y|OS_VERSION|:|sanconfig| |
The shell script below was written to generate an sms file by hostname with the "sms" suffix.
#!/usr/bin/csh
setenv DIR `/usr/bin/dirname $0`
setenv CFGDIR `/bin/cat $DIR/CFGDIR`
echo "SMS Version: ${SMSVERSION}" > ${CFGDIR}/data/`/usr/bin/hostname`\.sms
|
Note that the string "SMS Version:" becomes part of the output file as shown below:
SMS Version: 1.3 |
By defining a suffix, delimeter and key, Golden Compare will read this file report and perform comparisons with the golden value (VALUE) in the raw file above.
The Archive Set capability is used to maintain a history of the parameter sets assigned. They can be used to run comparisons, but most editing and update function are limited in the Administrative GUI. Only current sets are easily modified through the Administrative GUI. These Archive Sets are still modifiable with a text editor.