Set up Server with Depots and Install Clients

You can use most any system as your Ignite-UX server. You can have depots on your server for HP-UX 11i, 11.0, and 10.20. I would recommend using an 11.00 or 11i system as an Ignite-UX server because I have seen problems with a 10.20 system acting as a server for loading clients with 11.00 and 11i. I have never seen a problem with an 11.0 or 11i system acting as a server for loading clients with any version of HP-UX. In general, though, the server acts as a host for depots and its operating system is not an integral part of loading software onto clients. Ignite-UX is a versatile product. To demonstrate its flexibility, we'll use an 11.0 Ignite-UX server in this section to load 11.0 software to clients. We can create 11i and 10.20 depots as well. Although we'll use 11.0 in this section, the procedure for 11i is identical. Later in the chapter we'll recover Virtual Paritions (vPars) systems running 11i with Ignite -UX. We'll use a workstation (model J2240) running 11.00 in our examples in this section. From the 11.00 depot we create on this system, we can load a variety of clients. The fact that we're using a workstation rather than a server doesn't matter as far as loading clients is concerned . I find that many system administrators use a workstation as an Ignite-UX server even though they're loading primarily servers, such as N-Class systems.

The software depots you create on your Ignite-UX server consume a lot of disk space. A core operating system with many applications could take up several GBytes of disk space. I like to devote several GBytes of disk space to Ignite servers so I don't have to increase the size of /var (the default location for software depots) when additional depots are loaded on a system. My rule of thumb is /var at 6 GBytes to support several depots.

Just to give you an idea of the disk space consumed by depots, I have issued the following bdf commands upon initial system installation without any software depots and then again after creating a core operating system and application depot. The location of the software depots is /var by default; however, you can load the depots in any directory. I would recommend creating a file system such as /var/ depots as a depot area. In the following example, we'll focus on the capacity of /var , since it is used as the destination for depots in upcoming examples.

 #  bdf  Filesystem          kbytes    used   avail %used Mounted on /dev/vg00/lvol3     204800   19830  173464   10% / /dev/vg00/lvol1      83733   13654   61705   18% /stand /dev/vg00/lvol8    6553600  156292 5998347    3% /var /dev/vg00/lvol7     512000  341251  160127   68% /usr /dev/vg00/lvol4     102400    1522   94578    2% /tmp /dev/vg00/lvol6     602112  186976  389238   32% /opt /dev/vg00/lvol5     204800    1157  190923    1% /home /dev/dsk/c1t2d0    2457600  2457600        0  100% /var/tmp/cddirAAAa02574

The following bdf , which was taken immediately after the core operating system depot for 11.0 was created, shows that /var availability has been reduced to about 5.667 GBytes from 5.998 GBytes. This represents roughly 330 MBytes of data that were loaded as part of the core operating system.

 #  bdf  Filesystem          kbytes    used   avail %used Mounted on /dev/vg00/lvol3     204800   19943  173357   10% / /dev/vg00/lvol1      83733   13654   61705   18% /stand /dev/vg00/lvol8    6553600  507003 5668779    8% /var /dev/vg00/lvol7     512000  341255  160123   68% /usr /dev/vg00/lvol4     102400    3350   92862    3% /tmp /dev/vg00/lvol6     602112  186976  389238   32% /opt /dev/vg00/lvol5     204800    1157  190923    1% /home /dev/dsk/c1t2d0    2457600 2457600       0  100% /iuxcdrom0 #

The disk space consumed by the core operating system depot can be confirmed by viewing the location of the depot as shown in the following listing:

 #  cd   /var/opt/ignite/depots  #  du -s *  688842  Rel_B.11.00 #

This listing of the du command shows that roughly 330 MBytes (688K blocks divided by 2048 bytes/block) are in the core operating system directory. This 330 MBytes of disk space consumed by the core operating system depot is nothing compared with all of the application software we're going to load into the depots directory. We're going to put both the core operating system and applications in this directory, so substantially more space will be consumed.

To further drive home the point of the amount of disk space consumed, the following du command shows the amount of disk space consumed by both the core operating system depot (still about 330 MBytes) and the total applications contained on the three CD-ROMs that came with the release of the operating system for which we're creating our depots. The /var/opt/ignite/depots/app directory, which is the depot for the contents of the three application CD-ROMs, is roughly 3.7 GBytes!

 #  cd /var/opt/ignite/depots  #  du -s *  688874  Rel_B.11.00 3722622 app #

The space consumed by the applications is over 10 times the space consumed by the core operating system. This 3.7 GBytes consists of every application available for the 11.0 release of the operating system; however, this gives you an idea of the space required when using Ignite-UX to create depots.