Fix H307 violations and re-enable gating

H307 is a new rule in hacking 0.9, so fix new violations and
re-enable gating.

Change-Id: I805d10427ebeaee36589936f77a2cf0932c1378e
Fix H904 violations and re-enable gating

H904 got stricter in hacking 0.9, so fix new violations and
re-enable gating.

Change-Id: I7a3e9006cfb756da4893b9c0a6139a2e70c9aaf4
Fix H405 violations and re-enable gating

H405 is a new rule in hacking 0.9, so fix new violations and
re-enable gating.

Change-Id: I61541fa0a9dc18ad938df54d56c65c972b151622
Remove useless sources.json

Change-Id: If0595a079e5cb153c18e05cbd3ddaa64760638f1
update default_log_levels set by ceilometer

the current log levels are pretty old. update the current list to
extend current default default_log_level defined in oslo-incubator
and adding in stevedore and keystoneclient levels

Change-Id: I239645ef641613a994a48f20c0238e76dc9660f2
Partial-Bug: #1294789
Merge "Fix H307 violations and re-enable gating"
Merge "update default_log_levels set by ceilometer"
Merge "Remove useless sources.json"
Merge "Fix H904 violations and re-enable gating"
Merge "Fix H405 violations and re-enable gating"
Gathering together pieces for ironic notifications

Experimenting with a public fork on which I can keep a verbose
history which will be later squashed for review.

Change-Id: Id63da0380e2b10f511303405920ed69f2e226e64
First mighty spike at a notification plugin

This is very much a work in progress, so much so that there's not
much point even committing it for review yet, using github as my
location indepdendent storage.

This borrows heavily from the compute notifications code. The basic
idea is that there are a few classes of samples that can be had
(Fan, Temperature, Voltage, Current). Within these are potentially
multiple individual sensors and values. In all cases the volume of
a sample is always in 'Sensor Reading'.

Each class has a _transform_id and _transform_reading method which
can be used to bring the data in line with expected forms.

Questions:

* How much of the rest of the payload do we want to save, and thus
  give to the sample constructor?
* What is an event_type and how do we figure it out?
* Do we need to insure that numeric values are saved as numbers, not
  string representations thereof?
* Are the sample.nameS that are being created the correct way to
  deal with samples coming from specific devices? Or does that info
  go somewhere else? If a single instance of hardware has ten temp
  readings, how do we distinguish which reading?
flake8 and hacking fixes
Merge branch 'bp/ironic-notifications' of github.com:cdent/ceilometer into bp/ironic-notifications

Conflicts:
	ceilometer/hardware/notifications/ipmi.py
	ceilometer/tests/hardware/notifications/test_ipmi.py