pep8: enable H402 checks

Change-Id: If4a512ef31549f5611c9a462bef23ace12822757
pep8: enable H401

That was easy.

Change-Id: I1cc1450338b33e1164c6a2a7d83937019334210f
pep8: enable H304 checks

I hope this isn't too invasive.

Change-Id: I1ff846919bbff9d926bf3330c5247ceb353f9164
pep8: enable H302 checks

I'm on a streak.

Change-Id: Ie953e890dd36f3301076ed406782912fe3513e1a
pep8: enable F403 checks

Change-Id: I70da3f953b67022532eec55b228c6e476dcd4972
pep8: enable E125 checks

Change-Id: Ic9904c80320b3bf7335d4871d509120320caf64b
Signed-off-by: Julien Danjou <julien@danjou.info>
Imported Translations from Transifex

Change-Id: I65cc32c022659abe71c08e8815e22736a218daac
doc: be more explicit about network counters

Change-Id: Ia42cc840dd977aff51767ddc576cfd6c1ed545b2
Fixes: bug#1187943
Remove useless periodic_interval option

Change-Id: Iac2c72bf64be79d1227af5b98873b5b1511b548a
Fixes: bug#1181160
Merge "pep8: enable H402 checks"
Merge "pep8: enable H401"
Merge "pep8: enable H304 checks"
Merge "pep8: enable H302 checks"
Merge "pep8: enable F403 checks"
Merge "pep8: enable E125 checks"
Merge "Remove useless periodic_interval option"
Merge "Imported Translations from Transifex"
Check that the config file sample is always up to date

Change-Id: Ief192e8c88d052da68f13d3e9502c8799b8e1c17
Signed-off-by: Julien Danjou <julien@danjou.info>
mongodb: fix limit value not being an integer

PyMongo actually wants an integer and not None.
It seems that was hidden by MIM.

Change-Id: Ia3583018f841ca0387a467cd9f24c13124ab4141
Change period type in alarms API to int.

Previously this was float, which looks like an over-sight,
as we will not be supporting sub-second evaluation.

Also float is a mismatch with the v2 statistics API, which
requires that the given period be an int (the alarm period
is passed to the statistics API during threshold eval).

Finally, the sqlalchmey schema defines the period as Integer,
so it makes no sense for the types stored mongo & mysql to
differ.

Submitting this one-liner as a separate patch, as it may be
slightly controversial because it requires that all existing
alarms stored in mongo be deleted and re-created (as we don't
have a schema migration mechnanism for mongo).

Change-Id: Id999005e4de5d77309b0a32ad582804525ec1494