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.

Fault tolerant based on events, now it is totally event driven.
Logs with INFO scope.
Romoved comment from OFChannelHandler to show logs again.

floodlightdefault.properties2 renamed to floodlightBackupNode.properties

:)

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...