Updated openstack/openstack
Project: openstack/python-keystoneclient  fe133ea52d9b14832a4aa168b35aae4261d207d4
null
document that --pass can be required

Closes-Bug: #1286202

Change-Id: I19861b9959723c19671954be5a751fcf06494e8d
Updated openstack/openstack
Project: openstack/python-keystoneclient  2ea52c1e3aed528ddf9dc7d254ba5e521c774f1a
null
Generate module docs

The module docs were not being generated.

Co-Authored-By: David Stanek <dstanek@dstanek.com>

Change-Id: I26e1d9a3d407474eb6b016f3ada4c495b5043460
Closes-Bug: #1278662
Updated openstack/openstack
Project: openstack/python-keystoneclient  76e1ec137e0e76efd5b3461b8eff77cb3ff5f4b1
null
Fix doc build errors

There were some parts that had invalid RST in their docstrings
which caused warnings and errors to be generated.

Related-Bug: #1278662
Change-Id: Ibb53e6f49b5fa100fa6ecfe47331f9a70729d03b
Updated openstack/openstack
Project: openstack/ceilometer  2e7da5cce33016ecd369a4012cab76ac0feda1ba
null
Rationalize get_resources for mongodb

Fixes bug 1288372

Previously the performance of the /v2/resources API without
constraints degraded sharply as the size of the meter collection
grows, regardless of the number of known resources.

We rationalize the underpinning storage driver method for mongo
so as to rebase the query on the much smaller resource collection.

This requires a subtle change in the semantic of the first and
last sample timestamps which decorate the resource representation.
These values are now defined respectively as being not later than
youngest sample, and not earlier than the oldest timestamp, known
for each resource.

In order to maintain support for "tight" timestamp constraints
on resource queries, we adopt a hybrid approach. For resource
queries without timestamp constraints, we optimize with a simple
query on the resource collection, but revert to a map-reduce on
the meter collection for timestamp-constrained queries.

The logic being that when one makes a resources query constrained
by timestamp, one is essentially asking a question about samples,
hence prepared to incur the cost of a query on the meter collection.
Whereas for other constraints (user_id, project_id, source etc.)
on the resources queries, one is more asking a question purely
related to the resources themselves.

Change-Id: Ifbf8932b4164f62bfda1cb3b8b9afe181051bc52