Hi Jon -

Your point is well taken.

This particular design is provides a framework for logging. However, the user interface design isn't part of logging.

The strength of this logging facility provided by python is that it's easy to extend the functionality as needed. If a user interface requires particular output, the logging module can be extended to capture whatever information is needed and deliver it to the consumer implementing the user interface.

For example, in the current design document, the implementation of the progress handler (which is in section 8 of the doc) delivers the progress messages to the progress receiver. What the progress receiver does with that information is outside of the scope of the logger.

thanks,

ginnie


On 05/17/10 01:45 PM, Jon K Aimone wrote:
Hi,

I understand, and I agree with direction this design is taking. I guess my concerns come from having not yet seen a corresponding document form expected early consumers (e.g. AI) showing use of this service and potential user interfaces presenting available data. I think section 12.2 leaves many open questions about what users would expect for visible output and available run-time controls on the target system during installation. This begs some user's perspective requirements and corresponding design.

Ginnie Wray said the following on 05/17/10 06:44 AM:
Hi Jon -

I appreciate your feedback and expressed concern.

The intent in the logging framework design is to provide a backend that is robust and flexible enough to interface with a diverse set of consumers. I think we achieve that with the Python logger, from my experiments and research. The ability to add different types of data handlers and formatters as what makes it so easy to use with different front ends.

Perhaps I haven't expressed that clearly enough in my design document?

ginnie


On 05/14/10 13:35, Jon K Aimone wrote:
Hi,

I'm a bit concerned that we've designed the back-end without a full understanding of the front-end requirements... but that's just my paranoid, customer perspective on quality and usability acting up again!

There I go... jumping that gun again. I know. O:-)

Dave Miner said the following on 05/14/10 07:25 AM:
On 05/13/10 08:31 PM, Jon K Aimone wrote:
Hi,

Is where another document somewhere that describes (or will describe)
how a user will interact with this facility to peruse, watch progress
and / or control the level of detail in the logs? And I believe these
need to be run-time control available to the user / operator, not
compile time control.

Today one must login to the system and tail files to see progress. What
will replace this process?

Or have I jumped the gun again?


Yup :-)

That's a function of the applications using the facility. The example you use above for AI is something the AI team will evaluate and address in due time (I know there's a bug for it, but don't remember the number offhand).

Dave

Ginnie Wray said the following on 05/13/10 02:17 PM:
Hi -

As a result of some additional research, I've updated sections of the
design document for the install logger. Sections 1 through 11 of the
document below have been updated. I have not revised any of the
material that pertain to remote logging.

http://hub.opensolaris.org/bin/view/Project+caiman/Logging

The current version is v1.3. I've also uploaded a UML diagram that is included in the document. It's a little small in the document, so you
can take a look with larger font using the online version. It is the
UML diagram v1.3.

I would like to have feedback by COB on May 24th, but I know we're all
busy, so anything beyond that deadline is appreciated as well.

Thanks,
ginnie

_______________________________________________
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


_______________________________________________
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

_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to