heat/heat/api
Ahmed Elkhouly f52d77f0d2 Resource mark unhealthy RPC and ReST API
There may exist resources that the user (or application) knows are
unhealthy where Heat has no way of determining that.

Add a PATCH handler to the Resource endpoint::

  /stacks/<stack_name>/<stack_id>/resources/<resource_id>

The PATCH method will accept a JSON body of the form::

  {
    'mark_unhealthy': <bool>,
    'resource_status_reason': <string>
  }

This patch Implements:
- RPC API to mark resources as CHECK_FAILED in both the legacy and
convergence architectures in heat-engine
- ReST front end to the RPC API call in heat-api

Change-Id: Ifa48b179723a2100fff548467db9e162bc669d13
Partially-implements: blueprint mark-unhealthy
2016-02-24 18:00:44 -05:00
..
aws Use EntityNotFound instead of PhysicalResourceNotFound 2015-11-19 22:58:01 +08:00
cfn Incorrect grammar with dot 2016-01-17 05:22:42 +00:00
cloudwatch Using LOG.warning replace LOG.warn 2015-12-29 09:32:42 +00:00
middleware Merge "Optimize the fault map for EntityNotFound" 2016-01-29 04:34:35 +00:00
openstack Resource mark unhealthy RPC and ReST API 2016-02-24 18:00:44 -05:00
__init__.py Empty files shouldn't contain copyright nor license 2013-12-24 20:29:31 +08:00
versions.py Remove identical modules versions.py 2015-06-16 17:00:39 +03:00