Welcome to the JET wiki space.
This page will be used to capture and disseminate information about the use of the Jumpstart Enterprise Toolkit.
What Is the Jumpstart Enterprise Toolkit ?
The Jumpstart Enterprise Toolkit is the name given to the Jumpstart Framework, developed by Michael Ramchand and Marty Lee within project 'RedBull'.
Amongst the aims of the RedBull project were to create a framework around Jumpstart that would simplify its deployment, as well as provide a basis to easily provision more complex installations automatically with minimal custom scripting on the part of the user.
JET 4.7 is available here
What are JET's main features
In a nutshell, JET provides a wrapper around Sun's installation technology to greatly simplify the provisioning of Solaris using Jumpstart.
After installing JET on you SPARC or x86 based Jumpstart server, you can:
- Install any of multiple versions of Solaris onto either SPARC or x86/x64 based clients.
- Deploy Flash archives.
- Utilise multiple boot methods: bootp, dhcp (including grub for x86/x64), and wanboot.
- Work across multiple subnets. (using a combination of methods)
- Install Recommended patches, or patch based on the EIS-DVD.
- Configure all your network interfaces.
- Mirror your root disk. (or set up ZFS boot)
- Configure Zones.
And much much more.
How does it work?
The main JET framework is supplied in a single Sun package called SUNWjet. This package contains everything necessary to do a standard Solaris installation using either bootp or dhcp.
Additional functionality is provided by additional modules, which are supplied in package format as well. Common additional packages include:
- JetSDS: Allows you to mirror your disks using SVM.
- JetEXPLO: Installs and configures explorer.
- JetFLASH: Allows Jet to install Flash Archives.
- JetVTS: Install Sun's Validation Test suite.
- JetSAN: Installs (on Sol 8 and 9) the SAN packages, and configures.
- JetJASS: Installs and configures Solaris Security Toolkit.
- JetZONES: Install and configures containers on Solaris 10 systems.
- JetLDOM: Install and configure Logical Domains on CMT based servers.
- JetWanBoot: Allows JET to act as a Wanboot server.
- JetISO: Use ISO images directly.
- JetRBAC: Allow non-root users to run JET.
- JetSBD: Configures Secure By Default
- JetZFS: Create ZFS pools, datasets and volumes.
When using JET for the first time, or initially setting things up, it's important to get the core framework running first, and to get comfortable with using JET before adding and configuring additional modules. Marty Lee wrote a good JET Primer here
JET User Guide
The JET User Guide has been converted to wiki format.
Quick Guides
Mirroring root disk using SVM
Using DHCP with JET
Jet and WanBoot
NFS-less JET
JET Resources
There are a few external resources for JET. The primary one is http://jet.maui.co.uk which is also a wiki, and run by one of JET's original co-authors.
There's also a mailing list/group (with almost 500 members) JetJumpstart Yahoo Group that you can subscribe to.
Tutorials
You will find a tutorial about Jumpstart Enterprise Toolkit at http://www.c0t0d0s0.org/plugin/tag/jet
Comments (2)
Sep 18
BrianJester says:
Michael, Any plans to serve up a bootable miniroot from a Windows machine so ou...Michael,
Any plans to serve up a bootable miniroot from a Windows machine so our SPARC boxes could WANBoot from it & centralize server (Windows & Solaris) deployment from a Windows box?
Brian Jester
Sep 19
mramchand says:
No plans per se. In a wanboot environment all you really need to do is place the...No plans per se. In a wanboot environment all you really need to do is place the right stuff in the right place on a webserver. JET does this for you using a combination of running the add_install_client script and some scripting. It would be trivial to put the media onto a windows based webserver. It would be non-trivial to re-write add_install_client for Windows.
In short, it is possible, but hard work.