tree 540fa644191c5efc0df43a8f12724fb6773d712b
parent 6a4cd00be9d5ad70140fb6ddbd9bea51b00e4a14
author Jonathan Hart <jono@onlab.us> 1441287793 +0200
committer Gerrit Code Review <gerrit@onlab.us> 1444061216 +0000

Generalize IntentSynchronizer and separate reactive routing code

 * IntentSynchronizer can now handle any intent rather than having use
   case specific APIs
 * IntentSynchronizer does not generate or store intents anymore, it only
   perform synchronization
 * SdnIpFib generates and manages the procative route-based intents
 * ReactiveRoutingFib generates and manages the reactive intents
 * Unit tests have been tightned up to only test single components, rather
   than multiple components together
 * PeerConnectivityManager uses meaningful keys when creating intents

Change-Id: I4bb036ec8d056f43ece46f7dfc71d5e5a136b77d