Need a better logging.conf.example

[Dmitri Zimine]

During demo setup, we found the current logging.conf.example a bit limiting. I propose to:

1) Configure it so that it writes well-formatted INFO level to the console, DEBUG to /tmp/mistral.log and a pretty workflow trace outputs to /tmp/mistral_wf_trace.log.

2) Do the formatters to match default output (same as we have today when the logging.conf not being used)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/142295

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/142295
Committed: https://git.openstack.org/cgit/stackforge/mistral/commit/?id=df5f04c58a28d213a127ea88b0c8237a412c03d5
Submitter: Jenkins
Branch: master

commit df5f04c58a28d213a127ea88b0c8237a412c03d5
Author: manasdk <email address hidden>
Date: Wed Dec 17 01:00:56 2014 +0000

    Updates logging configuration samples

    - Changed all formats to look more like the default formatters. This simplifies parsing
      in tools like logstash etc.
    - Changed location of all log files to end up in /var/log instead of /tmp. /var/log is
      a better default than /tmp for log files.
    - In wf_trace_conf_logging.conf.sample using separate formatters for different handlers.
      This accounts for the usecase of each handler having its own specific log format to
      reduce redundancy in log statements.

    Change-Id: I467f4d493cd379c11cf7e5e872e4baa4faeac674
    Closes-Bug: 1322740