You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/01/23 20:44:35 UTC

[jira] [Resolved] (SLIDER-762) Add API-level slider REST client

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

Steve Loughran resolved SLIDER-762.
-----------------------------------
    Resolution: Fixed

> Add API-level slider REST client
> --------------------------------
>
>                 Key: SLIDER-762
>                 URL: https://issues.apache.org/jira/browse/SLIDER-762
>             Project: Slider
>          Issue Type: Sub-task
>          Components: client, Web & REST
>    Affects Versions: Slider 0.70
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>             Fix For: Slider 0.70
>
>   Original Estimate: 4h
>          Time Spent: 29h
>  Remaining Estimate: 0h
>
> Using the slider REST API & authenticating Jersey code, write a REST client which binds to an AM then issues API calls.
> * API calls to mimic those used by slider client today: get cluster state, enum, perform actions.
> * Actions will be added client-side as they go in server side; they will fail if routed via YARN proxy and proxy doesn't support it or routed direct and the ws/ path isn't open to all callers.
> * this initial implementation will *not* rebind to AMs that fail/get restarted elsewhere. That will need extension to re-enum the app id in the RM, or re-lookup in the yarn-registry, both with some backup policy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)