ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AMBARI-2405) Make non-cloud response objects optional
Date Mon, 12 Jun 2017 21:01:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yusaku Sako reassigned AMBARI-2405:
-----------------------------------

    Assignee: Tom Beerbower

> Make non-cloud response objects optional
> ----------------------------------------
>
>                 Key: AMBARI-2405
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2405
>             Project: Ambari
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Brian Swan
>            Assignee: Tom Beerbower
>            Priority: Minor
>         Attachments: AMBARI-2405.patch
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message