An idea for such an addition to the P4Runtime API spec was discussed at the 2020-Sep-11 P4 API work group meeting.
The idea is that after a successful VERIFY_AND_SAVE operation, currently it seems that the only way to proceed is to commit that new program to the data plane.
It seems potentially useful to have a way, after a successful VERIFY_AND_SAVE, for the client to indicate that it wishes to abort that operation, keeping the data plane in the current state, and allowing the client to go back to making read and write requests on table entries/etc. for the current program. ABORT seems like a reasonable name for such an operation.
An idea for such an addition to the P4Runtime API spec was discussed at the 2020-Sep-11 P4 API work group meeting.
The idea is that after a successful VERIFY_AND_SAVE operation, currently it seems that the only way to proceed is to commit that new program to the data plane.
It seems potentially useful to have a way, after a successful VERIFY_AND_SAVE, for the client to indicate that it wishes to abort that operation, keeping the data plane in the current state, and allowing the client to go back to making read and write requests on table entries/etc. for the current program. ABORT seems like a reasonable name for such an operation.
It seems best to create a PR for this issue, after resolving issue https://github.com/p4lang/p4runtime/issues/308 to clarify the existing spec behavior.