Closed prsunny closed 4 months ago
Currently the route table is modified w/routes belonging to an ENI (per ENI). Controller calls each route update w/ENI key. Group table & binding allows for atomic binding for an ENI (instead of updating 1 by 1) (Not a subset of ENI routes). Cx update their routes in the route table, and expect all or nothing to work. Adding 1 by 1 we can end up in a non-complete/inconsistent goal state.
What if libsai has no resources to support an atomic update?
The controller will need to wait to determine whether this is a successful operation or not.
If unsuccessful, old route table will persist.
Are all comments resolved? IF Y, I can merge :)
hi @r12f , @kperumalbfn , and @pranjal-git - would you mind reviewing for Prince please? TY...