DNS sidecar and Nexus quota config templating

[JimMadge]

It isn't clear to me what these options do or what sensible values are.
There are some defaults set, so I wonder if we can,

• Not template these in dsh config template (i.e. implicitly use default values)
• Template with the default values
• Remove these entirely from the configuration?

There is also a gap in the documentation to show these keys in the example and to provide advice/recommendations.

[cptanalatriste]

The Nexus quota is a tricky parameter to get it right, and we only know the right size after usage. During many DSGs, including the last one, the quota fills up, and we need to increase. In contrast, in CVD-Net, we've been working well with the default for a while (after the new default was introduced).

Regarding the DNS Sidecar parameters, we made them configurable so the users can have more control over costs (critical in CVD-Net at that time). You can make the sidecar run more frequently/smoothly, but it will cost you. Otherwise, if you're happy with the occasional DNS error and are willing to wait a bit, there's a chance of saving some money. For context, with the default values, running the DNS sidecar costs 10 GBP per day, and we have entirely removed the DNS errors of the past.

Given all that, I guess I would prefer the "Template with the default values" option.

[JimMadge]

I think so far our attitude has been for the config to be explicit. If we have default values, it feels much safer to remove these things from the configuration and have them as optional 🤔.