Author, and minimal changes.

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

ant tests result in some failures.

keytool -genkey -alias AliasChallengeResponse -keystore key2.jceks -keypass "PassWord" -storepass "PassWord" -storetype JCEKS

Value of CHALLENGE_RESPONSE_SECRET=AliasChallengeResponse

Value of CHALLENGE_RESPONSE_SECRET at CryptoUtil.java is hard coded.

The key.jceks needs to be created like this:

Value of CHALLENGE_RESPONSE_SECRET=AliasChallengeResponse

Value of CHALLENGE_RESPONSE_SECRET at CryptoUtil.java is hard coded.

We can shutdown gracefully and not wait (as Netty3 did). If not waiting turns out to be a problem, we can wait again.

Fixed a blunder in OFSwitchManager and Controller to allow switches to connect if a server IP isn't explicitly given in floodlihgtdefault.properties. Still can't get sync's bootstrap test to pass. Feels like a race condition b/t update threads.

Let's try this again. Fixed the two SFP bugs (Maxence's bug and another that prevented adding drop flows with null or empty-string actions). Also, replaced netty with a newer version in preparation for SSL support.

Revert "Fixed a couple bugs in SFP. (1) Always check the switch we're pushing a new flow to to see if an old flow needs to be removed from another switch (Maxence's bug). (2) Check for empty string in action lists and only print/add actions if they are specified. This allows an empty string or null to mean 'drop.'"

This reverts commit e2458ef3.

Fixed a couple bugs in SFP. (1) Always check the switch we're pushing a new flow to to see if an old flow needs to be removed from another switch (Maxence's bug). (2) Check for empty string in action lists and only print/add actions if they are specified. This allows an empty string or null to mean 'drop.'

Initial OF1.3 handshake working. Still trouble write()ing to OFSwitch instance after handshake complete. The Connection is reported as down, yet the switch is echoed repeatedly w/o a problem...

This reverts commit 4ae94669.

Refactored structure of core components to work with openflowj-loxi.
Presently refactoring Routing, Firewall, Forwarding, DeviceManager,
LinkDiscovery, Topology, and LearningSwitch.
Hub has been refactored.

amend to PR #443

Build is broken, but someone could fix this.  All they have
to do is fix all of the compile errors and update the hand
shaking logic.

moving counter registration to init() methods, and use of metadata constants