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

2017-04-26 Thread Jeremy Mitchell (JIRA)

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

Jeremy Mitchell updated TC-253:
---
Description: 
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.

  was:
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.

This api should also queue updates on child caches IF status is "offline" 
(admin_down or offline) and the server type is ^EDGE* or ^MID*


> 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
>
>
> 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)


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

2017-04-26 Thread Jeremy Mitchell (JIRA)

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

Jeremy Mitchell updated TC-253:
---
Attachment: screenshot-1.png

> 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
>
>
> 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)