Insufficient INFO logging

[aeva black]

Ironic is not logging very much at the INFO level today, and it should be. This is primarily what operators will use to look for activity, before turning on debugging.

Some guidelines have been proposed across projects, and we should aim to follow them:
  https://wiki.openstack.org/wiki/LoggingStandards

[aeva black (tenbrae)]

There has been some confusion / discussion on IRC as to when to log at what level. I believe the following summary by Lucas is worth referencing:

14:01:57 < lucasagomes> INFO for success, ERROR for failures, WARNING for failures that will be automatic retried or fallback
                        somehow, CRITICAL for errors that compromise the whole service and not an operation
14:02:01 < lucasagomes> and DEBUG for the rest

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Ellen Hui (<email address hidden>) on branch: master
Review: https://review.openstack.org/100360
Reason: Doesn't seem that useful to log here.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Ellen Hui (<email address hidden>) on branch: master
Review: https://review.openstack.org/99431
Reason: Abandoned in favor of https://review.openstack.org/#/c/99744/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/99744
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=5a727ae886254014f8055d85dd0e3eaf37b816c2
Submitter: Jenkins
Branch: master

commit 5a727ae886254014f8055d85dd0e3eaf37b816c2
Author: Ellen Hui <email address hidden>
Date: Wed Jun 11 22:39:51 2014 +0000

    Add more INFO logging to ironic/conductor

    Change-Id: I9506852ed76cbb57f21403233809ca5f04b8046f
    Partial-Bug: #1273856

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/99495
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=3ffa8b1c961e8392f0efed45d1d63e88f0549464
Submitter: Jenkins
Branch: master

commit 3ffa8b1c961e8392f0efed45d1d63e88f0549464
Author: Ellen Hui <email address hidden>
Date: Wed Jun 11 22:13:19 2014 +0000

    Add more INFO logging to ironic/common/service.py

    Change-Id: I60b0a33ce98f8b614a00af0c8cc5f27043bf022a
    Partial-Bug: #1273856

[Dmitry Tantsur (divius)]

Ellen Hui, hi! You've been assigned to this bug for a while already. Are you intending to do anything else about this bug? Could you give a status update or unassign yourself?

[aeva black (tenbrae)]

Cross-project guidelines for LOG standardization have been agreed upon:
  http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html

We should track this work against a blueprint instead of a bug. Bugs can have only one assignee, which is updated any time code is proposed, whereas a blueprint lets us track contributions from anyone that is working to improve the logging within Ironic.

[aeva black (tenbrae)]

Cross-project guidelines for LOG standardization have been agreed upon:
  http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html

We should track this work against a blueprint instead of a bug. Bugs can have only one assignee, which is updated any time code is proposed, whereas a blueprint lets us track contributions from anyone that is working to improve the logging within Ironic.

I've filed the BP here: https://blueprints.launchpad.net/ironic/+spec/follow-logging-standard