* Joseph J. VLcek (Joseph.Vlcek at Sun.COM) wrote: > Alok Aggarwal wrote: > >I have posted the first draft of the Bootable AI Image > >functional specification at - > > > >http://www.opensolaris.org/os/project/caiman/Bootable_AI_Image/bootable.ai.spec.txt > > > > > >Please take a look and provide feedback by COB, Thursday > >July 30th. > > > >Thanks, > >Alok > >_______________________________________________ > >caiman-discuss mailing list > >caiman-discuss at opensolaris.org > >http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > Hey Alok, > > Here is my feedback. It is mostly related to the usability of the > Bootable AI Client by VMC. > > Joe > > - - - > > Issue 1: > -------- > > 3.1 Booting an AI image from media > > The VMC project had planned that the default would be > what you list as: > > * Boot from media and invoke AI with a default manifest > > As we discussed it will be possible to modify the image to > set this choice as the default for VMC. > > This task has not been planned as part of the VMC work. The > method to modify the default GRUB selection will be needed.
True. But as we discussed last week, the reason for the change in the default boot target makes a lot of sense for the non-VMC case. I think we'll just need to adjust the VMC project plan to include the work to make the media usable. This change has benefits for VMC. We don't have to replicate building AI media as part of VMC. > Can I ask you to provide a script that will do this that > the VMC can use? Or maybe just helping us with this task... This should be fairly straight-forward. Installadm create-service does something very similar to what we (VMC) will need to do by putting the contents of the AI src image onto the filesystem so it can be served to network clients. We'll need to do that, then modify the grub menu for the image and possibly supply a new AI client manifest (if the user doesn't want the default) and then package it all back up into an ISO so we can boot our virtual machine with it. > Issue 2: > -------- > > 3.3 live-fs-root SMF service refactoring > and > 3.4 auto-installer service refactoring > > Can you please elaborate a bit on what will be done. > > Issue 3: > -------- > > Just to clearify: For VMC providing a modified AI manifest would > require that manifest to be built into the image. It will not > be possible for the user to select a manifest at boot time as > control of the boot process will be in a headless virtual machine. > > So the default manifest should be suited to the needs of the VMC > project. The current AI default manifest will meet these needs. > > Issue 4: > -------- > > 5.2 Scenario Two > > This will require the user to select a non-default GRUB option > for x86 boot correct? > > The VMC project requires this scenario to not exect any user > input, including selecting of an optional GRUB menu. > > See my comments at "Issue 1" above. > > Issue 5: > -------- > > Status and Observability > > How will the bootable AI client provide progress status and > observability into possible failures, specifically to the VMC? AI observability isn't part of this project so this is out of scope. The AI completeness work should cover this. Cheers, -- Glenn
