[TC-337] Inactive delivery services are added to remap.config about trafficcontrol HOT 6 CLOSED

@nir-sopher Based on the documentation, When this is set to no Traffic Router will not serve DNS or HTTP responses for this delivery service.

I've used this in the past to configured and test delivery service before pushing configuration down the Traffic Router. Like a pre-stage before enabling and CR-Config.

Should this be considered a feature or a bug?

from trafficcontrol.

@smalenfant Note original defect by @elsloo (Comcast/traffic_control#1287). I migrated it during the bug-scrub

As it is useful and somehow documented, I would consider it a feature with an "improvement" requirement to better define the "active" field, allowing it to have 3 modes (no deployment, caches-only, and full-deployment).
However, taking "tenancy" into account, such fields should be in the hands of the CDN owner and not the DS owner. I.e. they should not be part of the DS table.

Furthermore, taking into account the "deployed versions" table defined for DSCV (Delivery Service Configuration Versioning), the "active" field can be removed from the DS table, and the DS should be deployed if the version exists in the "deployed versions" table. The "deployed versions" table can have a "deploy-mode" field with the values "full" and "caches-only" - to support the usecase Steve described.

Therefore, I would not change this behavior for now.
@elsloo - what do you think.

from trafficcontrol.

If we're building a more comprehensive solution that supersedes the original issue referenced above, I'm okay with ignoring this for the time being. I'm not sure that allowing inactive delivery services in remap.config was a conscious decision, so @smalenfant might be relying on something that was unintended behavior. The documentation merely describes what Traffic Router does, not whether the remap exists on the edge.

I discussed this quickly with @PSUdaemon and @knutsel and they both suggested that we might want to introduce states on delivery services, much like we have on servers. For example, we might want to have "disabled," "mapped," "mapped and routed," "routed," etc. I think this still holds when we think about DSCV @nir-sopher, as a particular version of a delivery service could be in one of those states.

from trafficcontrol.

@elsloo are you ok with moving this to a future release so we can figure out the right solution?

from trafficcontrol.

This is somewhat related to #1121. If inactive delivery services are not added to remap.config, then ANY_MAP delivery services will have to move to active, at which point the TR treats them similarly to HTTP delivery services, which is invalid according to the docs.

from trafficcontrol.

duplicate of #3746

from trafficcontrol.