Hi Darren,
You proposal sounds good. I have a few questions
related to the specifics of implementing your proposal.
1) When the machine sits at the login prompt, there might be other
sys messages popping up. What will happen to those messages?
Are you going to re-direct them to somewhere? Will they just
pop up as usual? If you just allow them to get displayed, it
might disrupt the display of the AI progress messages, and make them
hard to read. Would it be beneficial to add some sort of prefix to
clearly identify those messages that are from AI?
2) For some of the progress messages, you have "." in them.
For example: "Installing from IPS ................... Done". Are those
dots generated as the progress of that action proceeds?
The progress reporting done by the engine is based on the set
of checkpoints that are being executed. I think AI is executing
all the registered checkpoints at once, right? If that's the case,
how will you be generate those dots to indicate progress?
Will it be done by the checkpoint? If so, seems like a duplication
of effort by the checkpoint since the checkpoint is already reporting
progress.
3) The progress reporting provided by the CUD will give
a percentage number and a message.
These information can be retrieved by the application
by registering a progress handler.
Can that be used instead of the customized log
handler? Regardless, I think that it will be useful to display the
percentage number somehow so the user knows
how much is completed?
4) Checkpoints are general, to be used by applications
other than AI. Would checkpoints have to be modified
to be aware of this customized log handler so
the right messages get displayed?
Thanks,
--Karen
On 12/08/10 02:54, Darren Kenny wrote:
Hi,
As part of the migration for AI to the CUD architecture, we are looking at at
how best to provide some progress information to the console, and I would like
to get peoples feedback on whether this meets their requirements or not.
The amount of information would be minimal, it's primarily to let people know
that an AI install is in progress, and that it's still working or has failed,
etc. Detailed logging is already being provided in the install log should that
be desired.
The current proposed solution is to provide a customized log handler that can
direct specific output to stderr, and the SMF service will in turn direct
stderr to the device /dev/sysmsg which will then direct any text output to the
console, and any auxiliary console devices.
This text would of course then be merged with any other text output to the
console - including the login: prompt.
My current assumption is that people won't be logging into the console usually
unless they have something specific to do - at the moment this tends to be to
check if the AI install service is actually running...
So if we output a couple of new-lines, and then start the logging, it would
look something like:
Successful Install:
login:
Starting Automated Installation at<DATE>
- Device Driver Updates for Live Environment
- Discovering Targets
- Selecting Target(s)
- Instantiating Target(s)
- Beginning Transfer Phase(s)
- Installing from IPS ................... Done
- Copying files ...... Done
- Transfers completed
- Applying Initial Target Configuration .... Done
- Installing Device Driver Updates to new Boot Environment ... Done
- Updating Boot Archive
- Transferring Logs to new Boot Environment
Automated Installation Completed Successfully at<DATE>
Rebooting...
Failed Install:
login:
Starting Automated Installation at<DATE>
- Device Driver Updates for Live Environment
- Discovering Targets
- ERROR: Failed to locate any suitable targets, further information
is available in the log at : /var/run/install_log
Automated Installation Failed at<DATE>
If someone was to want to still log in, then they can, by pressing RETURN,
which will result in the login: prompt being shown again.
It's not currently planned, but we could consider ceasing the logging to the
console once someone has logged in so as th not cause more noise there.
Does this sound like a runner to people, or do people feel that more is
required?
Thanks,
Darren.
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
