Fix BaseException.message DeprecationWarning

https://review.openstack.org/#/c/32154/ introduces a deprecated
TypeError.message reference, which won't work in python3 and
causes a DeprecationWarning to be output on >= python 2.6

Change-Id: Ibd11d4ad6b82e96ede8f38fe76112bd71e98c5c9
Add VerifyAll to test methods using mox.

Missed this comment in an earlier review.

Change-Id: If9737a03ba003331d0e20288e3bbc09002c6dbdb
Unrestricted username length causing error.

When we tried to create a username in keystone with
a length > 64 characters, an error was being raised.
Only use the first 64 characters of the dynamically
generated name in this case.

Change-Id: I5a5f863d721da8d187facb48230aeab251c7d240
Do not refresh timestamp from database on read.

Doing a database refresh on timestamp read is causing errors
such as:
heat.openstack.common.rpc.amqp InvalidRequestError:
  Could not refresh instance '<Stack at 0x2c95a90>'

This has only been seen using postgres, possibly because the problem is
being masked on mysql due to the driver's lack of concurrency.

The database refresh seems to be unnecessary, as there appears to be
no logic which depends on timestamps being accurate (nor is there
any timestamp comparison logic at all)

Fixes bug: #1193132
Change-Id: I22c3c4546a0f44b76a95e473b68b6fbb2e423b90
Give alarm a physical_resource_name which need no id.

This restores previous behaviour, including workarounds for
circular dependencies.

Fixes bug: #1192814

Change-Id: I33e8e4d7806fb397553944dbd6ebb85b575b9cb5
Merge "Fix BaseException.message DeprecationWarning"
Merge "Give alarm a physical_resource_name which need no id."
make stack creation return json response

added a serializer to handle create response serialization

fixes bug #1187883

Change-Id: Ibdeb8b810d759901979becb8b29bdc337f2f5bec
Merge "Add VerifyAll to test methods using mox."
Merge "Unrestricted username length causing error."
Adding common base class for Rackspace Resource providers

Change-Id: If7d15e01c53fb6db4bdee5759b0ef4f087640c58
Fixup some trivial license header mismatches

Newer Hacking releases are pedantic about the
license header. Fix up the trivial mismatch.

Change-Id: I418222734303b8578ab0b34b8eb044d9543fc888
Emit alarm actions if a rule remains in ALARM state.

It looks like the original intent of this edge-triggering was to
prevent actions being emitted too frequently, causing overshoot of
scaling resources.

However this causes an issue when one scaling resource change is not
enough to bring the alarm state under the threshold.

Proper use of Period, EvaluationPeriods and Threshold should be sufficient
to prevent scaling resource overshoot.

Fixes bug: #1193970

Change-Id: I5b38eb82cd1ad568fe4af77999e9d52f9eb99328
Merge "make stack creation return json response"
Merge "Emit alarm actions if a rule remains in ALARM state."
Merge "Fixup some trivial license header mismatches"
Merge branch 'master' into bp-dev/cloudlb-resource
removing coppied resource

Change-Id: I5ca3d95bcf67f6c0bb85a0a397cd077b1b68a50d
Merge branch 'bp/rackspace-cloud-database-provider' into bp-dev/cloudlb-resource
Make handle_update work

Change-Id: I23c742694e13c04dee307c4ee69739fb4509aecf