[AMBARI-2405] Make non-cloud response objects optional

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Component/s: documentation
• Assignee: Tom Beerbower
• Reporter: Brian Swan
• Created: 17/Jun/13 19:09
• Updated: 12/Jun/17 21:00
• Resolved: 10/Sep/13 23:34

Description

Several of the Ambari API response schemas (https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md) list several objects as required that don't make sense when Ambari is deployed in a cloud hosting environment. These objects should be made optional. Specifically, the following properties should be optional (listed by API call):

/clusters/:clusterName

• cluster_id
• requests
• configurations
  /clusters/:clusterName/hosts/:hostname
• public_host_name
• rack_info
• total_mem
  /clusters/:clusterName/hosts/:hostName/host_components/:componentName
• desired_stack_id
• stack_id
  /clusters/<name>/hosts/<node>/host_components/datanode (also tasktracker)
• disk
• cpu
• load
• memory
• network
  /clusters/:clusterName
• workflows
  /clusters/<clusterName>/hosts/<hostname>
• host_status
• host_state