1 year in the case of the customer I'm at. Most customers have minimum 6 month
cycles and they spend 6 months trying it out before they release it. The 
specific bits 
they picked would need to be available in the repository for at least 1.5 
years. Do we 
plan on doing that?

Jim Litchfield

----- Original Message -----
From: Mike Dotson <[email protected]>
Date: Wednesday, March 25, 2009 2:26 pm
Subject: Re: [desktop-discuss] Does the AI opensolaris autoinstallation have 
the post script    just like the postscripts in the jumpstart
To: Shawn Walker <swalker at opensolaris.org>
Cc: Frank Fitch <Frank.Fitch at Sun.COM>, James Litchfield <James.Litchfield at 
Sun.COM>, Glenn.Lagasse at Sun.COM, "Eric J. Ray" <Eric.Ray at Sun.COM>, 
Casper.Dik at Sun.COM, Jon.Aimone at Sun.COM, desktop-discuss at 
opensolaris.org, nv-users at sun.com, Lubomir Sedlacik <Lubomir.Sedlacik at 
Sun.COM>, nv_re at sun.com


> On Wed, 2009-03-25 at 16:03 -0500, Shawn Walker wrote:
> > Frank Fitch wrote:
> > > Shawn Walker wrote:
> > > 
> > >>
> > >> Patches no longer exist in the IPS era.  
> > > 
> > > slight correction
> > > 
> > > *solaris* patches longer exist in the IPS era.
> > 
> > The context or implication was Solaris patches, so I assumed as such.
> > 
> > ...
> > > And, whatever you call them, we are going to have to install 
> updates to 
> > > solaris bits during the install.
> > 
> > Those updates are just packages, which again is controlled by the 
> > manifest, etc.  So the manual patchadd thing of the past does not apply.
> > 
> > ...
> > > If you want folks to use your tool, you have to make the tool 
> usable. An 
> > > install tool without the ability to completely customize installs 
> is 
> > > like a race car without wheels. Sure, it looks real pretty, and 
> may in 
> > > theory be the best car in the race. But it probably won't win.
> > 
> > I can neither confirm nor deny your assertions ;)  With that said, I 
> was 
> > just trying to point out that many of the reasons that some people 
> might 
> > have for needing this sort of scripting are no longer applicable. 
> 
> 
> > Specifically, when it comes to managing which *Solaris* software is 
> 
> > installed, there should be no need for scripting.
> 
> Really?  Are you sure?  
> 
> So if I as a customer purchase different types of systems, one that's 
> a
> database server based on x4600's and m9000's, one thats an application
> system based on x4200's and a web tier based on brand X systems, they're
> all supposed to magically know what image to install without scripting?
> 
> Now say the customer has one based on OpenSolaris 2008.5, and the other
> two based on OpenSolaris 2008.11 because that's what they have qualified
> for.  
> 
> And of course your going to allow for automatic repository configuration
> of the system to the Sun support repository with proper keys and
> passwords, etc, based on support contract for that system.  
> 
> And how are you going to provide installation of a system with same
> *Solaris* levels as a system installed 3 or 6 months ago because that's
> what the customer has qualified but the repos have been updated?
> 
> 
> > 
> > Cheers,
> -- 
> Thanks...
> 
> 
> Mike Dotson
> Area Technical Engineer - ACS West
> Phone: (503) 343-5157
> Mike.Dotson at Sun.Com
> 

Reply via email to