8 primary build and apply process, Build a configuration revision, Chapter 8: primary build and apply process – HP Integrity NonStop H-Series User Manual
Page 109: Chapter 8, Primary build and apply process, Chapter 8: “primary build and apply process
8 Primary Build and Apply Process
After creating a new software revision, you build an activation package containing information
about all the products listed in your revision. After transferring the activation package to the target
system, the software is staged during the Apply process.
This section describes the primary (or normal) build/apply process typically used when migrating
to a new RVU. In this scenario, a user has created a new revision for a Target system that is
Expand-connected, has already been initialized, and is running a Current revision. The steps in
this normal process include:
•
“Build a Configuration Revision” (page 109)
•
“Prepare for a Build and Apply Request” (page 110)
•
“Initiate a Build/Apply Request” (page 111)
Other less typical build/apply processes involve many of those same steps, but include other
important considerations as well. For more information, see:
•
“Performing a Build/Apply When Host and Target are not Expand-connected” (page 129)
•
“Performing an Initialization Build/Apply” (page 134)
•
“Building and Applying a Clone Group Configuration Revision” (page 176)
.
Build a Configuration Revision
A planner uses NonStop Software Essentials to build a configuration revision for the new software
revision. The components of a new configuration revision build include:
•
The product versions named in the new software revision
•
A new operating system image if required. DSM/SCM runs system generation accordingly.
•
New SRL files or DLL files
•
Profile information, including the appropriate location for product files: the Target Subvolume
(TSV) for Guardian files and Target Directory Location (TDL) for OSS files (see
).
•
An activation package, which includes:
—
Pointers (if the systems are connected using Expand) to the product files in the archive for
the software to be installed. If the package is placed on tape or disk, the product files
themselves are included in the package.
NOTE:
While specifying which files to include in the package when you: if you include
all files and have the activation package written to disk, a very large amount of disk
space is needed to hold the entire RVU. For more information on specifying files to include
in the activation package (while initiating a Build/Apply request), see
—
The operator instructions, which the planner edited during the creation of the new software
revision.
—
Information needed by DSM/SCM to install the new software on the target system,
including the TSVs and TDLs where the software will be placed.
The process of performing the build includes:
•
Transferring the products listed in a software revision from the archive to the target system.
•
Merge the distribution files into executable or usable formats.
•
Create the activation package. If necessary, NonStop Software Essentials includes a new
operating system image produced by a system generation program.
Build a Configuration Revision 109