Hi Peter,

Peter Tribble wrote:
> On Fri, Jun 13, 2008 at 10:00 PM, Sarah Jelinek <Sarah.Jelinek at sun.com> 
> wrote:
>   
>>> 4.1: "complete automation support" leaves much to the imagination and
>>> room for differing interpretations.  I'd be more specific about what
>>> this means.
>>>
>>>       
>> I think we have discussed this in subsequent emails. We are trying to
>> say that AI won't barf or do the wrong thing, and we won't offer a text
>> based installer to ask the remaining questions, if some of the required
>> data is missing. This is 'all automated' all the time. And, if critical
>> data is missing we will not perform the install. We will however default
>> on some things, like default locale, if we can.
>>     
>
> So what does happen when something goes awry? Do we stop? (In which case
> telling the user what's missing, and giving them an opportunity to fix it, and
> then carry on, would seem appropriate.) Or panic? Reboot? (Into what state?)
>
>   
We halt the installer. Right now with the SXCE installer we bring up a 
text ui if the profile doesn't answer the questions we need to start the 
install/upgrade. We are not planning this, we are planning to have 
automation only, so we will have to specify the required options for a 
profile.
>>> 4.3: We're not providing upgrade in the interactive installer.  Why do
>>> we provide it here?
>>>
>>>       
>> I think we need to provide it here. The interactive installer targets a
>> different audience than AI does. Maybe it is the term 'upgrade' as
>> opposed to 'update'. I intend this to mean that we will allow for
>> 'updating' the system to the latest pkgs in the ips repo, via key,value
>> pair specification. I think enterprise customers would want this to
>> manage their servers.
>>     
>
> Enterprise customers want jumpstart, as it is now, pretty well.
>
> Within the context of AI/IPS, though, automated upgrade doesn't seem
> an obvious requirement to me. Why wouldn't you do all this from the
> running system?
>   
They could do it from a running system. But, they may not want to log in 
and do this, and they may have procedures in place which upgrade now via 
jumpstart, which means booting the clients. I don't think upgrade is a 
high priority and I think for the initial release which is a 
Preview(Nov) we will not provide this and get feedback from our users on 
this issue.


thanks,
sarah

Reply via email to