Implements in operator for complex query functionality

Implements: blueprint complex-filter-expressions-in-api-queries
Change-Id: I6ee7249f605f2afdeae59adf97f588cf1075a453
Implements monitoring-network

This feature collects the network information(devices, connect statuses
and statistices) via North Bound API from the SDN controller.

Implements: blueprint monitoring-network

Change-Id: Ifaa88fd3135dafe8ae3e83e03b76fb9b7e1b0904
Add comments for _build_paginate_query

Add comments for _build_paginate_query which will called
_recurse_sort_keys. It will generate the query criteria
recursively if multiple sort keys passed in.

Change-Id: I102308fc1a57f1ba8bd96e64badedbcf60840c28
Adds doc string to query validate functions in V2 API

Rename is_timestamp_valid parameter to allow_timestamps and add
doc string to _validate_query and _validate_timestamp_fields
functions, related to the bugfix of bug 1280975.

Change-Id: I7c8564ce88d048e5b7d6d1e3c7109c5cb08e48f3
rename meter table to sample

as we branch common meter definition data to it's own table,
we rename table containing raw data to more appropriate name:
sample

blueprint: meter-table-sql
Change-Id: I55c86540098225a3d52116df8b27854483921ee9
sample table contains redundant/duplicate data

create a meter table to store meter definition attributes:
- name
- type
- unit

blueprint: meter-table-sql
Closes-Bug: #1211985
Change-Id: I4dd510e66d64226b03cfce8d7dd5e77937793ba3
Remove code duplication

Remove code duplication from impl_mongodb and impl_db2 as both of
these drivers use pymongo. This is a multiple step process as there
are several differences between the implementation of these drivers.

The first step is about to move the identical functions to a common
base file, called pymongo_base with a Connection class, from which
the Connection class of both drivers will be inherited.

Change-Id: Ib3c250213cda5450c96c6e495f56623ed7ac0490
Fix typo on testing doc page

Fix typo.

Change-Id: I50e4f3ac87ad52df931b45c6138038e28cefb95e
Sync latest config file generator from oslo-incubator

The fix to the config file generator to support lazy messages
is the main addition of interest because it is needed after
lazy messages were enabled.

Commits included:
  1a6dfb956 Sanitize FQDN in config generator
  e839886cc Config generator fails with lazy messages
  763eedff6 Fix DictOpt support in config sample generator

Partially implements blueprint i18n-messages
Closes-Bug: #1280826

Change-Id: I2174139ba3767d05924747cbefa377ba8780103d
Set default log level of iso8601 to WARN

In openstack.common.log, the iso8601's default log level is WARN.
But ceilometer doesn't set WARN as default log level of iso8601.
This may cause a lot of DEBUG level message recorded in log files if we
haven't configured the default log level in ceilometer.conf.

Change-Id: I8edbcd5f0885b424c70483180b479588bca254a2
Closes-Bug: #1284412
Fix the way how metadata is stored in HBase

The goal of this patch is to fix filtering on metadata.
In HBase we should use the same approach as in SQL now:
store raw metadata as well as flattened one.
When user sends get request on meters, samples or resources
it is possible not to fetch all the data but construct corresponding
filter based on flattened metadata values.
Unfortunatelly, it is not possible not to store raw metadata because
flattening on API level is done in a different way. This
improvement is postponed till API v3.

Change-Id: I1206535ab12037817175d5e79716b223594f246a
Merge "Implements monitoring-network"
Merge "rename meter table to sample"
Merge "sample table contains redundant/duplicate data"
api: export recorded_at in returned samples

Change-Id: I970bc82d70fd75cbb25ea6c7e0778521aaa9b255
Blueprint: storage-sample-timestamp
Merge "Fix the way how metadata is stored in HBase"
Tolerate absent recorded_at on older mongo/db2 samples

Fixes bug 1284608

Prevents failure of a samples query against a mongo-like instance
(i.e. either mongodb or db2) selecting metering data that predates
the advent of the recorded_at attribute for samples:

  Ia0ff8bd07fd811fe8d3050d30971a05a277798d0

Change-Id: If480321923e9166583bbea91c3878950bafbedf1
remove audit logging on flush

in something as simple as the tempest gate, this creates 2.5 MB
of compressed logs. I do not believe there is any actual value
in logging the flush, especially as the failure to flush is
correctly logged.

Change-Id: I176bc13e5cacf892b07c4fed3871924500622d01
Merge "Tolerate absent recorded_at on older mongo/db2 samples"
Merge "Implements in operator for complex query functionality"