Generic Table First draft

[saynb]

• Phase 1: Objective : Phase 1 aims to provide support for a set of simple target-specific externs through GenericTables. Current APIs should work on the tables as intended. Read-write symmetry should be maintained wherever possible. Have a structure in place in p4info with which new type system and properties at different granularities can be specified and maintained.

  • Not extend any of the current RPC updates. Use INSERT, MODIFY, DELETE and Read RPC as is
  • Define Table categories/ properties
  • Define Entry and Field properties
  • Define Type system
  • Achieve Write/Read for simple PNA specific externs like ExactValueMatchLookupTable
  • Work on generic-table-dev

• Phase 2 Extend API list and other features.

  • Entry Handles
  • Table attributes (symmetric vs asymmetric)
  • New APIs
  • reset
  • add_or_mod
  • sync
  • usage_get
  • mod_inc
  • Table custom operations extensions. A way to define new operations via json modeling. For example, sync
• Phase 3
  • String representation of fields. Like IPv4 IPv6
  • Table notifications. Model notifications in a generic way

[saynb]

@chrispsommers @jafingerhut Have taken care of the comments and marked all items as resolved. Please feel free to unresolve any comment where you feel needs any more clarification/work

[chrispsommers]

@jafingerhut @smolkaj @jonathan-dilorenzo Last call for comments/approval. it;d be nice to merge this into the dev-branch which in any case is DRAFT.

@saynb Is this synced with main?

[saynb]

@jafingerhut @smolkaj @jonathan-dilorenzo Last call for comments/approval. it;d be nice to merge this into the dev-branch which in any case is DRAFT.

@saynb Is this synced with main?

The generic-table-dev branch needs to be synced with main. I can then git merge it in this private branch. Can you please help with that?

[chrispsommers]

@saynb Sure, just make the PR and tag me, thanks.