Open italovalcy opened 2 weeks ago
I have the same opinion as Italo. From the operations perspective, I see two significant issues with the current approach:
If the data plane configuration is removed, when it is time to end the maintenance, we will have no ways of testing the link to make sure it is error-free and ready for production. That was one of the reasons the process is the way it is today.
Maybe a new metadata might be created to help. If metadata "never_disable" is on, the EVC should never be removed. Then we use those for testing, for instance, with BERToD.
According to the Maintenance blueprint, when a Link is under maintenance and the impacted EVC has no alternative path, the service should be deactivated. This should be done not only from the control plane perspective, but also on the dataplane perspective. Meaning: we should remove the flows from that particular EVC once the MW starts if no alternative path is found for that particular EVC.
It seems that only the control plane part is being done now.
Cc'ing @RenataFrez and @jab1982 so they can also share their perspective as network operators.