By scottdickson on Apr 29, 2009
Jumpstart makes use of rules to decide how to install a particular system, based on its architecture, network connectivity, hostname, disk and memory capacity, or any of a number of other parameters. The rules select a profile that determines what will be installed on that system and where it will come from. Scripts can be inserted before and after the installation for further customization. To help manage the profiles and post-installation customization, Mike Ramchand has produced a fabulous tool, the Jumpstart Enterprise Toolkit (JET).
My Questions for YouAs a long time Solaris admin, I have been a fan of Jumpstart for years and years. As an SE visiting many cool companies, I have seen people do really interesting things with Jumptstart. I want to capture how people use Jumpstart in the real world - not just the world of those who create the product. I know that people come up with new and unique ways of using the tools that we create in ways we would never imagine.
For example, I once installed 600 systems with SunOS 4.1.4 in less than a week using Jumpstart - remember that Jumpstart never supported SunOS 4.1.4.
But, I am not just looking for the weird stories. I want to know what Jumpstart features you use. I'll follow this up with extra, detailed questions around Jumpstart Flash, WAN Boot, DHCP vs. RARP. But I want to start with just some basics about Jumpstart.
Lacking a polling mechanism here at blogs.sun.com, you can just enter your responses as a comment. Or you can answer these questions at SurveyMonkey here. Or drop me a note at scott.dickson at sun.com.
- How do you install Solaris systems in your environment?
- I use Jumpstart
- I use DVD or CD media
- I do something else - please tell me about it
- Do you have a system for automating your jumpstart configurations?
- Yes, we have written our own
- Yes, we use JET
- Yes, we use xVM OpCenter
- No, we do interactive installations via Jumpstart. We just use Jumpstart to get the bits to the client.
- What system architectures do you support with Jumpstart?
- Do you use a sysidcfg file to answer the system identification questions - hostname, network, IP address, naming
- No, I answer these interactively
- Yes, I hand-craft a sysidcfg file
- Yes, but it is created via the Jumpstart automation tools
- Do you use WANboot? I'll follow up with more questions on this at a later time.
- What's Wanboot?
- I have heard of it, but have never used it
- We rely on Wanboot
- Do you use Jumpstart Flash? More questions on this later, too
- Never heard of it
- We sometimes use Flash
- We live and breathe Flash
- What sort of rules do you include in your rules file?
- We do interactive installations and don't use a rules file
- We use the rules files generated by our automation tools, like JET
- We have a common rules file for all Jumpstarts based on hostname
- We use not only hostnames but also other parameters to determine which rule to use for installation
- Do you use begin scripts?
- We use them to create derived profiles for installation
- We use them some other way
- Do you use finish scripts
- We use the finish scripts created by our automation
- We use finish scripts to do some minor cleanup
- We do extensive post-installation customization via finish scripts. If so, please tell me about it.
- Do you customize the list of packages to be installed via Jumpstart?
- Not only do we customize the list of packages, but we create custom packages for our installation