incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Speidel (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-1029) Add api support for updating multiple host_component resources for multiple hosts in a single request
Date Wed, 21 Nov 2012 21:48:58 GMT

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

John Speidel updated AMBARI-1029:
---------------------------------

    Description: 
Ambari UI needs ability to update multiple host_component resources for a set of hosts.  Currently
this is not possible because it is necessary to include the host resource as part of the host_component
URI.

New functionality allows a host_component URI without providing a host resource.
Example: update foo property for the DATANODE and TASKTRACKER host components for hosts "h1"
and "h2".

URI syntax:
PUT http://localhost:8080/api/v1/clusters/c1/host_components?HostRoles/host_name=h1|HostRoles/host_name=h2&HostRoles/component_name=DATANODE|HostRoles/component_name=TASKTRACKER
{
foo=bar
}

With this functionality, it is now possible to do a get with the same syntax.
GET http://localhost:8080/api/v1/clusters/c1/host_components?HostRoles/host_name=h1|HostRoles/host_name=h2&HostRoles/component_name=DATANODE|HostRoles/component_name=TASKTRACKER

This will allow a user to see what resources will be updated.  GET only works for the host_component
collection resource if host is not specified in URI since the role name is not unique across
hosts.  If a user attempts to get an instance resource without specifying a host in the URL,
a 400 INVALID REQUEST is returned.

  was:
Ambari UI needs ability to update multiple host_component resources for a set of hosts.  Currently
this is not possible because it is necessary to include the host resource as part of the host_component
URI.

New functionality allows a host_component URI without providing a host resource.
Example: update foo property for the DATANODE and TASKTRACKER host components for hosts "h1"
and "h2".

URI syntax:
PUT http://localhost:8080/api/v1/clusters/c1/host_components?HostRoles/host_name=h1|HostRoles/host_name=h2&HostRoles/component_name=DATANODE|HostRoles/component_name=TASKTRACKER
{
foo=bar
}

    
> Add api support for updating multiple host_component resources for multiple hosts in
a single request
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-1029
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1029
>             Project: Ambari
>          Issue Type: Sub-task
>            Reporter: John Speidel
>            Assignee: John Speidel
>
> Ambari UI needs ability to update multiple host_component resources for a set of hosts.
 Currently this is not possible because it is necessary to include the host resource as part
of the host_component URI.
> New functionality allows a host_component URI without providing a host resource.
> Example: update foo property for the DATANODE and TASKTRACKER host components for hosts
"h1" and "h2".
> URI syntax:
> PUT http://localhost:8080/api/v1/clusters/c1/host_components?HostRoles/host_name=h1|HostRoles/host_name=h2&HostRoles/component_name=DATANODE|HostRoles/component_name=TASKTRACKER
> {
> foo=bar
> }
> With this functionality, it is now possible to do a get with the same syntax.
> GET http://localhost:8080/api/v1/clusters/c1/host_components?HostRoles/host_name=h1|HostRoles/host_name=h2&HostRoles/component_name=DATANODE|HostRoles/component_name=TASKTRACKER
> This will allow a user to see what resources will be updated.  GET only works for the
host_component collection resource if host is not specified in URI since the role name is
not unique across hosts.  If a user attempts to get an instance resource without specifying
a host in the URL, a 400 INVALID REQUEST is returned.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message