alarm: rename counter_name to meter_name

This is a follow-up wrt the recent fix that handled in Ceilometer for
the alarming API.

Change-Id: Ide73a2e703bf31652b819c6d5170891c73b77ec9
Added support for running the tests under PyPy with tox

This is a precursor to having them run under check and gate.

Change-Id: I42ed34362bb840fe3a6d1d22e28beba8963fdb85
Fix a typo in "sample-create" help message

The word "alarm" is used twice instead of "sample".

Change-Id: I9a3ce514f3a3766add14ed1b352e31bf003f1cee
Merge "alarm: rename counter_name to meter_name"
Use global openstack requirements

Update global openstack requirements.

Change-Id: Idf561ce746c86c775855d00cb3436feaf9f65cba
Adding missing 'statistic' field to alarm-show

Closes-Bug: #1225049

Adding missing 'statistic field to printed table with alarm details

Change-Id: I69a743bfa340d4e1193f58c84195db398cbdf02b
Pass region_name argument to keystone client

Change-Id: If82bd7fe5680faef6e56abb6f76d203b7296beb5
Closes-Bug: #1228063
Replace OpenStack LLC with OpenStack Foundation

Change-Id: Ia007da282714d8ee7337fd3b51f6dcc3b64d7ec3
Fixes-Bug: #1214176
Use the new alarm format

The change sync the client API with the new alarm type and keep
compatibility with the previous format of the alarm.

It allows to create the new type of alarm: combination alarm.

Implements blueprint alarming-logical-combination

Change-Id: Ie62265023cadc20cf36a0d0b3775f4d984e324cf
Merge "Replace OpenStack LLC with OpenStack Foundation"
Merge "Pass region_name argument to keystone client"
Improve the CM shell client alarm visualisation

This change aim to get a better alarm representation in shell.

In alarm-list:
* it add a short sentence to describe the alarm rule
* it remove project_id/user_id because it always show the same id for
  all alarm for end-user

In alarm-show, it show alarm rule attributes as alarm properties instead
of a unparsable json in the rule property.

example of short sentence for column 'Alarm condition':
* combinated states (AND) of 8babd6a2-c457-42d0-9eb5-cdfb3cb50203,
  d0e11a94-8f59-48a9-8f6d-b0d68aaac8d0
* cpu_util >= 50.0 during 1 x 60s

Change-Id: If4df2dc08f9f4cb7796fd98308c7d62e311d1138
Help messages: specify which options are required

Closes-Bug: #1223283

Change-Id: I080fa73bd45a1f9f442dbcdfa65fdc24e30521da
Added support to --os-cacert

Closes-Bug: #1224343

Change-Id: Ib0549d4496c47900c81cc970b99bcff25cad0040
Allow to update an alarm partially

The patch allow to only modify a part of an alarm instead of force to
set the full alarm description.

This permit to an application that have been written code around alarm
with ceilometerclient 1.0.4 and ceilometer pre havana-3. To update alarm
without any change with this and ceilometer >= havana-3 (ie: heat).

Fixes bug #1231303

Change-Id: I20250131d05d20bfadbca450dfe6b8237f4b7183
Updated from global requirements

Change-Id: I71d6d8aad148b240f8ab1325d3c3ff2996ebf642
Fix shell.do_alarm_get_state to get as opposed to set

Otherwise the CLI fails when attempting to set a state arg that
doesn't exist.

(Simple copy'n'paste error in the original code).

Change-Id: Iab117177805449ddec9d03656a95a0cbbbbd58bb
Use standard CLI object-verb ordering for alarm-{g|s}set-state

The openstack CLIs all use an object-followed-by-verb ordering
convention when construct command names.

Follow a similar convention for commands to get and set alarm
state.

Change-Id: I34e0f450019556c80476df782d4c86dca08bdc9d
Merge "Fix shell.do_alarm_get_state to get as opposed to set"
Merge "Use standard CLI object-verb ordering for alarm-{g|s}set-state"