Change ATS Config Generation to Infer DSCP Files

[rob05c]

ATS config generation creates DSCP files from DS settings. These settings are read and then set as a file on the remap.config line for the DS.

But the files themselves are not inferred. The location Parameters for set_dscp_#.config must exist, or ATS will fail to start.

The Config Generation should infer these files from the DSCP settings of all DSes on the Server, instead of relying on duplicate, potentially-wrong Parameters.

I'm submitting a ...

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

Traffic Control components affected ...

• Traffic Ops ORT

Current behavior:

DSCP files are not dynamically created

Expected / new behavior:

DSCP files are dynamically created as needed, irrespective of location Parameters.

Minimal reproduction of the problem with instructions:

Delete all set_dscp_ location Parameters, run ORT, observe ATS exploding.

Anything else:

[mitchell852]

@rob05c is this issue still relevant

[rob05c]

Yes, we should still do this.

[mitchell852]

Yes, we should still do this.

@rob05c can you add impact and effort level labels? (high, med, low)