timestamp columns in sqlalchemy not timezone aware

Fixes bug # 1066148.  Sqlalchemy schema timezone
fields are not timezone aware therefore the
timestamps need to be adjusted as such

Change-Id: I0979fe3b9487257f988790ddb23a317a3df7a19d
Fix sqlalchemy performance problem

Fixes bug #1070074 too much lazy loading on the
default model.  Removed those and only added lazy
loading to queries that specifically need eager
loading

Change-Id: Ifa7446bddef855ae8e8b76040ba3336a53606215
implement get_volume_max for sqlalchemy

Fixes bug #1057679

Change-Id: I0034bec7b5da23496ac04224013e571f7ea82abc
api: add timestamp interval support in _list_events()

We also remove test_all() because it's already tested in
test_list_resources, where it belongs.

This fixes bug #1079235

Change-Id: Ib57fad688c09b38944c0129ede68b9620f074a1d
Signed-off-by: Julien Danjou <julien@danjou.info>

Conflicts:

	tests/api/v1/test_list_events.py
Fix sqlalchemy for show_data and v1 web api

When sqlalchemy (e.g. mysql) is used for ceilometer, show_data.py and web api do
not work because some attributes and keys are different, such as meter/meters,
the patch is fix them and make both can work.

Change-Id: I4b827c3e6664213f1401b183ccbc3a1aaae872aa
Signed-off-by: Shane Wang <shane.wang@intel.com>
api: add support for timestamp in _list_resources()

Change-Id: I683bcbc2072b782eb94739aaa99e151ee9d0df3e
Signed-off-by: Julien Danjou <julien@danjou.info>

Conflicts:

	tests/api/v1/test_list_resources.py
Merge branch 'deploy' into stable/folsom-att-working-timestamp-filter
Make Impl of mongodb and sqlalchemy consistent

SqlAlchemy connection inherits from base.Connection, which doesn't have session
parameter in its function get_resources(). And session of get_resources() in
SqlAlchemy is not used and it can be got from self.session. So remove it to make
them consistent.

Change-Id: I85d5094d53af3de40645fa828d73d1dbc2677f0b
Signed-off-by: Shane Wang <shane.wang@intel.com>
sqlalchemy GET /v1/resources returns too much data

Meters data needs to match mongodb implementation.
The resources returned has meter attribute nested and
those results are each and every row of the meters for
that resource as well as all fields of each row. If a
resource has tens of thousands of meters associated to
it, the eager loading will load all of those rows and
return all that data in the json result. Instead, it
should match the mongodb implementation which simply
returns a distinct list of unique {'counter_name':
value, 'counter_type': value, 'counter_unit': value}.
force pip requirement for anyjson compatible with nova-compute
fix json requirement
making dbsync pkg binary
Merge branch 'stable/folsom-att-working-timestamp-filter' into stable/folsom-att

Conflicts:
	ceilometer/storage/impl_sqlalchemy.py
missed change from merge