> > I do have a jumpstart server right now with Solaris 8 and 9 images and
> > I do install all my new boxes using jumpstart. Then I have to go
> > through a list of applications that I have to install..
> > 2) Can I use the archive to install any 'sun4u' architecture clients?
> > (or)
> > If the archive was created out of Sun Fire V240 Can I use it only
> > for
> > V240's?
> 2) Yes, if master system is 'sun4u' and clones are 'sun4u' that's
> fine. It's not limited to "models", only kernel architecture.
It can get a little more dicey than that in some extreme examples. For
instance, if you were to install the archive you created on your V240 on a
F15K domain. There are F15K-specific tasks that the Solaris install
scripts will perform during a regular install, but not during a flash
install (e.g. domain-side IPsec configuration for certain intraframe
communications).
I personally think that this is something of a bug, and have argued it
with Sun, due to the fact that if I can perform a flash install on an E10K
domain, and E10K-specific actions are still taken (e.g. setting of
ssphostname). Sun doesn't see it that way, and if support issues come up
later, no matter how unrelated they may be, it's very likely that your use
of a flash archive to install Solaris on a different type of machine may
come up.
Anyway, my advice to Nicole is to reconsider using flash for the purpose
she describes, as I eventually did. For the reason discussed above, and
also because it leads to difficult revision control of your server-build
stack. I find it's much cleaner to simply use pure jumpstart, with finish
scripts and temporary startup scripts adding patches, packages, and making
other changes as necessary. This way, if you need to change something in
your build (e.g. upgrade SSH), it's simply a matter of swapping out a
package (moving a new file into place in your jumpstart configuration), as
opposed to going through the process of performing a flash install on a
spare machine, updating that machine, and creating a new archive.
You can see this gets even nastier when a new MU or version of Solaris is
released and you want to begin using that new image. You either have to
start from scratch and build a completely new flash archive (hope you kept
good notes!), or you need to perform an upgrade on an archive, as
described above, which effectively means that every machine you build
going forward will act as if it'd had an upgrade performed on it, as
opposed to a clean install, which isn't ideal.
I'm mainly speaking about flash technology as it existed a year or two
ago, so there may have been advancements I'm unaware of that mitigate some
of the situations I've described.
Hope this helps,
Ben