Update MatchUtils, ActionUtils, and GroupUtils to support converting OFGroup and OFPort types to/from strings more easily. This includes human-readable strings for special values, such as OFPort.CONTROLLER, etc., and OFGroup.ALL, etc.

Fix bug in statistics module REST API to correctly retrieve requested statistics for given DPID and port.

Loxi master is up-to-date now with FL codebase. With this commit, both ant and mvn should work to build. We will transition to mvn though to reduce the branch size (w/history purge) for upcoming v2.0.

Refactor OpenFlow server socket config to OFSwitchManager and expose more configuration options via floodlightdefault.properties

Update statistics REST API with OF1.5 statistics. This includes an update to Loxi to better support statistics/multipart messages. Loxi master will need to have this update incorporated before Travis CI will build successfully.

Getting there w/OF1.5 support. Just need a switch that supports it (well) to do some more thorough testing.

This is a huge commit. Lots of (good) stuff has been added and updated. First and foremost, OpenFlow 1.5 is now supported (yay) via a major update to OpenFlowJ-Loxi. This update necessitated the update of the Static Flow Pusher module and MatchUtils, ActionUtils, and InstructionUtils to support the newly-added features. This prompted me to explore the SFP to see if there was anything that could be improved. First thing that came to mind was adding support to push OpenFlow groups in addition to flows, thus group support has been added to the SFP via JSON, which is the format that should have been used in the first place. Action lists will be updated in the near future to be JSON instead of one massive ',', '=', and '->' delimited string. Thus, the Static Flow Pusher has been renamed the StaticEntryPusher, since it now encompasses groups. While groups were being added to the SFP (ahem...SEP), a number of optimizations were made to the SEP code, greatly reducing its complexity (IMHO). The support for OpenFlow meters can now be added rather trivially in the future, if desired. Last thing to note about the SEP is the work-in-progress addition of a 'schema' API to allow northbound applications to get information about SEP syntax. This is not complete yet, but the skeleton code is in place. Next thing in this pull request is miscellaneous changes throughout the controller, primarily in (de)serializers and REST APIs to support OpenFlow 1.5. Next item of business is the removal of the DebugEventService. This is an artifact of days past and need not clutter the controller anymore. Same goes for the TestModule; now that we have better tutorials and documentation on the wiki, an example isn't necessary. And, last but not least, some old libraries that weren't being used have now been removed.

Many REST ingest schemes (e.g. Graylog "JSON path from HTTP") expect servers to return well-formed JSON objects.  Floodlight is sometimes returning values that lack root objects.

Was:
   [ <list-of-device-objects>]

Now:
   { 'devices' : <list-of-device-objects> }

Add default of FALSE to allowing all origins in cross-domain requests. Remove old CORS code that was commented out.

Update Web UI to default to /ui/index.html for any request to /ui/. Also add in a filter for allowing any origin.

Updated to Java 8, junit-4.12, easymock-3.4. Still having trouble having unit tests pass in Eclipse for DeviceManagerImplTest, but they work find in maven and ant. testPacketInBasic and testPacketInBasicIPv6 are the trouble makers (fail occasionally).

Update MatchUtils and ActionUtils to fully support parsing 32-bit signed and unsigned port numbers in hex and decimal from strings. Also improved and added more keywords for ingress and output ports to support local, table, normal, controller, in_port, all, and flood without care for the openflow version.

Handle link and port down events in Forwarding. Remove flows ingress and egress a failed port or link to eliminate stale entries. This is done in Forwarding instead of the Link Discovery Manager, since some user modules might not want their flows removed and wish for them to persist until the link comes back up.

Add link speed to statistics REST API, which might be useful to gauge how much of the available bandwidth is being used.

Fired when receive a ROLE_STATUS message, at Master to Slave transitions, switch become deactivated.

Author, and minimal changes.

Tests ok.

NullPointerException verifications.

ant tests passed.

Switch roles from floodlightdefault.properties.

Fault tolerance with primary-backup or distributed, without reconfiguration.
One time crashed the controller shall restart with all switches in slave mode.
This can be achieved from floodlight.properties file.

The second properties file, floodlighBackupNode.properties is for backup nodes, and swicthes shall be configures in slave mode.

Regards

Hello guys, I have changed the logic of simple.FT (Fault Tolerant) module.

The basic idea is, the FT module register on SyncManager to receive RPC events
(connect and disconect nodes).

In connect events, the controller send its switch list to storage and
the other controllers can sync this info.
In disconnect events, the controller is informed about which controller crashed and
get switch list from storage and send a role request message to swicthes.

Regards.

and compare with initial cluster config defined in floodlightdefault.properties.

Issues: Do not treat the message ROLE_STATUS.
In case a cluster goes down and goes up, there is a problem, the Controller does not change its own role to role slave.

But works properly as Primary-Backup configuration.

Under development...

and compare with initial cluster config defined in floodlightdefault.properties.

Issues: do not treat the message ROLE_STATUS.
In case a cluster goes down and goes up, there is a problem, the Controller does not change its own role to role slave.

But works properly as Primary-Backup configuration.

Under development...