compute() has been optimized and all old code is gone. We no longer need to compute trees for each cluster. Furthermore, the computation of broadcast ports has been streamlined. Other routing/topology refactoring has been done as well.

Next round of refactoring. Attempting to normalize the terminology used. Fixed some bugs that have been around for a while too.

unit tests fixed by fixing an archipelago bug. A cluster is a *strongly connected* group of switches. A switch that is weakly connected to a cluster but not strongly connected to any other cluster will exist in its own cluster. This weak link, if not an external/BDDP-discovered link, will not be used to try and compute paths. Thus, while we compute clusters, any link that is not within a cluster and is not an external link is stored for reference when computing archipelagos. Essentially, the external links which typically are between clusters get merged into a new set with these weak links to allow for proper computation of archipelagos.

Create wrapper class that takes an OFMessage and allows for direct use in other containers where we don't care about the XID of the message. For example, if we want to create a unit test with predictable results but the XIDs are different depending on unit test execution, we can use the wrapper class to guarantee consistency. In the main code, we can more easily compare OFMessages without care for the XID and create cool data structures like caches.

Put maximumRouteEntriesStored into floodlightdefault.properties. Topology manager and instance can now access it.

Added in the routecache. Similar to pathcache, routecache is computed by Yen's algorithm in the compute function. As the name implies, a routecache entry does not need to be built into a route, as it is already built. Future commits will involve replacing patchcache with the new routecache.

Transferred over all of the Yen's algorithm additions. This includes getRoutes(). Some additions may have been missed.

Fix HA role REST API and add flag to allow us to toggle the controller's behavior when a transition to STANDBY occurs. For now, since we don't have much logic in other modules to handle STANDBY roles, we'll shutdown, but in the future, we should give the ability to stay running and await the next transition to ACTIVE.

Remove old makefile. Add round #1 of version support via REST API. The included code adds a /wm/core/version/json REST API. This will work in Eclipse and in situations where the jar is being run in the build environment with the pom.xml. It will not work when the jar has been compiled and relocated outside of the build environment. For this, we need to come up with a solution to build in the version at compile-time. This will either incorporate it as code or save it somewhere in the classpath.

convert integer DPIDs specified to the SEP to DatapathId to prevent duplicate DPID flow sets listed just because the DPID was entered in a different format. hexstring is what will be used

(1) Fix bug in forwarding where OF1.0 doesn't support tables, so don't set a table ID. (2) Tidy up stats REST API. (3) Remove LLDP info log that should have been debug.

Add in old URIs for static entry pusher for backwards compatibility. Note this only addresses URI compatibility *not* JSON key:value compatibility. Clean up warnings in LoadBalancer unit test

Finally! :-) OFMessageDamper works. Required creating a custom hashCode() (hashCodeIgnoreXid()) function for all OFMessages we would like to dampen.

Update Forwarding to support specifying a default table ID for flow insertion. It's flow table 0 by default, but it can be overridden using the net.floodlightcontroller.forwarding.Forwarding.table-id=X config parameter in floodlightdefault.properties. Set X to any table b/t 0 and the max.