You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Jeremy Mitchell (JIRA)" <ji...@apache.org> on 2017/02/07 21:35:41 UTC

[jira] [Closed] (TC-129) Create TO API endpoint to queue all servers for a delivery service

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

Jeremy Mitchell closed TC-129.
------------------------------

> Create TO API endpoint to queue all servers for a delivery service
> ------------------------------------------------------------------
>
>                 Key: TC-129
>                 URL: https://issues.apache.org/jira/browse/TC-129
>             Project: Traffic Control
>          Issue Type: Improvement
>          Components: Traffic Ops, Traffic Ops API
>            Reporter: Jeremy Mitchell
>            Priority: Minor
>
> Currently, you can queue updates (flip server.upd_pending field to true):
> - for a specific server
> - for a specific cachegroup (all the servers in that cachegroup)
> - for a specific cdn (all the servers in that cdn)
> but you can't queue updates for:
> - a specific delivery service (all the servers explicitly (edges) or implicitly (mids) assigned to that DS)
> Create the following endpoint restricted to users of ops role or above:
> POST /api/deliveryservices/:id/queue_update
> This endpoint should only queue updates. It should not allow you to dequeue updates because you may inadvertently dequeue server updates for servers that belong to another delivery service that has been queued. To dequeue, you'd have to do it at the cdn, cachegroup or server level.



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