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)
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
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
removing dependency to clients
Merge branch 's-havana' into devel