Administration Guide

Modifying the file collection hierarchy

The delivered file collections have the default hierarchy shown in Figure 3. You can modify the hierarchy in several ways. One way is to make a given boot-install server function as the master server for a collection. This enables you to maintain a different set of files on a group of nodes that request their supper updates from that boot-install server. You do this by eliminating the logical path from the control workstation to the boot-install server for one or more boot-install collections. This is called taking the boot-install server offline and you do it with the supper offline command. Figure 6 shows a boot-install server that is offline for the power_system collection.

Figure 6. SP hierarchy of an offline boot-install server

View figure.

In this case, Boot-install Server A and Frame 1 get any changes made on the control workstation; Boot-install Server B and Frame 2 do not. Only changes made directly to the files on Boot-install Server B affect the files on Frame 2.

Note
Whenever you change the hierarchy, you must be aware of the location of the master files for every file collection. In Figure 6, there are two master file collections for power_system. The master files for the node.root collection on Frame 2 reside on Boot-install Server B and the master files for the node.root collection on Frame 1 reside on the control workstation.

If you want to change a file in the node.root collection for every node, you must make that change in two places, on Boot-install Server B and on the control workstation, and then run the supper update command on each node.
If you want to change a file in the node.root collection for just one frame of nodes, you must make that change in the master file collection for that frame, either Boot-install Server B or the control workstation, and then run the supper update command on each node in that one frame.

The following example shows you the procedure and commands to change the default hierarchy as represented in Figure 3. It shows you how to take the power_system collection offline, change a file in the node.root file collection, and distribute that update to the nodes on Frame 2.

Example

This example assumes that .profile is in the node.root file collection.

To take the boot-install server offline from the control workstation, log in to Boot-install Server B as root and enter:
```
   /var/sysman/supper offline power_system
```
On Boot-install Server B, modify the .profile in the /share/power/system/3.2 directory.
Remember, any changes made on the control workstation will not be updated on Boot-install Server B because it is offline. You must make the changes on Boot-install Server B.
Issue remote commands to update the node.root file collection on each of the nodes.
```
   /var/sysman/supper update node.root
```
Boot-install Server B no longer gets updated files from the control workstation. Unless you remove the supper command to update the power_system from the crontabs file on Boot-install Server B, the command will execute every hour and fail. Edit the crontabs file and remove:
```
   0 * * * * /var/sysman/supper update power_system 1>/dev/null 2>/dev/null
```

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]