Once an EVC is redeployed, telemetry_int will also redeploy accordingly. Also, to ensure fast convergence when handling link down for EVCs that have failover, it's expected that a typical query to stored flows since it's querying indexed fields will not add significant latency, this point will be observed, and we'll see if it'll perform as expected or if more optimization will be needed from telemetry_int perspective.
telemetry_int will likely need to augment certain mef_eline events just so it can piggyback efficiently when an EVC has failover_path protection. Querying again and reprovisioning more flows than necessarily wouldn't be ideal and it would defeat the benefits of having failover path optimizations in the first place.
This will be one of the last items to be addressed on epic_telemetry_int_v1 since it's a non functional requirement, just so it can also be properly tested when This NApp is stable.
To quote from https://github.com/kytos-ng/kytos/pull/402/files
telemetry_intwill likely need to augment certainmef_elineevents just so it can piggyback efficiently when an EVC has failover_path protection. Querying again and reprovisioning more flows than necessarily wouldn't be ideal and it would defeat the benefits of having failover path optimizations in the first place.This will be one of the last items to be addressed on
epic_telemetry_int_v1since it's a non functional requirement, just so it can also be properly tested when This NApp is stable.