Let a domain decide when he should be synchronized.

[clero]

Domains are browsed twice when applying configurations.
The first one gather syncer of domains which are not
"sequence aware" and launch a sync on them.
The second one launch an apply without providing a syncer set.
It lets sequence aware domains to synchronize if needed.

This patch allows to browse domains only once. If a domain
is sequence aware, it will be synchronized during configurations
restauration. If not, the synchronisation will be delayed at
the end of all applies.

Sequence aware domains are now synchronized first.

Signed-off-by: Jules Clero [email protected]

•  General Comment
• <img border=0 src='https://avatars.githubusercontent.com/u/7363635?v=3' height=16 width=16'> 👍 @krocard @dawagner @benaware
• <img border=0 src='https://avatars.githubusercontent.com/u/6862950?v=3' height=16 width=16'> 👍
• <img border=0 src='https://avatars.githubusercontent.com/u/6461629?v=3' height=16 width=16'> 👎 Synchronization of all sequence unaware domains needs to say coalesced. This is because the synchronization of sequence aware domains is susceptible to do some read/modify/write operations on syncers which are shared with sequence unaware ones. By synchronizing sequcence unware ones first, we ensure a proper initialization of the shared syncers.

  

[clero]

👍 @krocard @dawagner @benaware

[krocard]

👍

[benaware]

👎 Synchronization of all sequence unaware domains needs to say coalesced. This is because the synchronization of sequence aware domains is susceptible to do some read/modify/write operations on syncers which are shared with sequence unaware ones. By synchronizing sequcence unware ones first, we ensure a proper initialization of the shared syncers.