[jira] [Comment Edited] (TC-253) TO API - create API endpoint for changing server status

["Jeremy Mitchell (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TC-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984869#comment-15984869 ] 

Jeremy Mitchell edited comment on TC-253 at 4/26/17 2:09 PM:
-------------------------------------------------------------

Queuing updates on child servers when the server is "offlined" (set to ADMIN_DOWN) or "onlined" (set to REPORTED) is functionality that exists currently in the GUI. See attached screenshot.




was (Author: mitchell852@apache.org):
Queuing updates on child servers when the server is "offlined" or "onlined" is functionality that exists currently in the GUI. See attached screenshot.



> TO API - create API endpoint for changing server status
> -------------------------------------------------------
>
>                 Key: TC-253
>                 URL: https://issues.apache.org/jira/browse/TC-253
>             Project: Traffic Control
>          Issue Type: New Feature
>          Components: Traffic Ops API
>            Reporter: Jeremy Mitchell
>            Assignee: Jeremy Mitchell
>            Priority: Minor
>             Fix For: 2.1.0
>
>         Attachments: screenshot-1.png, screenshot-2.png
>
>
> The API could look like this:
> PUT api/$version/servers/:id/status and include a request payload like:
> { "statusId": 1, "offlineReason": "foo bar" }
> If status is OFFLINE or ADMIN_DOWN, then offlineReason is required.
> This api should be limited to ops or above.
> Changing the status of a server should also queue updates on child caches IF the server type is ^EDGE* or ^MID*. This is needed because when you change the status of server, the parent.config file of the children servers (servers that are in a child cache group) is affected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)