JumpStart Enterprise Toolkit quick How to
JumpStart Enterprise Toolkit (SUNWJET PACKAGE )
The JumpStart Enterprise Toolkit provides a framework to simplify and extend the JumpStart functionality provided within the Solaris Operating System.
How Jumpstart Works? (answer in one liner)
When ‘boot net’ command is issues at the client machine, it does a rarp broadcast to know its IP and the JET server to boot from. These details are kept in the /etc/ether file on the JET server. The main Client boot information is stored in the /etc/bootparams and sysidcfg file on the JET server.
Using the SUNWjet Toolkit
The toolkit is supplied as a number of Solaris packages that need to be added to the prospective JumpStart server. No Solaris or product media is supplied with the packages; these still need to be obtained through usual sources (CDs, and so on).
JET can be used to install Solaris on the Sparc and x86/64 platforms Quick-Start guide: (all steps performed as root)
1.Add the packages
# pkgadd -d SUNWjet.pkg
2.Add /opt/SUNWjet/bin to the path of the root user
3.Either:
a.run 'copy_solaris_media' to copy the Solaris image from CD/DVD to disk
b.run 'add_solaris_location' to inform the toolkit of existing Solaris images
4.Create a 'template' for a new client, using the 'make_template' command.
# make_template machine1
The toolkit provides a mechanism for creating a new template based on an existing one, through the use of the 'make_template' script.
For example, to create a new template for the target server 'apple' based on the existing server 'banana', you can do the following:
# make_template -T banana apple
5.Edit the new template and configure the build
# vi /opt/SUNWjet/Templates/machine1
6.Configure the build environment for this client
# make_client machine1
7.Start the build on the client:
(for Sparc)
ok boot net - install
(for x86/64)
Force a PXE boot
The JumpStart Enterprise Toolkit provides a framework to simplify and extend the JumpStart functionality provided within the Solaris Operating System.
How Jumpstart Works? (answer in one liner)
When ‘boot net’ command is issues at the client machine, it does a rarp broadcast to know its IP and the JET server to boot from. These details are kept in the /etc/ether file on the JET server. The main Client boot information is stored in the /etc/bootparams and sysidcfg file on the JET server.
Using the SUNWjet Toolkit
The toolkit is supplied as a number of Solaris packages that need to be added to the prospective JumpStart server. No Solaris or product media is supplied with the packages; these still need to be obtained through usual sources (CDs, and so on).
JET can be used to install Solaris on the Sparc and x86/64 platforms Quick-Start guide: (all steps performed as root)
1.Add the packages
# pkgadd -d SUNWjet.pkg
2.Add /opt/SUNWjet/bin to the path of the root user
3.Either:
a.run 'copy_solaris_media' to copy the Solaris image from CD/DVD to disk
b.run 'add_solaris_location' to inform the toolkit of existing Solaris images
4.Create a 'template' for a new client, using the 'make_template' command.
# make_template machine1
The toolkit provides a mechanism for creating a new template based on an existing one, through the use of the 'make_template' script.
For example, to create a new template for the target server 'apple' based on the existing server 'banana', you can do the following:
# make_template -T banana apple
5.Edit the new template and configure the build
# vi /opt/SUNWjet/Templates/machine1
6.Configure the build environment for this client
# make_client machine1
7.Start the build on the client:
(for Sparc)
ok boot net - install
(for x86/64)
Force a PXE boot
Comments