![]() ![]() ![]() ![]() In the case of a non-interactive install, the bootparams file also contains information about the location of the JumpStart scripts, and the sysidcfg file for that particular target server. The main boot information is stored in the /etc/bootparams file on the JumpStart server. The Solaris supplied script 'add_install_client' performs the function of defining the boot server, the location and type of the operating system image, and adds the target servers ethernet address to the local '/etc/ethers' file for the rarpd daemon to use. When a 'boot net' command is issued at the target servers OBP prompt, the target server starts to broadcast on the network, firstly through the RARP protocol, so it can establish its IP address and then for a boot server from which to boot the Solaris Operating Environment. When a target server is being jumpstarted, the following steps are performed: Provide a library of common functions which are used by both the scripts within the toolkit and any additional product modules, in order to reduce code repetition.Īlthough the aim of this document is not to provide an in depth description of the JumpStart technology, this section aims to refresh the reader with the most pertinent points about JumpStart.Set up a target server configuration by specifying the products to be installed and the installation parameters for each of them. ![]() Configure the JumpStart server and populate the server with media and patches.The toolkit provides a set of utilities which are used in the following areas: Detailed product knowledge of JumpStart or additional products should not be required to automate the build of servers this does not however preclude the concept of understanding a product in order to configure it properly only that the installer does not need to know all the installation commands for every product. Intuitive: The configuration of a target server should require the minimum effort on the part of the installer.This provides a variety of benefits such as the ability to update single products or add new ones without impacting the existing configurations. Modular: There should be a separation between the toolkit itself, the installable products, and the target server configurations.The toolkit should allow multiple identical target servers to be configured as well as many different configurations within the same framework. Flexible: The toolkit must be flexible enough to support a variety of target server types.The result was the creation of the JumpStart Enterprise Toolkit, which was developed to be Sun Professional Services UK recognised the benefits of JumpStart but also saw the need to automate the installation and configuration of common applications such as volume manager software and third party or unbundled packages. JumpStart makes use of a client- server architecture, where an install server is created that is able to deliver the Solaris Operating Environment packages to a target machine (a client) over a local networkįunctionality was also coded so that an administrator could fine tune the configuration and add additional packages through the use of a post-installation script, but this often involved quite complex scripting and in depth product knowledge, to the extent that getting it to work correctly often took far longer than a comparable install by hand. JumpStart was developed by Sun Microsystems to automate the installation of the Solaris Operating Environment over a network. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |