Content Invalidation Jobs should work with MSO (multi site origin) delivery services

[ocket8888]

I'm submitting a ...

• new feature / enhancement request
• other

Traffic Control components affected ...

• Traffic Ops

Current behavior:

Currently if you try to create a content invalidation job for a Delivery Service with multiple origins, a job will be generated only for the origin marked as the Delivery Service's "primary" origin.

Expected / new behavior:

Unclear. Should users need to make a different job for each desired origin, and need to specify to which origin a job belongs at creation, or should job creation automatically create a job for each of a Delivery Service's origins?

[mitchell852]

I would vote for this behavior: Creating a job for a delivery service actually creates a job for each origin of that delivery service.

Because creating a job (the only kind of job we have is PURGE job aka invalidate content job) for a subset of a delivery service's origins will not fully invalidate that content.

NOTE: there are 2 ways to configure MSO I believe:

1. Create multiple origins (tp.domain.com/#!/origins) for a ds
2. Create servers of type=origin and attach them to a ds via a ds profile

The above solution would only work for number 1