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/11/06 21:56:16 UTC
[GitHub] [trafficcontrol] dpham692 opened a new issue #5258: Should not let user assign Topology to Delivery Services that already linked with an EDGE Server
dpham692 opened a new issue #5258:
URL: https://github.com/apache/trafficcontrol/issues/5258
<!--
************ STOP!! ************
If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact
the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
guidelines at https://www.apache.org/security/ regarding vulnerability disclosure.
- For *SUPPORT QUESTIONS*, use the Traffic Control slack (https://s.apache.org/atc-slack)
or Traffic Control mailing lists (https://trafficcontrol.apache.org/mailing_lists).
- Before submitting, please **SEARCH GITHUB** for a similar issue or PR.
-->
## I'm submitting a ...
<!-- delete all those that don't apply -->
<!--- security vulnerability (STOP!! - see above)-->
- bug report
## Traffic Control components affected ...
<!-- delete all those that don't apply -->
- Traffic Portal
## Current behavior:
<!-- Describe how the bug manifests -->
TP let user assign Topology to a DS that currently linked with an EDGE Server.
## Expected behavior:
<!-- Describe what the behavior would be without the bug -->
TP should not allow user to assign Topology to a DS that currently linked with an EDGE Server.
## Minimal reproduction of the problem with instructions:
<!--
If the current behavior is a bug, please provide the *STEPS TO REPRODUCE* and
include the applicable TC version.
-->
1. Create Delivery Services with no Topologies. Create a an EDGE Server.
2. Link DS with the EDGE Server.
3. Go back to Delivery Services and update it to have a Topologies. Notice that it success.
## Anything else:
<!--
e.g. stacktraces, related issues, suggestions how to fix (feel free to delete
this section)
-->
<!--
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
https://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] dpham692 closed issue #5258: Should not let user assign Topology to Delivery Services that already linked with an EDGE Server
Posted by GitBox <gi...@apache.org>.
dpham692 closed issue #5258:
URL: https://github.com/apache/trafficcontrol/issues/5258
----------------------------------------------------------------
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] rawlinp commented on issue #5258: Should not let user assign Topology to Delivery Services that already linked with an EDGE Server
Posted by GitBox <gi...@apache.org>.
rawlinp commented on issue #5258:
URL: https://github.com/apache/trafficcontrol/issues/5258#issuecomment-724284260
I believe the existing behavior is actually what we want. We would like to keep ds-server assignments in place for existing DSes but just ignore them if the DS is updated to use a topology. Once assigned to a topology, however, we should prevent assigning EDGE caches to a topology-based DS. Although, we _do_ allow assigning topology-based DSes to servers, in order to allow the cloning of DS assignments from server to server.
----------------------------------------------------------------
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] mitchell852 commented on issue #5258: Should not let user assign Topology to Delivery Services that already linked with an EDGE Server
Posted by GitBox <gi...@apache.org>.
mitchell852 commented on issue #5258:
URL: https://github.com/apache/trafficcontrol/issues/5258#issuecomment-725552064
> TP let user assign Topology to a DS that currently linked with an EDGE Server.
Yes, this behavior is fine as @rawlinp said.
----------------------------------------------------------------
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] mitchell852 edited a comment on issue #5258: Should not let user assign Topology to Delivery Services that already linked with an EDGE Server
Posted by GitBox <gi...@apache.org>.
mitchell852 edited a comment on issue #5258:
URL: https://github.com/apache/trafficcontrol/issues/5258#issuecomment-725552064
> TP let user assign Topology to a DS that currently linked with an EDGE Server.
Yes, this behavior is fine as @rawlinp said. Want to close this @dpham692 ?
----------------------------------------------------------------
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