inconsistent use of getLogger in keystone

[Joseph Heck]

within the keystone codebase and middleware, we use "log = logging.getLogger..." a bit inconsistently. This bug is to run through the instances where we instantiate it, and set it to:

 LOG = logging.getLogger('keystone.module.name.here') and update it's usage.

Also - add that detail to HACKING.rst

[Dolph Mathews (dolph)]

We can (and do) also:

    from keystone import logging

    logging.debug('foobar')

... so I assume we should also update keystone.logging to prevent this from being possible?

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/5357
Committed: http://github.com/openstack/keystone/commit/678dcad410b2496eb1ed34bb91c0d0914a9c6b0d
Submitter: Jenkins
Branch: master

commit 678dcad410b2496eb1ed34bb91c0d0914a9c6b0d
Author: Dolph Mathews <email address hidden>
Date: Wed Mar 14 14:28:04 2012 -0500

    Refactor keystone.common.logging use (bug 948224)

    Change-Id: I01b2b5748a2524273bb8c2b734ab22415652f739