TP: only delivery services not assigned to a topology can be assigned directly to a server

[mitchell852]

I'm submitting a ...

• bug report
• new feature / enhancement request
• improvement request (usability, performance, tech debt, etc.)
• other

Traffic Control components affected ...

• CDN in a Box
• Documentation
• Grove
• Traffic Control Client
• Traffic Monitor
• Traffic Ops
• Traffic Ops ORT
• 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.