organise requirements files

alphabetise requirements so it's easier to see what packages we
depend on.

Change-Id: I27fc8d042c7d38267a4134215ccacc4a6b373e0b
Imported Translations from Transifex

Change-Id: I5813774fefd9863e8c26744ffc8aa280cc70dd03
Remove rpc service from agent manager

The agent doesn't need to act as a rpc server.
This patch migrate the agent manager from a rpc service to a normal service

Change-Id: I06f4546fa40f8702a75adc7f6f8e439d17af3de3
Merge "organise requirements files"
sql migration error in 020_add_metadata_tables

- add check to verify resource_metadata is not empty
- fix check to verify insert statement is set

Change-Id: I6b7c1d4a8ebf35af2547d97baa39831597012468
Closes-Bug: #1257779
Merge "Remove rpc service from agent manager"
Don't need session.flush in context managed by session

Within the scope of a single method, keeping all the reads and writes within
the context managed by a single session. In this way, the session's __exit__
handler will take care of calling flush() and commit() for you.
If using this approach, you should not explicitly call flush() or commit().
See http://stackoverflow.com/questions/4201455/sqlalchemy-whats-the-
difference-between-flush-and-commit

Closes-Bug: #1258044
Change-Id: I53f7a054ffd4a4d72ae20d5efc91bc24c1f7516e
Merge "sql migration error in 020_add_metadata_tables"
Properly reconnect subscribing clients when QPID broker restarts

Fixes bug 1251757

This is a cherrypick of oslo-incubator:
e227c0ed7e0ed1f9b8d029336f8aeb60e38c23df

From the oslo-incubator bug:
When the QPID broker is restarted (or fails over), subscribed clients
will attempt to re-establish their connections.  In the case of fanout
subscriptions, this reconnection functionality is broken. For version
1 topologies, the clients attempt to reconnect twice to the same
exclusive address - which is illegal.  In the case of version 2
topologies, the address parsing is broken and an illegal address is
created on reconnect.  This fix avoids the problem by removing the
special-case reconnect code that manages UUID addresses; it is
unnecessary as the QPID broker will generate unique queue names
automatically when the clients reconnect.

Change-Id: If966bb25e49b5837293a1bb181bbb02086599d81
Create a shared queue for QPID topic consumers

Fixes bug 1257293

This is a cherrypick of oslo-incubator:
ef406a21782134aeefb944f74b3f1a47d6169318

From the oslo-incubator commit:
When multiple RPC servers (consumers) are subscribed to the same RPC
topic, a single RPC request to that topic should be received by only
one of the consumers.  A bug in the QPID driver caused every consumer
to receive a copy of the RPC request.  This bug affects only Topology
version 2.  This patch will cause a single queue to be created for
each topic, and shared among all consumers of that topic.  This
results in each RPC request being received by only one consumer,
in turn across all the competing consumers.

Change-Id: I97c6eb5fe63322ab70716c63074818ff1b6ea82b
Merge "Properly reconnect subscribing clients when QPID broker restarts"
Merge "Create a shared queue for QPID topic consumers"
add more test cases to improve the test code coverage #5

In this patch, the following module test coverage improved to 100%

ceilometer/alarm/partition/coordination

Class PartitionIdentity was not tested for various method. This
patch set correct that problem. Also, class PartitionCoordinator
has 3 exception branches were not tested. This patch set added
more test cases to check these conditions.

Change-Id: Ia33a28e1650b6312843375af04973c9d5da2d89d
Add import for publisher_rpc option

If this option is not imported a NoSuchOptError is
raised starting the ceilometer-collector service

Closes-Bug: #1258650
Change-Id: I46f8a0510603d31ce8cc9a0b5b15880083138487
fix unit

The unit in document is different to source.
This patch fixes the unit to same as source.

Change-Id: I25df51f8e88976d81bae4f36116b5ea2588f8a23
add newly added constraints to expire clear_expired_metering_data

- cascade deletes to metadata tables on meter deletion
- delete associations on object deletion
- add check to not delete user/project entries associated with Alarm

Change-Id: I24cbaea9ede6d142dc22eaf070b3f7d1f14b484a
Closes-Bug: #1258071
Merge "fix unit"
Add configuration-driven conversion to Events

Add configuration to control what traits get added to Events
from notifications, how those traits are defined, and what
notifications get converted (and eventually stored).

Change-Id: I2befc97b3d3b33851a5bfe709bf086895fd72cce
Implements: blueprint configurable-event-definitions
Updated from global requirements

Change-Id: Id43d52959670ad2e10961f6957e131e60e33fc31
Merge "add more test cases to improve the test code coverage #5"