You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2020/07/08 01:55:53 UTC

[GitHub] [trafficcontrol] mitchell852 opened a new issue #4860: TP: only delivery services not assigned to a topology can be assigned directly to a server

mitchell852 opened a new issue #4860:
URL: https://github.com/apache/trafficcontrol/issues/4860


   ## I'm submitting a ...
   <!-- (check all that apply with "[x]") -->
   <!--- security vulnerability (STOP!! - see above)-->
   - [] bug report
   - [ ] new feature / enhancement request
   - [x] improvement request (usability, performance, tech debt, etc.)
   - [ ] other <!--(Please do not submit support requests here - see above)-->
   
   ## Traffic Control components affected ...
   <!-- (check all that apply with "[x]") -->
   - [ ] CDN in a Box
   - [ ] Documentation
   - [ ] Grove
   - [ ] Traffic Control Client
   - [ ] Traffic Monitor
   - [ ] Traffic Ops
   - [ ] Traffic Ops ORT
   - [x] Traffic Portal
   - [ ] Traffic Router
   - [ ] Traffic Stats
   - [ ] Traffic Vault
   - [ ] unknown
   
   ## Current behavior:
   When attempting to assign delivery services to a server, the user is presented with ALL delivery services within the server's cdn (GET /deliveryservices?cdn=server's cdn id). This was fine until topologies were introduced. Now delivery services that utilize a topology cannot be assigned to a server (they will fail api validation) so they need to be excluded from the list of eligible delivery services for server assignment.
   
   ## Expected / new behavior:
   When fetching a list of delivery services that can be assigned to a server (GET /deliveryservices?cdn=server's cdn id), exclude those delivery services that utilize a topology to prevent the user from selecting an ineligible ds (one that uses a topology)
   
   ## Minimal reproduction of the problem with instructions:
   - find a delivery service and assign a topology to it
   - find an edge server in the same cdn as the delivery service and try to assign that delivery service to that server. you will get an api error.
   
   <!--
   Licensed to the Apache Software Foundation (ASF) under one
   or more contributor license agreements.  See the NOTICE file
   distributed with this work for additional information
   regarding copyright ownership.  The ASF licenses this file
   to you under the Apache License, Version 2.0 (the
   "License"); you may not use this file except in compliance
   with the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
   Unless required by applicable law or agreed to in writing,
   software distributed under the License is distributed on an
   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
   under the License.
   -->


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [trafficcontrol] ocket8888 closed issue #4860: TP: only delivery services not assigned to a topology can be assigned directly to a server

Posted by GitBox <gi...@apache.org>.
ocket8888 closed issue #4860:
URL: https://github.com/apache/trafficcontrol/issues/4860


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org