anchor.diff:               "id": 51
               }
            ]
  -      }
  -
  +        }
   
   ##Alarm [/clusters/{clusterId}/alarms]
   ###Retrieve configured alarms [GET]
  
positive.code:             "id": "multi-node"
          }
  
  ##  Clusters [/clusters/{id}]
  ###Remove a cluster [DELETE]
  
  + Parameters
  
negative.code:             "id": "multi-node"
            }
          ]
          
  
  ## Clusters [/clusters/{clusterId}/state]
  ###Set state [POST]
  
  + Parameters
      + clusterId (required String `clusterID`) ... The id of the cluster.
  
  + Request (application/json)
  
          {
            "state": "SUSPENDED"
          }
  
  +  Response 200 (application/json)
  
          {
              "appMovement": "prohibited",
              "state": "SUSPENDED",
              "port": "8080",
              "host": "172.24.0.2",
              "id": "multi-node"
          }
  
  ## Clusters [/clusters/{clusterId}/movement]
  ###Configure application movements [POST]
  Configure whether moveing the submitted applications between different queues to set a priority among them is allowed or not. 
  Based on our contribution to the CapacityScheduler [YARN-2248](https://issues.apache.org/jira/browse/YARN-2248) we made available to move running applications between queues.
  
  + Parameters
      + clusterId (required String `clusterID`) ... The id of the cluster.
  
  + Request (application/json)
  
          {
            "allowed": "false"
          }
  
  +  Response 200 (application/json)
  
          {
              "appMovement": "prohibited",
              "state": "SUSPENDED",
              "port": "8080",
              "host": "172.24.0.2",
              "id": "multi-node"
          }
  
  #Group Alarms
  An alarm watches a metric over a specified time period, and used by one or more action or scaling policy based on the value of the metric relative to a given threshold over a number of time periods.
  