Tech-debt: use image specific loggers

[Joshua Harlow]

Instead of using a single logger (and doing the weird prefix the message with the image name all over the place) it would be much nicer to just have a single logger for the main 'control program' (the one what runs actions to build images); and then for each image and its associated activity put all the logs for each into a different location (a configurable option that say defaults to $CWD/logs); then the output of kolla build is much easier to understand and reason about (vs the garbled mess that it is currently).

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/321884
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=929d84b143e723735817c88efc5df8d6239c6991
Submitter: Jenkins
Branch: master

commit 929d84b143e723735817c88efc5df8d6239c6991
Author: Joshua Harlow <email address hidden>
Date: Wed Jun 8 17:46:16 2016 -0700

    Stop using a global logger for all the things

    Instead of using the same logger for all the things
    which makes it incredibly hard to figure out what the images
    and there builds are doing; instead have it so that each
    image gets its own logger which is then used by tasks that
    process that image.

    Each images logs now will (optionally) go to a logs directory
    that can be more easily read and looked over and leaves
    the main logger for informational/task kind of
    output only.

    Closes-Bug: #1586478

    Change-Id: I939e073a2bc5ed8b5a1e969888fc743d80f468c9

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/kolla 3.0.0.0b2 development milestone.