Description of problem:

When ovn-controller is in the process of programming flows to ovs-vswitchd or
if there are any pending transactions, ovn-controller falls back to full recompute of logical flows in the next engine run.  This is the present design of ovn-controller.  But this full recompute can be very costly on very high scale environment.  ovn-controller should try to handle changes without falling back to full recompute.

One example is - Suppose a ct_zone engine needs to be full recomputed for any change, and if full recompute is not allowed then the engine is aborted and a full recompute of the whole engine is performed in the next run.  ct_zone engine full recompute ideally doesn't result in full recompute of openflows.


This needs to be improved in ovn-controller.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: