Hey Jan, * jan damborsky (Jan.Damborsky at Sun.COM) wrote: > Currently, when Automated Installation is done, it waits for user > to manually reboot the system. There is a desire to support > automatic reboot feature, so that the overall process of the > installation might be hands-off. This requirement is tracked > by bug 6556. > > In order to provide end user with possibility to automatically > reboot machine after AI is done, I am thinking about approach > described in proposal below. > > Please let me know, if you think it should be modified or different > approach should be taken. > > Thank you very much, > Jan > > > [1] introduce new element in AI manifest > > ... > <optional> > <element name="ai_auto_reboot"> > <data type="boolean"/> > </element> > </optional> > ... > > It would be optional - if not specified, machine would not reboot. > > [2] If 'ai_auto_reboot' option is provided and set > to 'true', AI would 'touch' file in /tmp/ directory > as indicator that auto reboot should take place. > > [3] Reboot in AI SMF service > > Reboot itself would be done from auto-installer SMF method as the > last action - after AI engine is done and only if it returned success > (in order to allow user inspect log files in case installer failed, > since they might be unaccessible after reboot):
And how are we going to handle clients whose boot order is always set to 'network' first? As I suggested on thursday last week, I think some sort of mechanism is needed for the ai_client to communicate to the ai_server that it's installation was successful so that the ai_server can disable the client (at least on x86, sparc clients we can set the boot order on the client). Cheers, -- Glenn
