Prevent alarm_id in query field of getting history

The ceilometer CLI support alarm_id in query field of getting alarm
history.
But it will raise error when invoking the db function get_alarm_changes.
Getting history of an alarm, the alarm id is required, so we needn't allow
the alarm_id in query field of getting alarm history.

Change-Id: I968b5bbcbc5af18a737b63598b63c1caa78d187e
Closes-bug: #1290809
Refactored the way how testscenarios tests are run

Instead of using custom loader we now use a base class from
testscenarios. This allows us to retain compatibility with
unittest test runner and run a single test if needed.

Change-Id: Id5ae4fd0edfa868aaf6a57bd2e5f212b51b722e1
Use the list when get information from libvirt

If the libvirt adds new elements to the domain info struct or others,
when use the new libvirt, there will be a valueError (too many values
to unpack). When we get information from libvirt, we should use the
original variable format. This change is for compatibility with upcoming
versions of libvirt which change this signature.

Change-Id: I885a48b730acd618e7cefc93cee3d69226575b7c
Closes-Bug: #1291805
Disable oslo.messaging debug logs

ioslo.messaging debug logs are too verbose, turn them off. A similar
patch dropped nova-conductor logs in the gate down from 7MB to under 300K.

Cherry-Pick from oslo-incubator since we are in feature freeze:
Ia12c003dae196e2220a5f6ea768758a75f2ede23 and
Icc61964c6a2b002ac1c8566f174e6a5230674c75

Change-Id: I48733823e178afd2f22d81d584bb73f95ec9a7cd
Use swob instead of webob in swift unit tests

While we are at it, don't bother importing webob and not using it if
we are going to end up using swob.

Change-Id: Ibb8cd23a6e8eb7bed11704b2dcee5bcdb9c3278a
Metadata in compute.instance.exists fix

Fixing problem with inconsistent metadata structure in messages from nova.
When message['payload']['metadata'] was not dict ceilometer raised AttributeError.

Related to: bug #1297686

Change-Id: Iaf9620202eda293acf6b4776d35600670f2e2a6b
ensure dispatcher service is configured before rpc

there is a rare race condition where when the mq contains
notifications, the rpc service is configured before dispatcher so
it may attempt to start sending messages to dispatcher before it
has been configured. this patch ensures the dispatcher
configuration is done before starting rpc service.

Change-Id: If4c3a225e0bd5ae6eefad072b844af1ef5786f3f
Add note on aggregate duplication to API docco

Provide some additional clarity on allowable duplication
in the selectable aggregates passed to a statistics query.

Change-Id: If534e0667aa08fd531bbf31032e7648f7b80890c
Open Juno development

Bump preversion to 2014.2 to formally open Juno development.
The Icehouse release branch (milestone-proposed) will be cut
from the last commit before this one.

Change-Id: I0e42b2373eca35cd4f955a4a387ef87e22904ebf
User a more accurate max_delay for reconnects

In an HA deployment, a 60 seconds delay between reconnects can be quite
problematic. This patch changes the delay calculation by setting the max
delay to 5s and by changing the way it is increased.

Unfortunately, this is one of the places where both our main drivers are
not consistent. Rabbit's driver uses configuration parameters for this
whereas qpid's driver has never had one. However, I would prefer not
adding configuration paremeters to qpid's driver for the following
reasons:

    1. Most of OpenStack services depend on the messaging layer, hence
    they need it to be available. A 5s delay seems to be reasonable and
    I could argue the need of tune it further. Although so frequent
    reconnects can add load to the network, that wouldn't be the main
    issue if one of the brokers go down.
    2. We're trying to move away from configuration options towards using
    transport URL. This path is still not clear and I would
    prefer avoiding adding new options until we clear it out.

Closes-bug: #1281148

Change-Id: I537015f452eb770acba41fdedfe221628f52a920
(cherry picked from commit 8b628d1e024f787dbb93d508117d9148388c0590)
Merge "Open Juno development"
Align to openstack python package index mirror

Some modules we developed will not be updated to pypi in time, meanwhile,
jenkins will poll packages from openstack mirror, so it is worth to be
set as default index in tox.

User can use -i option in tox cli to change default index server to any
popular or his favorite.

Change-Id: I4449f9b6861a327cf2fd888205843b51a57dcd2f
Closes-Bug: #1289121
Merge "User a more accurate max_delay for reconnects"
Merge "Metadata in compute.instance.exists fix"
Merge "Disable oslo.messaging debug logs"
Merge "ensure dispatcher service is configured before rpc"
Fix Jenkins translation jobs

The jobs ceilometer-propose-translation-update and
ceilometer-upstream-translation-update do not update from
transifex since our po files contain duplicate entries where
obsolete entries duplicate normal entries.

Remove all obsolete entries to fix the jobs.

Add test to pep8 that checks that no new breakages get
introduced.

Change-Id: I3d7d04a7d5d073d5123f1f7b1e16fd3ef167acfb
Closes-Bug: #1299349
Merge "Refactored the way how testscenarios tests are run"
Merge "Use swob instead of webob in swift unit tests"
Merge "Fix Jenkins translation jobs"