Sarah Jelinek wrote: > > jan damborsky wrote: >> Hi Ethan, >> >> Ethan Quach wrote: >> >>> jan damborsky wrote: >>> >>> >>>> jan damborsky wrote: >>>> >>>> >>>>> Hi Sarah, >>>>> >>>>> I have tried to address your TI&TD questions. >>>>> Please see my comments in line. Where no explicitly >>>>> specified, they take into account requirements for >>>>> Slim October release. >>>>> >>>>> Thank you, >>>>> Jan >>>>> >>>>> >>>>> Sarah Jelinek wrote: >>>>> >>>>> >>>>>> -Whole disk or existing Solaris partition only acceptable targets is >>>>>> current >>>>>> requirement for Slim. >>>>>> >>>>>> -Target discovery via orchestrator will still returns all data, gui must >>>>>> filter >>>>>> appropriately. This results in no change to target discovery interfaces. >>>>>> However, this results in a potential performance issue since the >>>>>> discovery >>>>>> of upgrade instances is unnecessary. >>>>>> >>>>>> -We could separate out os discovery from this. Currently it is >>>>>> done after disk discovery via handle_disk_discovery. Should we do this? >>>>>> >>>>>> >>>>>> >>>>> I think that since Upgrade path won't be supported and information about >>>>> existing >>>>> OS instances would be left unused, discovery of OS instances might be >>>>> omitted. >>>>> >>>>> >>>> Actually, it seems this is not true. According to existing UI task list >>>> data about existing Solaris instances are available in October release. >>>> I am sorry for misleading information. >>>> >>>> >>> Hi Jan, which UI task list are you referring to here? I don't see this >>> on the UI Roadmap for October that Frank sent out. >>> >>> >> http://opensolaris.org/os/project/caiman/Slim_Install/uiroadmap/ >> >> This is mentioned in Desired: >> * Disks (install): Display Solaris environments in a Solaris partition >> >> I wasn't able to find it neither in roadmap posted on Open Solaris pages. >> Then I asked Jedy :-) >> >> Jedy is working on this feature for Slim October release. >> > I can't imagine we would worry about existing Solaris Instances for > October.
I don't either. > And, in looking at this list I don't see that this means > upgrade, or existing Solaris instances. I think it means existing > Solaris partitions will be supported. Yes, that should be clarified. Perhaps the 'desired' feature here was so that we'd be nice enough to let them know, "Hey, you're about to overwrite these existing Solaris instances we found on your drive." > > The issue is of course that we cannot upgrade from a previous release to > Slim. And, we cannot upgrade Slim to a newer build. So, we have to make > sure that we mark the Slim installations appropriately so they won't be > recognized as upgradeable instances. The lack of a /var/sadm/pkg/SUNWcsu does this I think. -ethan > And, we can't offer upgrade with > Slim since previous Solaris releases contain more and different contents. > > Regards, > sarah > **** >> Jan >> >> >>> -ethan >>> >>> >>> >>>> Thank you, >>>> Jan >>>> >>>> _______________________________________________ >>>> caiman-discuss mailing list >>>> caiman-discuss at opensolaris.org >>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>>> >>>> >>> _______________________________________________ >>> caiman-discuss mailing list >>> caiman-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>> >>> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >> >> > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
