-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To Be Documented: SDN Controller's knowledge of flows and its control of various counters #43
Comments
@lisahnguyen to your point # 3 above, I would hope the P4 model would declare all counters. If they are associated with table entries which the SDN controller creates, then the counters would be created "automatically." |
@chrispsommers Thanks for the comment. |
@lisahnguyen Yes it is WIP, it is good that you bring all these points up early in the process. It is a community effort and the more eyes on it the better. |
Confirming that this is not the requirement, nor the statistics. Per Michal - We do not need to know for every single flow. However some statistic per flow (such as metering) we want to query statistics per bucket (not flow specific). Or scenarios where customers can do random sampling (per ENI). Dump the card (flows) for the customer to sample. Not close tracking/reporting on every single flow to the controller. More documentation will be forthcoming as we continue the project. |
Based on the discussion in Community meeting today, please help confirm/clarify the following understanding:
The text was updated successfully, but these errors were encountered: