Fix some spelling mistakes and a incorrect url

Change-Id: Id122cd98d133496e423847274d7abdbfd54262af
Fixes Hyper-V Inspector network metrics values

The Hyper-V inspector is currently returning the wrong metric values. The
current values are the aggregated ones, which is not correct in scenarios
in which instances have more than one nic.
Furthermore, values were taken from the
Msvm_EthernetPortAllocationSettingData, instead of
Msvm_EthernetSwitchPortAclSettingData.

Change-Id: I669ff52a1be2ee56bf69aa3b680ab42fdcaf1cb7
Closes-bug: #1289014
Updated doc with debug instructions

This commits adds some info about how you can use debugger in
ceilometer.
Currently testr cannot break into debugger, you have to use
alternative test runner to use it.

Change-Id: Ica68da3da5d8162765a79686d29ffd8d8d9cc85f
Extend test case to cover old alarm style conversion

There is a related change https://review.openstack.org/#/c/74462/
that fixs bug #1281181. This change extends an existing test case to run
on db2 enigne to cover that bug

Change-Id: Ib6894c774ec3fe322a2b8a75cc036cedcee5ce43
add host meters to doc

we added meters to capture host stats. this patch adds these
meters to the documentation

Change-Id: I023c130c721ee74e53aa7a21489fe02d4b68a402
Ensure insecure config option propagated by alarm service

Fixes bug 1292130

Ensure insecure (i.e. non-cert-verifying) access over SSL to
keystone works from the alarm evaluator

Change-Id: Ice009ad97ea540afede697e9d812f1bde877dd84
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
Merge "Ensure insecure config option propagated by alarm service"
Merge "Extend test case to cover old alarm style conversion"
VMware vSphere: Bug fixes

- Fixed bugs in meter conversions i.e. converting the stat value queried
from vSphere to the one used for creating ceilometer samples.

- Switched the vSphere networking counters 'bytesTx/bytesRx' to
'transmitted/received'. The counters are synonymous, but the latter ones
are available since ESX 3.5 and former are available only in ESX 5.0
onwards.

- Added a null check in VsphereOperations._init_vm_moid_lookup_map()

Change-Id: I8691ce4ded7bdc824bd56427642f9dd87081727a
Implements: blueprint vmware-vcenter-server
Merge "Updated doc with debug instructions"
Make sure use IPv6 sockets for ceilometer in IPv6 environment

In IPv6 management network environment, ceilometer command will
throw 'Address family for hostname not support' when use WSGI
simple server. The root cause is python TCPServer implementation
is hard-coded to use IPv4, even in IPv6 environments. Python
community want to fix it in Python3.5, so we need to make a
workaround for it.

Change-Id: I3260a346a095b0f3e57093c18b1920dffe5ac55d
Closes-Bug: #1269243
Added documentation for selectable aggregates

Documented available aggregate functions
and added example syntax showing how to use
improved Statistics API, which allows the user to
selectively access aggregate functions. Also
documented the Capabilities API, which allows
the user to find out what functionality is supported
by their storage driver.

Closes-Bug: #1290924
Change-Id: I9739d2102baf6040de017843ae20391c4c9b6fff
Fix bug in get_capabilities behavior in DB drivers

Capabilities API returns NotImplementedError in case of SQLAlchemy
driver. This issue is fixed in this patch by moving the function into
the proper class.

Another issue is, that get_capabilities function overwrites the
DEFAULT_CAPABILITIES dict in base.py every time, when the function is
invoked.

This behavior was changed to create a CAPABILITIES dict in each DB driver's
__init__ function by making a deep copy from DEFAULT_CAPABILITIES and
updating the new dict with the AVAILABLE_CAPABILITIES. get_capabilities now
returns the newly created CAPABILITIES dict without modifying it.

Tests were also added to check that get_capabilities returns the expected
values for each DB driver.

Fixes-bug: #1292611

Change-Id: I725751b600bf462c19278e5785eb2d8530023083
Merge "Rationalize get_resources for mongodb"
Merge "Added documentation for selectable aggregates"
028 migration script incorrectly skips over section

028 migration patch for alembic scripts incorrectly skips over
applying former alembic script '17738166b91' when it is needed.

Change-Id: I86a49f1979d8c5a8d5e5f15da8c007216b626928
Closes-Bug: #1292312
Merge "Make sure use IPv6 sockets for ceilometer in IPv6 environment"
Merge "Fix bug in get_capabilities behavior in DB drivers"
Merge "028 migration script incorrectly skips over section"