[
https://issues.apache.org/jira/browse/WHIRR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated WHIRR-106:
----------------------------
Attachment: WHIRR-106.patch
* Added logging to each service. This is at info level, and is useful for a
fairly high-level view of what Whirr is doing.
* The CLI now logs info level to the console and everything else (for
org.apache.whirr and jclouds.compute categories) to a file called whirr.log.
The jclouds.compute category is nice because it logs things like what the
runscript output is, which saves SSHing to the instances.
* Added an appender to the test log4j.xml files for the whirr logging output.
* Also fixed the test log4j.xml files to have a root-level appender (log4j was
complaining about this before).
* Changed the poms so that log4j is used for tests and for the CLI, but
otherwise is not a dependency (slf4j is used as the logging facade). In
principle this means that clients using Whirr as a library could use any
logging supplier.
Patrick mentioned offline that it might be nice to have an interface between
Whirr and jclouds which does a lot of the service logging for you (i.e. the
writer of a Whirr service). I agree, but think this is bigger in scope and
probably belongs in another JIRA.
> improve logging in whirr cli
> ----------------------------
>
> Key: WHIRR-106
> URL: https://issues.apache.org/jira/browse/WHIRR-106
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.1.0
> Reporter: Patrick Hunt
> Fix For: 0.2.0
>
> Attachments: log4j.properties, WHIRR-106.patch
>
>
> I believe there are two issues here:
> 1) services are not logging anything
> 2) logging output does not seem to be setup correctly
> for 1) we should add info level (at least) messages to the service
> implementations to indicate progress
> for 2) we should include a default log4j.properties (or xml) in the shaded
> jar which has sane defaults (see attachment for an example I whipped up and
> am using myself)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
