Keeping the right balance
Exploring the Project Template, you will find other "hard-coded" values, and you might be tempted to replace them all with variables. But we discourage you from doing so, because having too many variables will complicate the model unnecessarily.
While there is no right or wrong decision for each particular value, we recommend considering the following:
-
The Project Template is meant to act as a "configuration file" by itself. Therefore, it is not necessary to keep it unchanged between different projects. What should be kept unchanged is the "code", as we have explained in the previous chapters.
-
Some values have local significance, and they are never advertised outside of the SD-WAN network. In this case, reusing the same values in different projects does not harm the network. In fact, it may even simplify the Operations, external Orchestration, and so on. For example, why not use the same Loopback summary in all projects?
As always, applying common sense helps keep your model generic and uncomplicated.