Hi Sarah, On Thu, 30 Jul 2009, Sarah Jelinek wrote:
> Hi Alok, > > Comments/questions below... I tried to to repeat what others have said, but > if I did, just tell me so... > > 1.2 Scope of the product: >> * Primary target is server installations that don't want to set up AI > This seems to indicate to me that the primary target for this is the text > based installer. Is this correct? The text installer could be used in such a situation or if a hands off installation is desired, the bootable AI can be used. But, in general, I agree that there is a bit of overlap between the two installers for above mentioned target audience. > Have we decided to combine the text > installer in with this image? If so, the text installer will be doing, if I > remember correctly, cpio installation. The first bullet in this section seems > to indicate that we will only do installation from an IPS network repo. The text installer image will be a separate image and will not be combined with the AI image. I believe that is captured in the text installer func spec. > nit: > 3.1, should say "following three(not two) choices" Got it. > In the case of VMC, how will the three grub menu options work? I assume VMC > will modify the menu.lst file to only have one entry and that entry contains > the value for the manifest? Correct. >> The first choice will be the default if none is selected by >> the user > > Where does the user specify the manifest for this choice? Or is this > pre-specified somehow? I assume this is default because we don't want to > automatically start AI in all cases. Which means that the user must specify > this somehow. The user will be prompted to provide a location for the manifest (path to, say, manifest on the flash drive or an http server). Yeah, this is the default choice because we don't want to overwrite a user's disk unless specified otherwise. > Section 3.4: > > Don't we already perform the lookup of the manifest in a separate service? Or > is this a new thing? I am just wondering how it compares to what we do today. In the current implementation, service discovery as well as invoking the auto-install binary are done as part of the auto-installer service. In the past, we've talked about splitting up these two functional areas into separate service (atleast in the context of derived manifests). Alok Alok
