Closed pudelkoM closed 1 year ago
@pudelkoM thanks for submitting this, we discussed the changes at the P4 API WG meeting today (10/23/2020). I think the takeways are:
scope
field to the Entity
message is useful (based on current use cases on Stratum) and low-riskForwardingPipelineConfig
message change:
ForwardingPipelineConfig
message could be changed to support multiple "configurations"p4_device_config
) to determine whether a write operation on an Entity
is valid based on the P4 object id & the scope
value. 2) could support compiling P4 programs from 2 different stakeholders independently and then using them for different pipelines (they can share the same id space).I believe we can start with adding a scope
field to the Entity
message, without any other change. However, we still need to update the specification accordingly to 1) define the appropriate terminology, 2) present some multi-pipe device model that users can refer to, 3) based on the device mode, describe which use cases we are trying to support and which are out-of-scope.
@bocon13 @ccascone @saynb - hopefully this is not to inaccurate based on our discussions, please feel free to commen
Hi @pudelkoM do you still want to move this forward, or is it time to retire it?
I'm doing some "housecleaning." @jafingerhut @smolkaj @antoninbas @bocon13 Is @pudelkoM still participating? No response to my inquiry 5 weeks ago. I am inclined to close this soon.
@chrispsommers I think we can close this. @pudelkoM is working on other projects now. We can also re-open if needed in the future. Thanks!
TODOs:
Fixes #316