kytos-ng / telemetry_int

Kytos Telemetry Napp
MIT License
0 stars 2 forks source link

chore: ensure proxy port is available for both ends #31

Closed viniarck closed 1 year ago

viniarck commented 1 year ago

TODO refactor to always ensure it has proxy port based on EP031 augmented

  • telemetry_int will require a looped link on each source sink for both intra and inter EVCs, if it's not present, then telemetry_int will not enable INT, which implies that in this v1 iteration, you'll need to always have a proxy port (check out EP033 for more information) associated with both UNIs since the EVC is bidirectional. Although the EVC is bidirectional, the looped ports are used unidirectionally for each INT source. This explicitness of always knowing that both UNIs will need a proxy port facilitates to keep track when a proxy port changes and performing a side effect. Also, in the future, if unidirectional EVC is ever supported, then the application can derive the direction a->z or z->a and only check if the loop is available in the sink UNI.

https://github.com/kytos-ng/kytos/pull/402