Hi Sundar,
On 03/30/09 18:50, Sundar Yamunachari wrote: > jan damborsky wrote: >> Hi Sundar, >> >> >> On 03/30/09 18:26, Sundar Yamunachari wrote: >>> Jan, >>> >>> 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). >>> Is the option install_debug enables verbose/debug only for AI >>> engine or will it be passed to all libraries and other commands >>> (like pkg)? >> >> I originally considered to apply it only to AI engine, >> basically do the following: >> >> # export LS_DBG_LVL=4 >> # /usr/bin/auto-install -p <ai_manifest> > If the debug/verbose is turned on for AI engine, all the libraries > like libtd, lib orchestrator, libti and libtransfer also would have > debug/verbose on? yes - this setting will apply to all consumers of liblogsvc logging service. >> >> I am open to suggestions - do you think it might be useful >> to turn on debug mode for other pieces as well ? >> I agree that pkg(1) might be one of candidates - looking >> at its man page, some subcommands support verbose mode, >> e.g. 'install' or 'uninstall'. > I think turning the verbose for pkg is good idea. Currently pkg output > is not captured on the install_log. We need to fix that first to get > the output to install_log. See bug 4278. I have verified that this information is captured in /var/svc/log/application-auto-installer:default.log The reason that those messages don't go into /tmp/install_log is that transfer module calls Python logging module for capturing output from CLIs - pkg(1) in this case. I have taken a quick look at Python logging module and it seems to have appropriate mechanisms available if we would like to format those messages as done by logging service and redirect them to the /tmp/install_log. That said, I would rather postpone this change after 2009.06 - it might not be the low risk one, since it affects DC as well and tracks more new features for improving AI progress report. Given the fact that all log files are now available on installed system (since bug 4407 was fixed), I think it is not necessary to have 4278 fixed for taking advantage of 4443. Please let me know, what you think. Thank you very much, Jan
