Network Installation Manager

Network Installation Management (NIM ) is a client-server -based framework for software management and provisioning for the IBM AIX operating system.

Function

The system consists of a central NIM server keeps a number of installable software packages necessary for their installation and facilities. All resources ( client, network, packages, ... ) are managed in a separate database. From this server from other systems, NIM clients are called, operated via network connections.

With NIM following operations can be performed:

  • Installation of the base operating system (AIX or Linux ) using the Bootstrap Protocol and TFTP
  • Importing or performing a system backup to restore or cloning
  • Installing Optional Software
  • Update of software already installed

The last three points put on NFS as a means of data distribution.

NIM compatible with techniques such as alt_disk_install or alt_disk_migration and their successors Multibos. Also nodes in HACMP or PowerHA clusters can be provisioned using NIM. The system allows the parallel execution of a specific operation on an entire group of clients, which allows the roll-out of software on all environments.

Architecture

The NIM server maintains a database in the ODM format, all data necessary for its function. These are in particular:

  • Installable software (see below)
  • Dependent on the particular server client systems and their properties
  • Networks via which the client can be addressed

Clients

The system can be used to provide systems such as the X term, but the common use is the provisioning of stand alone in the NIM nomenclature systems mentioned: ordinary machines (LPARs or physical machines ), which differ only by their relationship to the NIM Server distinguished. In order to do its work, the NIM server must be able, either via remote shell or from a NIM own equivalent, nimsh, on the client command (as root ) execute.

Software resources

The three most important for the administrator types of software resources are: LPP source, SPOT and mksysb. In addition, there are several other species (eg the boot ROMs for different types of machines to boot systems can externally ) to take care of the system on the whole self.

LPP source

Is a collection of installable packages ( bff format or rpm) with a name in order to manage the collection as an entity can. From such a collection away software packages can be installed or placed by updates to a different version level. It is possible with NIM resources in an LPP source as in a virtual system to " install ", so that the resource can also be edited using the tools of software maintenance themselves.

SPOT

SPOT stands for shared product object tree and is, strictly speaking, the equivalent of a - geshareten - / usr directory. It is eg. at XTerms NFS mount instead of a local disk. For standalone systems, it is used during the initial installation to generate a Ursystems, similar to the initramfs for the Linux installation. Also, the SPOT can - be installed and updated - with an LPP source as the source.

Mksysb

The mksysb is a bootable image of a complete, installed operating system produced ( along with some additional information is essentially a savevg rootvg ) and is from the same command. There are two basic ways to use mksysbs: to create a golden image and uses this to provide all other systems with a basic installation, which you can then individualized by further software installations, depending on the intended use of the system. In addition, you can also generate a running system with NIM resources such mksysb image and save it on the NIM server, so that in case of failure a fully configured backup is available very quickly and must be applied only to new hardware. The pre -preserved on the NIM server mksysb can be used to remote the target system to boot as well as to install.

Bundles

There is also the option of combining single installable packages to so-called bundles that can then be applied together on one or more client ( s ). The definition is done via simple ASCII files in which the packages are listed. Unlike LPP sources, mostly with an entire operating system version or revision (eg a maintenance level or technical level, a service pack or the like) Bundles are usually created for a specific Zeweck, such as a version of a particular driver package.

Expiration of a system installation

First, the resources to be used (typically a mksysb ) unlocked and stored by the system on the NIM server under / tftpboot. Thereafter, the target machine is started, and the boot PROMs provide for the initiation of a bootp sequence that assigns the machine 's IP address. Then transfer a rudimentary initial system via tftp. This system starts and takes over the further installation of the system stored in the mksysb image.

Expiration of a software installation or an update

First, the resources to be used (typically a LPP Source) enabled. The NIM commands automatically provide the appropriate NFS shares in / etc / exports. The then following operations can be performed both from the machine as well as from the NIM server: the shared resource is mounted via NFS, then the software using the normal means of package management ( installp and / or RPM Package Manager) is installed or updated, then the NFS share again left.

Software framework IBM AIX Trivial File Transfer Protocol Network File System IBM High Availability Cluster Multiprocessing Logical partition (virtual computing platform)
598494
de