p4-discuss@lists.p4.org

discussion of p4 language ideas, tools, questions, etc. -- not related to direct code development

View all threads

Standardize P4Runtime controller role definition scheme

AB
Antonin Bas
Mon, Oct 15, 2018 5:53 PM

Hi all,

The P4 API WG is currently considering standardizing one possible role
definition scheme for P4Runtime arbitration (
https://s3-us-west-2.amazonaws.com/p4runtime/docs/v1.0.0-rc3/P4Runtime-Spec.html#sec-master-slave-arbitration-and-controller-replication).
This would enable two or more different control entities to manage
different parts of the pipeline (e.g. L2 tables / L3 tables / INT logic /
...) without interfering with each other. Before moving forward with a
concrete proposal, we would like to gauge interest from the P4 community.
If you are interested in this feature and you feel comfortable presenting
your use-case in front of the WG (ideally at the October 24th meeting),
please let me know (antonin@barefootnetworks.com).

Thanks,

--
Antonin

Hi all, The P4 API WG is currently considering standardizing one possible role definition scheme for P4Runtime arbitration ( https://s3-us-west-2.amazonaws.com/p4runtime/docs/v1.0.0-rc3/P4Runtime-Spec.html#sec-master-slave-arbitration-and-controller-replication). This would enable two or more different control entities to manage different parts of the pipeline (e.g. L2 tables / L3 tables / INT logic / ...) without interfering with each other. Before moving forward with a concrete proposal, we would like to gauge interest from the P4 community. If you are interested in this feature and you feel comfortable presenting your use-case in front of the WG (ideally at the October 24th meeting), please let me know (antonin@barefootnetworks.com). Thanks, -- Antonin