Trove wsgi.py multi-interface binding to 0.0.0.0 should be logged

[N Dillon]

In trove/trove/common/wsgi.py (line 64) the launch() function binds to 0.0.0.0 which can cause issues; this should be logged

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/202802
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=cc25e2cdd8de5b37098147910c1c9db301cd5ca8
Submitter: Jenkins
Branch: master

commit cc25e2cdd8de5b37098147910c1c9db301cd5ca8
Author: jcannava <email address hidden>
Date: Thu Jul 16 16:18:59 2015 -0500

    Which interfaces trove starts up on should be logged.

    The bug specifically states that when trove starts up on 0.0.0.0 it
    should be logged, but there is no specific reason that there shouldn't
    be a log for admins to quickly reference what interface has the trove
    port.

    Change-Id: I1f6ba92d58096cff07f6e42391c59ed9fb07e0ac
    Closes-Bug: 1350060