Propogate cacert and insecure flags to glanceclient

Fixes bug 1278973

Previously, the insecure flag was only propagated to the keystoneclient
while the cacert flag was only propagated to the keystoneclient and
the ceilometerclient used by alarming.

Since the glanceclient also supports these options, these flags should
be propogated to it also to avoid SSL cert verification failures when the
central agent calls out to glance over https.

Change-Id: I967ba080a4011a54b5789ca0fc20cb9a37dafb15
(cherry picked from commit b000317f670f635b00ca52a4539a0b83b14c8ff4)
Bump stable/havana next version to 2013.2.3

Change-Id: Ia5b940faf01df6cae58df1f4b4f5e8fa2f3f078a
Add an insecure option for Keystone client

Change-Id: I05cea4c79ad89d2c55008ea0d7ba9eefa5908fa2
Closes-Bug: #1232437
(cherry picked from commit d48b4a3a4e5d0b80c3644844e0f1c8e3806c78d6)
cacert is not picked up correctly by alarm services

related to bug 1266472 which changes client to look only at os_cacert arg.
update alarm services to use just os_cacert as well.

Change-Id: Id28a0838330296fe030fa7c4a35a216dd3e64bad
Closes-Bug: #1266477
(cherry picked from commit 89f9b3049ac7a395c470f8d323b44e8128e5b1b2)
Refactor timestamp existence validation in V2 API

There was a bug in AlarmThresholdRule in v2.py, the timestamp_keys
were defined with a missing comma:
['timestamp', 'start', 'start_timestamp' 'end', 'end_timestamp'].

The validation, if the timestamp field is used or not, was unclear
in the current implementation. A new parameter, 'timestamp_is_valid',
was added to the validation functions to show, if the timestamp is
allowed to use or not in the validated query.

Fixes bug 1280975

(cherry picked from commit b1834e55fce08f1536c7d9392ae035b9583be8ed)

Change-Id: I2aaef54354926f9afe3bb1d4fae8f8aa0ae600ab
Merge "Add an insecure option for Keystone client" into stable/havana
Merge "cacert is not picked up correctly by alarm services" into stable/havana
Merge "Refactor timestamp existence validation in V2 API" into stable/havana
Merge "Propogate cacert and insecure flags to glanceclient" into stable/havana
Ensure the correct error message is displayed

When a untranslated error message pass through the translation pecan
hook, the previous translated error is send to the client.

This patch fix that by reseting the "translatable_error" of the
translation pecan hook before each request.

Conflicts:

    tests/api/v2/test_app.py

Change-Id: Icee79cf09fd696655048c7c0cf8a3d6706e31701
Fixes: bug #1260398
(cherry picked from commit 02d017022bab577b581b58f42b468bf0b2c644a9)
Fix the default rpc policy value

Before, each time a service that use ceilometer.publisher.rpc start this
annoying message appear because the default value is not the correct.

WARNING ceilometer.publisher.rpc [-] Publishing policy is unknown (wait) force to default
WARNING ceilometer.publisher.rpc [-] Publishing policy is unknown (wait) force to default

This patch set the correct default (to default inteads of wait), and check in tests
that the expected logger method is called.

Fixes bug #1245965

Change-Id: I41b9461359c7b0b17eb8e9dad1772bafdc3554fc
(cherry picked from commit 30ecd2f76633b8854401c6254210aaa5a7920be0)
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

(cherry picked from commit eb14d7e80502f8b57f7c79f9120cf3f30f7e872b)
Change-Id: Ice009ad97ea540afede697e9d812f1bde877dd84
Merge "Fix the default rpc policy value" into stable/havana
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
(cherry picked from commit bd3997c088710c741d3438a2cd98658f18e69e68)
Fix validation error for invalid field name in simple query

The field name validation code runs only in case of the operator that is
specified for the invalid field name, is 'eq'. Otherwise the validation
ends with an invalid operator error. The field name validation code was
modified to check the field name first and only checks the operators for
valid field names.

Closes-bug: #1294628

Change-Id: Id34ae882940b36dec3ea81043b0d29b996a38426
(cherry picked from commit 50cffbc08f24ff8e3935aabecdf4be0fb366116d)
Fixes Hyper-V Inspector disk metrics bug

Changed disk metric names used by Hyper-V utils.

Was using wrong metric names before. 'Aggregated Disk Data Read/Written'
metrics refers to all disks (sum), while the metrics needs to be per disk.

(cherry picked from commit 39c0ca654743513ab158fac399813a1a557ab61e)

Change-Id: I4ec36152a8b8147069151dd6eb98f36f7aab9229
Closes-Bug: 1250336
Fix ceilometer.conf.sample mismatch

ceilometer.conf.sample mismatch issue makes the tests failing. This patch
removes the checkupdate.sh test from tox.ini, like it was removed from nova
too, until having a proper solution for handling the changes in
ceilometer.conf.sample, to fix the gate quickly.

Closes-Bug: #1297999

(cherry picked from commit 63ff15ed95f71f5272c64b82ff148d35f75782d4)

Conflicts:

	tox.ini
Change-Id: Ia638fb19ce25788a418b59509ec3527e643aac4e
Checks for presence of Hyper-V cpu metrics before accessing

Adds a default value if there are no cpu metrics to be retrieved.

Closes-Bug: 1249959
(cherry picked from commit f15e2cc9248c99e9b5c6b371ecce4f0ed49450cc)

Change-Id: I39513648ab25d46b2639b24a94e7344954ce3aeb
Merge "Fixes Hyper-V Inspector disk metrics bug" into stable/havana
Merge "Checks for presence of Hyper-V cpu metrics before accessing" into stable/havana