HP 10 - Manual (Page 16)

Deployment planning 16
Deployment planning
Solaris installations proceed through three phases: boot, configuration, and software installation.
Each phase offers flexibility in implementation and can be customized for a variety of environments.
This chapter describes several common methods of implementing each phase and provides guidance
on selecting strategies that meet the requirements of most organizations.
This section describes the planning of deployment strategies where none exist. If ProLiant servers are
being integrated into an existing Solaris deployment environment, see “Deploying ProLiant servers,”
“Miniroot preparation,” and “JumpStart preparation.”
Selecting a deployment strategy
For purposes of this guide, a complete deployment strategy consists of a method of booting and
delivering the configuration and software packages. Use the following sections to select a deployment
strategy for the target environment.
Boot methods
PXE-based booting:
• Can be used in Solaris-only environments because Solaris can provide all the required services
• Can also be used to deploy other x86-based platforms that are not ProLiant platforms
• Can be used with existing x86 or Scalable Processor Architecture (SPARC) deployment
environments
• Manages deployment from the DHCP server
• Requires a PXE (DHCP/TFTP) server
Rapid Deployment Pack-initiated deployment:
• Can be used in mixed-operating system ProLiant environments
• Can be used to integrate Solaris deployments into existing ProLiant Windows and Linux
deployment environments
• Can be used to automate Smart Array configuration during deployment
• Can be used with an existing x86- or SPARC-hosted JumpStart server
• Manages deployment from the Rapid Deployment Pack deployment console
• Requires an Rapid Deployment Pack deployment server
Custom ISO-based booting:
• Can be used when neither PXE nor Rapid Deployment Pack are available nor desirable
• Can be used with existing SPARC deployment environments that do not require PXE boot services
• Can be used in Solaris-only environments
• Can be performed remotely using iLO virtual media
• Manages deployment from the physical or virtual system console
• Does not require a PXE or Rapid Deployment Pack server