Hi Joe,
On 03/30/09 17:23, Joseph J VLcek wrote: > jan damborsky wrote: >> There is a request from QE team as well as from users to allow >> process of installation to be observed remotely. For LiveCD case, >> this requirement was satisfied by fix for bug 6431 which introduced >> support for new configuration parameter 'livessh'. Is set to 'enable', >> ssh access is enabled to LiveCD environment. >> The same feature should be available for Automated Installation. >> >> Also, there is a need to be able to run the Automated Installer >> in debug verbose mode in cases when more information about >> installation process is desired - for instance when there is >> a failure to be evaluated or during testing. >> >> Based on this, there would be two parts to address those >> requirements: >> >> [1] enable ssh for AI >> --------------------- >> The suggestion is to take advantage of 'livessh' option introduced >> for LiveCD. If set to 'enable', AI would allow remote access >> using ssh by running following commands during boot: >> >> * generate ssh keys >> # /lib/svc/method/sshd -c >> >> * enable ssh SMF service >> # /usr/sbin/svcadm enable network/ssh >> >> [2] Enable debug verbose mode for Automated Installer >> ----------------------------------------------------- >> New option 'install_debug' would be introduced. If set >> to 'enable', AI engine would be run in verbose debug >> mode providing more information about installation process >> (captured in standard /tmp/install_log file). >> >> For x86, option would be defined in GRUB menu.lst file, >> it would be looked up in install.conf file for Sparc. >> >> Known Issues: >> ------------- >> Different mechanisms are used for x86 & Sparc - both have >> some disadvantages - please see bug 7789 for more details. >> Once bug 7789 is fixed, unified approach will be used >> for passing parameters for both architectures. >> >> Please let me know, if you think the proposal should be modified >> or different approach should be taken. >> >> Thank you very much, >> Jan >> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > > Hey Jan, > > Just to ensure it is understood: > > By selecting the LiveMedia GRUB entry: "Enable SSH", in addition to > enabling SSH, the defaults will automatically be chosen for the 2 > language questions and they will not be prompted for when booting > LiveMedia. Since there are no interactive screens for AI, the plan is to only enable ssh. > > > Is the proposed fix for bug 7789 to use a new file for passing > install configuration parameters to both SPARC and x86 AI clients? Yes, this is the intent. Just to clarify, fix for 7789 is not part of this proposal. > If so will the X86 AI client present an "Enable SSH" GRUB option? No, 'livessh=enable' would need to be added to the configuration file (to the $kernel line in menu.lst for x86 or to the install.conf file for Sparc). > > I think if the configuration file, proposed for fixing bug 7789, > contains a flag to "Enable SSH" then no GRUB entry should be presented > by the AI Client. The AI client should just boot with SSH enabled. There is no additional GRUB entry planned for this feature - it is assumed that the boot process would continue to be fully automatic as it is today. > > This would mean that the test folks could configure an AI service > that would provide the SSH enabled functionality. This would be > different from how their tests enable SSH for LiveMedia but I suspect > very workable. Yes, the implementation is planned to be different. The part of the reason is that there is no GRUB menu for Sparc and we would like to move to the unified approach used for both platforms. As far as populating configuration file with parameters is concerned, we currently don't have way to do it with installadm for Sparc, we can take advantage of -b option for x86 when creating new client. That means, parameters have to be added manually for Sparc or for x86 in cases when using '-b' is not suitable way (e.g. we don't want to make it client specific option). Thinking about this, it seems that fix for 7789 should also take care of this part of problem - how to add custom parameters to newly introduced configuration file. Thank you very much for your comments ! Jan
