heat/etc/heat
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
..
environment.d Add an option to disable cloud watch lite 2014-09-25 19:42:28 +10:00
templates Add Dimensions Default in AWS_CloudWatch_Alarm.yaml 2014-11-20 17:05:17 +03:00
README-heat.conf.txt Remove heat.config.sample file 2014-12-03 20:35:36 +00:00
api-paste.ini Merge "Added Keystone and RequestID headers to CORS middleware" 2016-02-17 18:59:33 +00:00
policy.json Resource mark unhealthy RPC and ReST API 2016-02-24 18:00:44 -05:00